Embedded Engineer

Noida

Type: Full Time

Location: Noida, Delhi NCR

Compensation (CTC): 25-30 LPA

Starting Date: April 2026 (or sooner)

We are moving from prototype to production and we need the person who will own the brain of our machines. If your interest lies at the intersection of hardware-software boundary, love wrestling with real-time data pipelines, and care more about reliable outcomes than theoretical purity, this role was written for you.

WHAT YOU WILL OWN

Hardware-Software Bridge: Own the software architecture and board bring-up. Work directly with operations to understand data-collection workflows and design firmware that simplifies and accelerates them
Camera & Vision Pipelines: Write V4L2 drivers, manage MIPI CSI-2 interfaces, handle video synchronisation, and ensure high-bandwidth data moves without dropping a single frame
Custom Sensor Firmware: Develop firmware for bespoke sensors and interface them cleanly with the main processor - vision is only part of the picture
System Architecture: Design for V1 to ship tomorrow while drawing system boundaries so V2 isn’t a rewrite. Memory bottlenecks, DMA, and thermal throttling are yours to solve

WHO YOU ARE

The Pragmatic Builder: Reliable data today > perfect architecture for five years from now. You know when to duct-tape a dev board and when to spin a custom PCB
Hardware-Software Bilingual: You don’t throw problems over the fence. When software misbehaves you reach for an oscilloscope or a logic analyser before blaming firmware
Egoless Engineer: COTS beats NIH every time if it saves three months of runway. You ship, not build-for-building’s-sake
Systems Thinker: You understand how a single firmware decision can ripple through thermal budgets, latency guarantees, and the operator experience

Name *

Email *

Highest level of Education (BTech, MTech, PhD etc.) *

Where are you currently located? *

What would be your dream home lab setup? *

Walk us through a time you debugged a problem that turned out to be at the hardware-software boundary *

What tools did you use? What was your mental model going in, and how did it change?

Describe a real-time embedded system you have shipped, not prototyped *

What was the hardest reliability constraint? How did you validate it before handoff?

You need to move high-bandwidth video from four MIPI CSI-2 sensors to storage without dropping frames on a resource-constrained SoC. Walk us through your approach *

We care about your decision-making process: trade-offs, bottlenecks you anticipate, and how you’d profile/validate

Tell us about a time you chose a COTS or open-source solution over rolling your own. What drove that decision, and would you make the same call again? *

We are looking for honest reflection, not the ‘correct’ answer

What embedded platform do you reach for first when prototyping something new, and why? *

Bonus: where does it fall short, and what do you switch to when it does?

Are you familiar with PCB design? If yes, which tools and what is the most complex board you have reviewed or laid out? *

Tell us about the most challenging schematic or layout decision you made

Describe a solution you designed that ultimately failed or never shipped. What would you do differently? *

Share your resume *

Share your GitHub *

Share your LinkedIn *

Made withBinary