We're looking for mavericks - inventors at heart, people who get genuinely fired up by a hard problem, not intimidated by it.

If you take things apart just to understand them, to get to the heart of machines, and then put them back together making it whole again; if you'd rather chase an unsolved problem than polish a solved one; and if "build something that matters" excites you - come build it with us.

We're building the electromechanical core of surgical robots - actuators, sensors, and control loops that have to work flawlessly because there's a patient on the other end of it. The problems here aren't solved. You'll define the architecture, build the first proof-of-concept, watch it fail, and dig into why - across electronics, embedded systems, and mechanical hardware, sometimes all in one afternoon.

What you'll actually be doing

- Architecting electromechanical subsystems from the ground up - not filling in someone else's spec.
- Getting your hands dirty across electronics, embedded systems, and mechanical integration.
- Building and breaking POCs - then figuring out what the failure is actually telling you.
- Designing test jigs, fixtures, and validation processes that don't exist yet.
- Benchmarking motors, encoders, and sensors to squeeze out real performance data.
- Living in oscilloscopes, multimeters,



and logic analyzers when things misbehave.
- Writing scrappy C/C++ firmware rapid enough to test an idea before it goes stale.
- Working shoulder-to-shoulder with electronics, embedded, mechanical, and clinical teams -
- because nothing here ships in isolation.

Who we're looking for

- You've got 2-5 years in electromechanical integration or robotics, and a degree in Mechatronics, Robotics, Electrical, Electronics, or something adjacent - but what matters more is that you've actually built things.
- You've prototyped subsystems, defined harnesses, and validated hardware with your own hands, not just on paper.
- You understand motors, encoders, sensors, and control systems at a gut level.
- You're comfortable in C/C++ and know your way around a bench full of test equipment.
- You're the kind of person who says "let me try something" before "let me check the spec" - genuinely energized by problems that don't have an obvious answer yet.

What you get

- Real ownership - your subsystem, your calls, your name on it.
- A front-row seat across electronics, embedded, and mechanical domains - not a narrow lane.
- A team of mavericks who'd rather solve a hard problem than avoid one.

📌 Mechatronics Engineer (Bengaluru)
🏢 Articulus Surgical
📍 Bengaluru