Principal Firmware Engineer
Microsoft (company site, opens in a new tab)14+ yrsNoidaOn-siteDirect career pageEst. 45–70 LPA
Posted 6d ago
Reach people at Microsoft
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at Microsoft you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Own end-to-end firmware security design and implementation for Azure server and rack hardware, from pre-silicon and post-silicon development through data-centre deployment.
- Define security-feature flows across platform subsystems, develop threat models with vendors and security teams, and maintain scalable firmware architecture.
- Lead system-level debugging and cross-team execution; contribute to long-term product roadmaps and mentor engineers.
Minimum Requirements
- Work Experience Required: 14+ years of professional firmware development experience.
- Bachelor’s degree or higher in Computer Engineering, Computer Science, Electronics Engineering, or a related field.
- Hands-on programming experience in C and RTOS.
- Demonstrated hardware and firmware architecture, design, and coding for solutions at scale; experience leading large initiatives across teams and influencing product roadmaps.
Ideal Candidate Profile
- A senior firmware engineer experienced across the product lifecycle, including SoC or platform bring-up, system-level debugging, and deployment at scale.
- Strong fit for cloud infrastructure security work involving hardware, firmware, and cross-subsystem security requirements.
- Additional relevant strengths include security protocols and cryptography, threat modelling or vulnerability assessment, supply-chain security, and low-level platform or peripheral development; these are preferred, not stated as mandatory.