Only External Postings
Embedded Software Engineer
About this role
Blueprint seeks an Embedded Software Engineer to design and develop automated firmware security analysis platforms using compiler technologies, fuzzing, and AI-assisted workflows. You'll build scalable tools that transform firmware into analyzable intermediate representations and automate vulnerability discovery across complex security challenges.
What you'll do
- Design and maintain automated firmware security analysis pipelines for vulnerability detection
- Build low-level tooling with C++, Python, and LLVM to analyze firmware at scale
- Develop compiler passes to convert firmware into LLVM Intermediate Representation (IR)
- Create and optimize fuzzing harnesses to maximize code coverage and uncover vulnerabilities
- Debug firmware rehosting environments and resolve automated analysis issues
- Collaborate with compiler engineers and security researchers to validate findings and review architectures
What they're looking for
- C++ and Python programming
- LLVM compiler technology
- Firmware security analysis
- Fuzzing frameworks and test harness development
- Systems programming and low-level debugging
- Machine learning/AI-assisted security workflows
- CI/CD pipeline design
- Root-cause analysis and vulnerability assessment
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Only External Postings
Blueprint builds enterprise data and cloud infrastructure solutions, with a focus on data pipelines, analytics systems, and secure cloud operations. The company is hiring data engineers, software engineers specializing in scientific computing and AI, and DevSecOps engineers to develop and maintain these systems.
View all jobs at Only External PostingsLikely interview questions
- Walk us through your experience developing compiler passes or LLVM-based tools—what challenges did you encounter?
- Describe a complex firmware security vulnerability you've analyzed; how did you approach the root-cause investigation?