Staff Engineer Software

We are hiring for embedded software engineering with minimum 5 years of experience. Must have hands-on development in C or C++ for microcontroller platforms. Should be good with writing CI/CD pipelines for embedded software builds and tests (GitHub Actions or equivalent). Should be good with multiple MCU families or vendor ecosystems. Also must have strong exposure on Create, review, and maintain embedded software code examples, sample applications, and SDK documentation published on GitHub.

Your Role

Key responsibilities in your new role :

• Create, review, and maintain embedded software code examples, sample applications, and SDK documentation published on GitHub
• Set and enforce quality standards across repositories: working first-run examples, clear READMEs, consistent project structure, and Pipelines that pass
• Build and maintain CI/CD workflows (GitHub Actions) to automate build verification, test execution, and release management for embedded software content
• Engage with the developer community: triage issues, respond to questions, review community pull requests, and participate in technical discussions
• Work with internal engineering teams to surface their libraries, drivers, and tools in a way that developers outside the company can use
• Identify gaps in the content portfolio by monitoring what developers ask for, what fails, and what competitors do better
• Write technical content: getting started guides, migration guides, application notes, and tutorials aimed at practicing embedded engineers

Your Profile

Qualifications and skills to help you succeed :

• 5+ years of embedded software engineering experience, with hands-on development in C or C++ for microcontroller platforms
• Strong Git and GitHub proficiency: branching strategies, pull requests, Actions workflows, repository management, and community features (Issues, Discussions)
• Experience writing CI/CD pipelines for embedded software builds and tests (GitHub Actions or equivalent)
• A genuine developer relations instinct: you communicate technical concepts clearly, you respond to developer feedback constructively, and you find it satisfying when someone else succeeds with your work
• Familiarity with peripheral protocols and MCU ecosystems: you can read a datasheet, understand a BSP, and diagnose why an example is notworking on a given board
• Technical writing skills: you write documentation that engineers actually read
• Experience with multiple MCU families or vendor ecosystems (not just one platform)
• Python or shell scripting for tooling and automation
• Background in open-source contribution or community moderation
• Experience with package managers, SDK distribution, or software release workflows
• Familiarity with Zephyr RTOS, CMSIS, Free RTOS, or other embedded software frameworks
• Understanding of developer experience (DX) principles and what makes software platform easy or hard to adopt