🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
This role is part of a team focused on building and securing foundational firmware and boot software for embedded platforms and SoCs. They will lead the design, development, and hardening of secure boot and Root of Trust capabilities, while enabling a reliable and secure firmware-to-OS stack across early bring-up and production releases. The role works closely with hardware, software, and validation teams across geographies to define firmware architecture, troubleshoot complex platform issues, and deliver high-quality SDK collateral. This position has a direct impact on platform security, product readiness, and the overall quality of embedded system deployments. What you ll do: - Design, implement, and maintain production-quality secure boot and Root of Trust solutions for embedded platforms and SoCs. - Enable and harden the boot and firmware stack, including boot flow, early platform initialization, and U-Boot. - Drive OS-level security enablement through Linux kernel and BSP integration, Device Tree updates, reserved memory definitions, firmware interfaces, and secure/non-secure boundary design. - Develop and debug platform security components and low-level drivers, including crypto accelerators, key services, secure storage, lifecycle and provisioning flows, anti-rollback mechanisms, and attestation hooks where applicable. - Lead firmware architecture definition by working with geographically distributed stakeholders to gather requirements and translate them into scalable embedded system designs. - Perform hands-on platform bring-up, system-level debugging, and root-cause analysis across FPGA, emulation, early-silicon, and production environments. - Deliver security collateral as part of SDK releases, including integration support, validation, bring-up and debug guidance, known issue tracking, and release readiness documentation. - Design and implement firmware solutions that meet system requirements, quality standards, and coding best practices. - Partner closely with hardware engineers, software developers, and QA teams to ensure cohesive, reliable, and secure product development. - Create and maintain clear technical documentation for firmware architecture, design decisions, implementation details, and developer usage. What you ve done: - Earned a B. E. /B. Tech or M. E. /M. Tech in Computer Engineering, Electrical or Electronics Engineering, or a related field. - Built 15+ years of experience in low-level firmware or boot software development, including deep expertise in secure boot and Root of Trust implementation on SoCs. - Demonstrated expert-level proficiency in C programming and robust experience working with low-level firmware and kernel-adjacent code. - Applied strong knowledge of Linux internals, including boot flow, memory management, MMU fundamentals, privilege and isolation concepts, and system-level debugging. - Gained hands-on experience with SoC and platform bring-up, with strong ownership of boot-stack quality, reliability, and security. - Worked extensively with U-Boot, the Linux kernel, Device Tree, and build systems such as Yocto, Open Embedded, Rocky Linux, or comparable environments. - Used debugging tools such as GDB and at least one of OpenOCD, JTAG, Lauterbach, or similar platforms to diagnose and resolve low-level issues. - Supported bring-up and validation on FPGA, emulation, or early-silicon platforms. - Worked with hardware communication protocols such as UART, SPI, and I2C. - Brought additional value through experience in pre-silicon or FPGA validation, post-silicon boot and security debug, and triage of complex platform issues. - Developed familiarity with platform security building blocks such as secure boot, secure storage, lifecycle and provisioning, anti-rollback, attestation, and firmware and OS trust boundaries. - Gained exposure to Broadcom and Marvell SDK environments. Who you are: - They are a hands-on firmware engineer who is comfortable working close to the hardware and solving complex system-level problems. - They bring a strong sense of ownership and accountability for platform security, code quality, and release readiness. - They communicate clearly and document thoroughly, making complex technical concepts accessible to both internal and external audiences. - They collaborate effectively with cross-functional and globally distributed teams to drive alignment and execution. - They approach development with rigor, applying coding standards, debugging discipline, and architectural thinking to every stage of the product lifecycle. Disclaimer: This job posting has been aggregated from external source. Role details, content, and availability are subject to change. Applicants are advised to confirm the latest information directly on the company website before applying. .
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.