Job Description & Details
This is a technical program management role where you'll actually need to understand the code, the stack, and the hardware-software boundaries. You won't just be updating Jira boards; you'll be driving low-level software integration alignments across RTOS, drivers, and network stacks while keeping cross-functional teams on track.
What You'll Actually Be Doing
You will spend your days bridging the gap between low-level engineering teams and executive stakeholders. Expect to dive into system designs, hunt down gaps between requirements and validation, and manage technical risks before they blow up delivery timelines. You'll herd cats across base software, hardware, and validation teams while maintaining absolute hygiene in Jira and translating nasty technical blockers into clear executive summaries.
The Core Tech Stack
You need a solid grasp of low-level software integration, RTOS, middleware, network stacks, and cybersecurity modules. While you won't necessarily be writing the C/C++ drivers yourself, you must be dangerous enough to follow complex technical arguments, understand FuSa (Functional Safety) requirements, and challenge engineers when their timelines sound wildly unrealistic.
Interview Expectations
Be ready for a hiring manager who will test your ability to dive into the weeds while maintaining a bird's-eye view. They'll likely ask you to explain how you've previously untangled a critical dependency deadlocked between a hardware team and a safety-critical software validation team. They want to see if you can actually technical-wrangle without hiding behind Agile buzzwords. Another favorite will be asking you to take a deeply complex architectural failure—like a real-time OS memory leak—and explain its impact to a room of non-technical VPs without losing them.
Application Advice
Don't just send a generic project management resume that lists standard Scrum Master certifications. Your CV needs to scream technical depth in embedded systems, networking, or cybersecurity. Make sure keywords like RTOS, low-level drivers, FuSa, risk impact analysis, and cross-functional alignment are prominent so you can easily clear the ATS and prove to the recruiter that you speak developer.