ZipRecruiter

Log In

1

Physics Simulation Python Jobs in Berkeley, CA (NOW HIRING)

Luminary Cloud

Geometry/Meshing Engineer

San Mateo, CA · On-site

... for physics simulation (e.g., CFD, structural analysis, thermal simulation) and Physics AI ... Proficient in Python. Enterprise-level software development and testing practices. * Operates at ...

Luminary Cloud

Geometry/Meshing Engineer

San Mateo, CA · On-site

$180 - $240/hr

... for physics simulation (e.g., CFD, structural analysis, thermal simulation) and Physics AI ... Proficient in Python. Enterprise-level software development and testing practices. * Operates at ...

Skild AI

Machine Learning Engineer

San Mateo, CA · On-site

Proficiency in Python, C++, or similar and at least one deep learning library such as PyTorch ... Experience with physics simulation engines and tools for training RL. * Deep understanding of ...

UniversalAGI

AI Product Engineer

San Francisco, CA · On-site

Deep technical comfort with Python on the backend, alongside React, TypeScript, and Next.js on the ... Prior experience or background with 3D applications, CAD, physics simulations, or engineering ...

Foundation

AI Engineer (RL & WBC)

San Francisco, CA · On-site

... physics simulation environments (e.g., MuJoCo, Isaac Lab). • Proficiency in Python and C++ for algorithm development and deployment. • Experience with deep learning frameworks (e.g., PyTorch, JAX ...

previous pagenext page

Showing results 21-40

All JobsPhysics Simulation Python JobsPhysics Simulation Python Jobs in Berkeley, CA

Physics Simulation Python information

See Berkeley, CA salary details

$13.5K

$82.8K

$148.8K

How much do physics simulation python jobs pay per year?

As of Aug 21, 2026, the average yearly pay for physics simulation python in Berkeley, CA is $82,773.00, according to ZipRecruiter salary data. Most workers in this role earn between $53,900.00 and $97,300.00 per year, depending on experience, location, and employer.

What is a physics simulation Python developer?

A Physics Simulation Python developer is a professional who uses the Python programming language to design, implement, and analyze simulations that model physical systems and phenomena. These simulations can range from simple particle motion to complex fluid dynamics or electromagnetic fields, and are widely used in research, engineering, gaming, and education. The developer typically utilizes scientific libraries such as NumPy, SciPy, and PyBullet, and may also work with visualization tools to present simulation results. Their work helps in understanding real-world physics problems, testing hypotheses, or creating realistic interactive environments.

What are the key skills and qualifications needed to thrive as a physics simulation Python developer?

To excel as a Physics Simulation Python Developer, you need a strong background in physics, mathematics, and proficiency in Python programming, often supported by a degree in physics, engineering, or computer science. Familiarity with simulation libraries (such as NumPy, SciPy, PyBullet, or SimPy), version control systems like Git, and experience with visualization tools are commonly required. Analytical thinking, problem-solving abilities, and effective collaboration are standout soft skills in this role. These skills enable the development of accurate, efficient simulations and foster productive teamwork in research or engineering projects.

What are some common challenges faced by professionals working in physics simulation with Python, and how can they be addressed?

Professionals in Physics Simulation with Python often encounter challenges such as optimizing simulation performance, ensuring numerical accuracy, and integrating complex libraries (e.g., NumPy, SciPy, PyBullet) into larger workflows. Addressing these issues typically involves using efficient coding practices, leveraging vectorized operations, and validating results with analytical solutions or experimental data. Collaboration with domain experts and regular code reviews can also help maintain code reliability and project scalability. Staying updated with the latest simulation frameworks and actively participating in open-source communities are excellent ways to overcome technical hurdles.

What is the difference between Physics Simulation Python vs Mechanical Engineer?

AspectPhysics Simulation PythonMechanical Engineer
Required CredentialsProgramming skills, knowledge of physics, often a degree in physics or computer scienceMechanical engineering degree, professional licensure in some regions
Work EnvironmentSoftware development, research labs, simulation environmentsDesign offices, manufacturing plants, R&D departments
Industry UsageSimulation software development, research, academiaProduct design, manufacturing, systems optimization

Physics Simulation Python focuses on developing and implementing physics-based simulations using Python programming, often in research or software development contexts. Mechanical Engineers apply engineering principles to design, analyze, and manufacture mechanical systems. While both roles require a strong understanding of physics, Physics Simulation Python emphasizes coding and simulation, whereas Mechanical Engineering involves practical design and application in physical systems.

What are popular job titles related to Physics Simulation Python jobs in Berkeley, CA?

For Physics Simulation Python jobs in Berkeley, CA, the most frequently searched job titles are:

What job categories do people searching Physics Simulation Python jobs in Berkeley, CA look for?

The top searched job categories for Physics Simulation Python jobs in Berkeley, CA are:

What cities near Berkeley, CA are hiring for Physics Simulation Python jobs?

Cities near Berkeley, CA with the most Physics Simulation Python job openings:

Physics Simulation Python jobs near you
Infographic showing various Physics Simulation Python job openings in Berkeley, CA as of August 2026, with employment types broken down into 1% Internship, 86% Full Time, 7% Part Time, and 6% Contract. Highlights an 79% Physical, 6% Hybrid, and 15% Remote job distribution, with an average salary of $82,773 per year, or $39.8 per hour.

Robotics Software Engineer, Simulations

Atomic Machines

Emeryville, CA • On-site

Full-time

Posted 7 days ago

Job description

Atomic Machines is ushering in a new era of micromanufacturing with its Matter Compiler technology platform. This platform enables new classes of micromachines to be designed and built by providing manufacturing processes and a materials library that are inaccessible to semiconductor manufacturing methods. It unlocks MEMS manufacturing not only for device classes that could never be produced by semiconductor methods, but also for entirely new categories. Furthermore, this digital platform is fully programmable in the way 3D printing is digital-but whereas 3D printing produces parts of a single material using a single process, the Matter Compiler technology platform is a multi-process, multi-material system: bits and raw materials go in, and complete, functional micromachines come out. The Atomic Machines team has also created an exciting first device-made possible only through the Matter Compiler technology platform-that we will be unveiling to the world soon.
 
Our offices are in Emeryville and Santa Clara, California.
About The Role:

Our manufacturing system is composed of nodes; each delivers a unit of manufacturing capacity for a process, and there are a dozen or more node types. As a Robotics Software Engineer, Simulations, you will help build our machines' digital twins: simulations that stand in for the real hardware behind the same software interfaces, so that manufacturing software can be developed and tested without waiting for machine time. You will join the simulation team at its start, working directly with its founding engineer.

Your work starts with the foundation all our nodes share and the robotics that move material through them. One week you might build the model of a motion axis, a gripper, or a sensor and watch a machine's software run against it; the next, wire a node's software into the simulator so it can be tested in CI, or dig into why the simulation and the real machine's telemetry disagree and decide whether that's a software bug or a gap in the model.

This role suits an engineer with strong fundamentals, curiosity about how physical machines behave, and an instinct for the difference between what the model says and what the machine did.

What You'll Do:
  • Build models of the devices that make up our machines (motion axes, sensors, grippers, and the machinery around them) that behave like the real thing behind the same software interfaces.
  • Build scenario and regression suites that let machine software be developed and tested in CI, with no hardware in the loop.
  • Extend simulation coverage across our machine types so more of the stack can be exercised without a physical machine.
  • Build validation tooling that compares simulation behavior against real-machine telemetry, and root-cause divergences to a software bug or a model-fidelity gap.
  • Grow toward owning a well-bounded piece of the platform, such as the device-model library or the simulation harness our CI runs on.
What You'll Need:
  • 2+ years building software for systems that interact with hardware or the physical world; industry, internships, robotics competitions, research, and serious open-source work all count.
  • Strong programming fundamentals with working Python: you can build and debug real systems in Python, even if it isn't your first language.
  • Simulation or modeling exposure: physics simulation, behavioral/discrete-event simulation, digital twins, or game-engine work; you have used a simulator seriously and know where it lied to you.
  • A first-principles mindset: you reason about why a design works, not just how you've seen it done.
  • Practical understanding of state machines, concurrency, and determinism.
  • Systematic debugging habits and the collaboration skills to chase problems across the software/hardware boundary.
  • BS in CS, CE, EE, ME, Mechatronics, Robotics, or equivalent experience.
Bonus Points For:
  • Working C++: our motion stack and parts of the simulation core are C++ (expected at L4; a strong plus at L3).
  • Physics-engine experience: MuJoCo, Drake, Bullet, PyBullet, or similar; rigid-body dynamics and contact modeling.
  • Robotics depth: kinematics, dynamics, motion planning, or state estimation.
  • Experience with robotics middleware, ROS or otherwise (we build our own).
  • gRPC/Protobuf APIs, observability tooling, or CI/test infrastructure at scale.
  • Hardware-in-the-loop testing or sim-based validation of real machines.

Apply