A complete application in a minute
Tailored resume and cover letter, ready to send.
L4B Software seeks a Principal Embedded Product Security Architect to lead security across Android/AOSP and regulated embedded Linux platforms in consumer electronics and medical devices. This is a hands-on engineering role focused on end-to-end security decisions from threat modeling to release.
You will collaborate with embedded teams to design secure boot, device identity, OTA updates, SBOM tracking and regulatory alignment, while delivering meaningful security implementations in production
L4B Software specializes in embedded software engineering, platform development and product cybersecurity. We work with Embedded Linux, Android/AOSP, board support packages (BSPs) and real-time embedded systems to develop reliable, secure and maintainable software platforms. Our engineering work supports industries including medical devices, consumer electronics and other connected embedded products where security must be integrated throughout the product lifecycle.
We are looking for a Principal Embedded Product Security Architect with strong hands‑on experience securing embedded devices and connected products, particularly in consumer electronics or medical-device environments. This is a hands‑on engineering position, not a general IT cybersecurity, SOC, network security or compliance‑only role. You will work directly with embedded software, platform and product‑engineering teams to design, implement, test and maintain security mechanisms across device hardware, bootloaders, operating systems, firmware and software‑update infrastructure.
We seek principal‑level engineers who have personally owned end‑to‑end security architecture and delivered substantial hands‑on security implementation into production embedded products, from threat identification and security decisions through release, monitoring, and lifecycle maintenance.
Serve as the accountable technical security architect for an Android/AOSP‑based mobile device platform, and a managed embedded Linux platform for regulated medical devices; own security decisions, risk acceptance recommendations, architectural reviews, implementation direction and release security readiness across both programs.
For the AOSP‑based mobile platform, establish and review an end‑to‑end Android platform security architecture covering verified/secure boot, hardware‑backed key protection and attestation, Android KeyMint/StrongBox where supported, SELinux policy, system‑service and HAL trust boundaries, device identity, production provisioning, secure OTA/rollback protection and vulnerability response.
For the regulated embedded Linux platform, own platform‑level security architecture and secure Linux baselines; lead threat and risk analysis, security hardening, boot integrity, secure communication and updates, SBOM/CVE monitoring, remediation, long‑term security maintenance, and security verification.
Deliver platform‑level cybersecurity evidence supporting IEC62304 and ISO14971 activities and applicable FDA cybersecurity expectations, working within L4B's ISO13485 quality management system. The medical device manufacturer retains responsibility for device‑level risk acceptance and regulatory approval.
Select threat modeling and risk assessment approaches based on the product and applicable requirements (e.g., STRIDE, TARA or other suitable methods); translate identified threats into prioritized architectural controls and documented engineering decisions.
Remain hands‑on: demonstrate prior personal implementation of meaningful embedded security controls and be capable of reviewing and debugging code, boot/security flows, platform configuration and verification evidence, while guiding AOSP, Linux, firmware and QA engineers.
Own product security from early architecture through integration, release, production maintenance and security incident/vulnerability response.
Do not treat penetration testing, governance or compliance work alone as a substitute for security architecture and implementation ownership.
Minimum 10 years of professional embedded or platform software engineering experience, with substantial hands‑on work in Embedded Linux, Android/AOSP, firmware, bootloaders or similar low‑level systems.
At least 5 years of direct, hands‑on embedded product cybersecurity experience designing, implementing and validating security controls in connected devices or other shipped embedded products.
At least 3 years of demonstrable technical leadership or ownership of product‑security architecture, including threat modeling/risk assessment, security requirements, design decisions, implementation oversight and verification through release.
Mandatory evidence: explain at least one real embedded product where the candidate was accountable for end‑to‑end cybersecurity decisions and personally implemented meaningful security controls.
General IT security, compliance‑only, penetration testing or advisory work alone does not satisfy this requirement.
Strong professional experience in embedded software engineering, with substantial hands‑on responsibility for embedded product cybersecurity.
Professional experience securing consumer electronics, medical devices or comparable connected embedded products.
Strong understanding of embedded hardware, firmware, bootloaders, operating systems and device security boundaries.
Hands‑on experience implementing security controls in Embedded Linux, Android/AOSP or comparable embedded platforms.
Demonstrated practical experience in several of the following: Secure Boot, Verified Boot or hardware root of trust.
Secure key storage, provisioning and cryptographic integration.
Embedded Linux security hardening.
Secure firmware updates and rollback protection.
Device‑level threat modeling and attack‑surface reduction.
Embedded vulnerability analysis and remediation.
Strong Linux debugging and embedded systems troubleshooting skills.
Proficiency in C/C++ and scripting with Python or Bash.
Ability to independently own technical security tasks from design through implementation and verification.
Experience working with cross‑functional product‑development teams.
Ideal background: 12–15+ years in embedded/platform engineering, with broad experience securing Android/AOSP and/or other embedded Linux devices and guiding product‑security delivery across multiple programs.
Direct experience with consumer electronics, connected devices, smart home products, multimedia devices, wearables or other commercially deployed embedded products.
Experience developing or securing medical‑device software, connected medical equipment or regulated healthcare products.
Practical experience with ARM TrustZone, OP‑TEE, TPM, secure elements or hardware security modules.
Experience with Yocto/OpenEmbedded, U‑Boot, Linux kernel configuration and BSP security integration.
Android Verified Boot (AVB), Android security architecture or SELinux policy development.
Secure OTA frameworks and firmware‑signing infrastructure.
Experience with SBOM tooling, CVE assessment and software composition analysis.
Familiarity with applicable product‑security standards and guidance, such as IEC62443, ETSIEN303645, IEC81001‑5‑1, IEC62304, ISO14971 or relevant EU Cyber Resilience Act requirements.
Experience supporting security verification, technical documentation and product‑security audits.
Experience working on products requiring long‑term security maintenance and vulnerability response.
We are particularly interested in engineers who can demonstrate: Security mechanisms they have personally designed, implemented, integrated or validated.
Experience working with actual embedded products rather than security concepts alone.
Understanding of how hardware, firmware, operating systems and connectivity affect device security.
Ability to investigate vulnerabilities and implement practical remediation.
Ownership of technical decisions and security deliverables.
Clear communication with embedded engineering and product teams.
Important: This position requires practical embedded product‑security engineering experience. General IT security, SOC operations, infrastructure security, penetration testing without embedded‑product engineering, or compliance‑only experience will not independently meet the role requirements.
Work on embedded platform and product‑security engineering challenges. Contribute to secure software platforms used in complex connected products. Collaborate with international engineering teams. Take ownership of meaningful security design and implementation responsibilities. Work in an environment where technical depth, independent problem‑solving and engineering quality matter.