1

Internship Robotics Simulator Jobs (NOW HIRING)

next page

Showing results 1-20

Internship Robotics Simulator information

See salary details

$2.4K

$5.3K

$7.7K

How much do internship robotics simulator jobs pay per month?

As of Aug 18, 2026, the average monthly pay for internship robotics simulator in the United States is $5,290.17, according to ZipRecruiter salary data. Most workers in this role earn between $3,000.00 and $7,500.00 per month, depending on experience, location, and employer.

What does an internship robotics simulator do?

An Internship Robotics Simulator typically involves working with software that models the behavior of robots in virtual environments. Interns in this role help design, develop, and test robotics simulations to evaluate algorithms, sensor integrations, or robot movements without needing physical hardware. This allows for rapid prototyping, debugging, and validation of robotic systems. Interns may assist engineers by creating simulation scenarios, analyzing results, and improving simulation fidelity. The role is ideal for students or recent graduates interested in robotics, computer science, or related engineering disciplines.

What are the key skills and qualifications needed to thrive as an internship robotics simulator, and why are they important?

To excel as an Internship Robotics Simulator, you need a background in robotics, mechanical or electrical engineering, and programming fundamentals, often supported by current enrollment in a relevant degree program. Familiarity with simulation tools like Gazebo, MATLAB/Simulink, or ROS, as well as coding languages such as Python or C++, is typically required. Strong problem-solving abilities, attention to detail, and effective teamwork are soft skills that help interns stand out. These competencies are essential for accurately modeling robotic systems, collaborating on innovative projects, and translating simulated results into real-world applications.

What types of projects or tasks can I expect to work on during an internship in robotics simulation?

As an intern in robotics simulation, you'll typically work on developing, testing, and troubleshooting virtual models of robots within simulation environments like Gazebo, ROS, or V-REP. Your tasks may include writing scripts to automate robot behaviors, creating and refining simulation scenarios, and assisting in integrating sensors or actuators into simulated robots. Expect close collaboration with engineers and researchers, as you'll often help validate algorithms before they're tested on real hardware. This hands-on experience provides valuable exposure to both software development and robotics engineering challenges.

What is the difference between Internship Robotics Simulator vs Robotics Engineer?

AspectInternship Robotics SimulatorRobotics Engineer
CredentialsEnrolled in or recent graduate of engineering or computer science programsBachelor's or master's degree in robotics, mechanical, electrical, or computer engineering
Work EnvironmentEducational or training settings, simulation labs, or remoteResearch labs, manufacturing facilities, or corporate offices
Industry UsageLearning and training in robotics simulation softwareDesign, develop, and test real robotic systems

The Internship Robotics Simulator role focuses on gaining experience through simulation tools and educational environments, while Robotics Engineers work on designing and implementing actual robotic systems in professional settings. Both roles share foundational knowledge but differ in scope and responsibilities.

More about Internship Robotics Simulator jobs

What cities are hiring for Internship Robotics Simulator jobs?

Cities with the most Internship Robotics Simulator job openings:

What are the most commonly searched types of Robotics Simulator jobs?

The most popular types of Robotics Simulator jobs are:

What states have the most Internship Robotics Simulator jobs?

States with the most job openings for Internship Robotics Simulator jobs include:

Infographic showing various Internship Robotics Simulator job openings in the United States as of August 2026, with employment types broken down into 10% Internship, 56% Full Time, 32% Part Time, 1% Temporary, and 1% Contract. Highlights an 77% Physical, 2% Hybrid, and 21% Remote job distribution, with an average salary of $63,482 per year, or $30.5 per hour.

Robotics Software Engineer, Simulations

Atomic Machines

Emeryville, CA

Full-time

Posted 3 days ago

New


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.