> Markdown version of [/jobs/ext/2071423-principal-system-engineer](https://www.wearedevelopers.com/jobs/ext/2071423-principal-system-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Principal System Engineer - **Company:** Analog Devices - **Location:** Boston, MA, United States - **Experience:** Expert - **Salary:** $157,080.0 - $227,460.0 - **Contract:** Permanent contract - **Skills:** Computer-Aided Design, Application Programming Interfaces (APIs), Artificial Intelligence, Altium Designer, Systems Engineering, C++ (Programming Language), Software Documentation, Embedded Software, Network Interface Controllers, Firmware, Failure Mode Effects Analysis, Python (Programming Language), Machine Learning, Software Architecture, Requirements Traceability, Signal Processing, Software Requirements Analysis, Subsystems - **Published:** August 15, 2026 - **Apply:** https://www.oriontalent.com/search-jobs/career/11646312/principal-system-engineer-massachusetts-ma-boston ## About the Role * 8+ years (12+ years preferred) in systems engineering of complex electromechanical or mechatronic products, including their embedded/host software. * A completed prototype-to-production journey. Direct, hands-on experience taking a hardware and software product from MVP/prototype through to a manufacturable, production-qualified release - not just participation in reviews. * Cross-domain fluency. Comfortable reading CAD drawings, electrical schematics, firmware/sensor specs, and software architecture/API designs well enough to spot interface conflicts, without needing to be the deepest expert in any one domain. * Hands-on tool proficiency. Working proficiency with mechanical CAD (e.g., OnShape or equivalent) and circuit design/schematic-capture tools (e.g., Altium or equivalent) sufficient to review, redline, or directly interrogate designs; enough coding ability (e.g., Python, C++) to script analysis, build small verification/test tooling, or prototype an interface. * Curiosity and initiative around AI. A demonstrated habit of learning new engineering tools and putting them to practical use, with an eagerness to do the same with AI-enabled tools for analysis, documentation, prototyping, and verification. Prior experience building AI or machine-learning systems is not required; sound judgment about when to use these tools and how to validate their output is. * Reliability & test methodology. Working knowledge of DFMEA, DVP&R, root-cause analysis, and structured V&V planning, applied across hardware and software. * Domain background. Robotics, sensors, tactile sensing, or dexterous manipulation experience is a strong plus; broader electromechanical and embedded-software product backgrounds (automotive, medical device, consumer electronics) are also welcome. * Collaboration style. Track record of earning trust and technical authority across engineering teams without formal reporting lines. ## Description * Own system requirements. Write and maintain System Requirements Specifications (SRS) and Interface Control Documents (ICD) across mechanical, electrical, firmware, software, and sensor sub-systems. * Lead architecture trade studies. Drive cross-disciplinary decisions (e.g., packaging approach, thermal/mechanical/electrical budget allocation, whether a fix belongs in firmware or host software) where sub-system optima conflict. * Own the hardware-software boundary. Define and maintain the interfaces between sensor/electrical hardware and the software stack that consumes it (calibration, signal processing, drivers/SDK, data formats), so hardware and software teams build to the same contract. * Drive verification & reliability. Own the V&V plan and FMEA process across the product lifecycle (EVT / DVT / PVT), and translate failure risk into design and test requirements - including software and firmware failure modes. * Bridge prototype to production. Identify manufacturability, yield, and process risks before they surface at scale; partner with process/fab and contract manufacturing partners. * Interface with external partners. Define and negotiate system-level interfaces - hardware and software/API - with external collaborators and customers integrating our solutions. * Build the practice. Establish lightweight systems-engineering tooling and documentation standards (requirements traceability, review gates) suited to our team's size and stage. * ## Related Videos - [Playing Pong on a shoulder press machine](https://www.wearedevelopers.com/videos/100140-playing-pong-on-a-shoulder-press-machine) - [10M Data Records Lost, Underwater Computing, and Psychedelic Fish - Matthias Geniar](https://www.wearedevelopers.com/videos/1908-10m-data-records-lost-underwater-computing-and-psychedelic-fish-matthias-geniar) - [More efficient software for more efficient microchips](https://www.wearedevelopers.com/videos/1164-more-efficient-software-for-more-efficient-microchips) - [Develop on Windows, Deploy on Red Hat Enterprise Linux](https://www.wearedevelopers.com/videos/1600-develop-on-windows-deploy-on-red-hat-enterprise-linux) - [The Software Engineer 2030: From Coder To AI Orchestrator? - Patrick Schnell](https://www.wearedevelopers.com/videos/1825-the-software-engineer-2030-from-coder-to-ai-orchestrator-patrick-schnell) - [Agent Smith Gets Hardware: Autonomous IoT Hacking From Debug Port to Cloud API](https://www.wearedevelopers.com/videos/100258-agent-smith-gets-hardware-autonomous-iot-hacking-from-debug-port-to-cloud-api) ## Related Articles - [How software is steering vehicle technology](https://www.wearedevelopers.com/magazine/515-how-software-is-steering-vehicle-technology) - [How to Become an AI Engineer](https://www.wearedevelopers.com/magazine/331-how-to-become-an-ai-engineer) - [Top Characteristics of a Software Engineer](https://www.wearedevelopers.com/magazine/166-top-characteristics-of-a-software-engineer) - [What is Software Engineering?](https://www.wearedevelopers.com/magazine/289-what-is-software-engineering) - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [Never delegate the understanding](https://www.wearedevelopers.com/magazine/749-never-delegate-the-understanding)