Embedded Systems Engineer

About the role

You will join a medical-adjacent instrumentation company building embedded measurement systems used in research laboratories. The embedded systems team sits at the intersection of hardware, firmware, and application software: you define how the pieces fit, prove the system meets its requirements, and own the integration when they do not. This role matters because customers buy a working instrument, not a collection of subsystems, and someone has to own the seams.

What you will achieve

• Ship system-level integration for two instrument product lines, from requirements decomposition through verification testing, with all acceptance criteria signed off on schedule, and verification reports accepted by quality on first submission
• Drive first-pass integration success by writing interface control documents that cut cross-team rework by 30%, measured in integration-phase bug counts
• Reduce system defect escape by building an automated integration test suite covering 85% of system requirements and running nightly on production-equivalent hardware, with failures triaged and assigned before the next standup
• Build the system timing and resource budget (CPU, memory, bus bandwidth) that keeps both product lines within their performance margins with 20% headroom, reviewed and re-baselined at every major design change
• Own failure analysis for system-level issues, delivering five-whys root causes with corrective actions inside one sprint and tracking them to closure

What you will bring

Must-haves

• 2-5 years working across the embedded system boundary: firmware plus hardware plus application software on the same product
• Solid C/C++ and Python, used for both target code and integration/test tooling you maintain yourself
• Experience writing and verifying requirements: test plans, traceability matrices, and acceptance criteria that survive review
• Hands-on system integration: bringing up multi-board systems and debugging across clock, power, and signal domains
• Familiarity with both RTOS and Linux targets and the engineering tradeoffs between them for a given product
• Strong lab skills: oscilloscopes, protocol analyzers, and power measurement applied to system-level validation
• Clear technical communication across hardware, software, and product stakeholders with different vocabularies

Nice-to-haves

• Experience with regulated or quality-managed development such as ISO 9001 design controls
• Familiarity with data acquisition, signal chains, or precision measurement instrumentation
• Knowledge of EMC/EMI considerations in system design and how firmware can make emissions better or worse