Get a reply from this employer
Your resume and cover letter, tailored to exactly what they’re hiring for.
L4B Software is seeking a Senior Embedded Systems Validation & QA Lead to own the verification strategy for Android/AOSP and Embedded Linux platforms. Collaborate with Android, Linux, BSP, DevOps, and cybersecurity teams to embed validation into the platform lifecycle.
You will drive architecture for test automation, define coverage, and ensure evidence-based readiness for releases across hardware and software boundaries.
This isn't a role where you simply execute someone else's test plan.
Before You Apply
This is a remote, full-time employment opportunity. We are not considering B2B, freelance, independent-contractor, or consulting arrangements for this position.
L4B Software is an embedded software and platform-engineering company headquartered in Munich, Germany, with an engineering presence in Pune, India. We design, customize, integrate, secure, and maintain operating-system platforms based on technologies such as Embedded Linux and Android/AOSP, tailored to the specific hardware, product requirements, security needs, and lifecycle expectations of our customers.
Our engineering capabilities span: Customized Embedded Linux | Android/AOSP | BSP & Platform Integration | Cybersecurity | DevOps | System Validation.
Our work supports demanding and long-lifecycle products across medical technology, automotive, industrial systems, and other embedded environments where reliability, security, maintainability, and long-term support matter.
Our engineers work deep within the platform — from BSP and hardware integration through OS customization, platform security, system services, build and deployment infrastructure, and validation. The result isn't simply software running on an operating system. The customized operating-system platform itself is part of what we engineer and deliver.
We are looking for a Senior Embedded Systems Validation & QA Lead to own and evolve the verification and validation strategy for L4B's Android/AOSP and Embedded Linux operating-system platforms. This is not a traditional manual QA role. You won't simply receive a finished product and execute predefined test cases.
You will help define: What needs to be validated. How it should be validated. What should be automated. What requires physical hardware. What evidence must exist. And when a platform is genuinely ready for release. You will work closely with Android/AOSP, Embedded Linux, BSP, DevOps, cybersecurity, and other engineering teams to build validation into the platform-development lifecycle.
This role combines technical validation, test architecture, automation strategy, engineering judgement, quality ownership, and technical leadership.
Define verification and validation strategies for Embedded Linux and Android/AOSP platforms.
Translate technical and product requirements into structured platform-level test strategies and test plans.
Establish requirements-to-test traceability.
Define meaningful test coverage and identify validation gaps.
Build regression strategies that evolve with the platform and product.
Define measurable release-readiness criteria and quality gates.
Review validation results and assess release risks.
Establish the evidence required before platform releases.
Ensure critical defects, known limitations, residual risks, and validation gaps are visible before release decisions.
Provide clear, evidence-based recommendations on platform readiness.
Determine which validation should run automatically within CI/CD and which requires physical devices or dedicated lab environments.
Guide and contribute to test automation using Python and appropriate test frameworks.
Integrate automated validation into engineering workflows.
Build reusable validation frameworks rather than one-off test scripts.
Improve repeatability, test efficiency, and early defect detection.
Support Android CTS, VTS, and platform-specific validation.
Coordinate Embedded Linux and BSP validation.
Coordinate functional, integration, regression, security, and hardware-dependent testing.
Support validation across operating-system, BSP, hardware, networking, security, and system boundaries.
Help investigate complex issues where the visible failure may originate in another layer of the platform.
Establish structured defect-management and technical-triage processes.
Improve traceability between requirements, tests, defects, fixes, and validation evidence.
Define and monitor meaningful test coverage.
Produce clear technical validation reports and release evidence.
Continuously improve L4B's validation methodology, tooling, and engineering practices.
Drive reusable validation approaches across projects and platforms.
Mentor engineers involved in verification and validation activities.
Challenge weak test assumptions and incomplete coverage.
Coordinate validation across multiple engineering disciplines.
Work with engineering teams to ensure validation is considered during development — not only at the end.
Help build a culture of quality ownership across engineering rather than quality being solely the responsibility of QA.
We're looking for someone who understands that validating a complex embedded platform is fundamentally different from testing a web or mobile application. You should bring: Strong professional experience validating embedded systems, operating systems, firmware-connected products, or complex software platforms. Experience designing verification strategies and comprehensive test plans. Strong understanding of integration, system, and regression testing. Experience building, implementing, or guiding automated testing. Strong Python and/or scripting capability. Experience integrating validation into CI/CD pipelines. Strong defect investigation and root-cause-analysis skills. Experience establishing and maintaining test evidence and requirements traceability. Ability to understand and investigate failures spanning multiple technical layers. Experience coordinating validation across different engineering disciplines. Strong technical judgement and communication skills. Ability to assess platform readiness based on coverage, evidence, defects, and risk rather than simply test-pass percentages.
Most importantly, you should be comfortable moving beyond: Did the test pass? to: Have we tested the right thing, under the right conditions, with enough evidence to trust this release?
You see a green CI pipeline and still ask: What haven't we tested? You know that some failures only appear on physical hardware. You understand that hundreds of test cases mean little if they don't trace back to meaningful requirements, interfaces, risks, and expected behaviour. You can work with Android, Linux, BSP, DevOps, cybersecurity, and hardware engineers and understand enough across those disciplines to build an effective validation strategy. When a defect appears at one layer, you're willing to investigate whether the actual cause sits somewhere else in the system. And when someone asks: Can we release? You don't answer based on instinct. You answer based on coverage, evidence, defects, risk, and engineering judgement.
This is not a conventional manual QA position focused primarily on executing predefined test cases.
It is also not primarily: Web application testing Mobile application/UI testing Manual functional testing Test-case execution without platform ownership We are looking for someone who can operate at the embedded system/platform level and influence how validation itself is designed.
This role offers something different from a conventional QA leadership position. You'll work close to operating systems, hardware, cybersecurity, DevOps, and embedded product engineering rather than being separated from engineering at the end of the development lifecycle. You'll have the opportunity to influence how validation is designed, not simply how tests are executed. You'll work on technically demanding platforms where validation can involve real hardware, operating systems, BSPs, security, automation, CI/CD, and long-term product reliability. And you'll have meaningful ownership in strengthening how L4B answers one of the most important questions in engineering: Are we confident enough in this platform to release it?
We hire for capability, relevant experience, technical judgement, and demonstrated ownership. You don't need to match every technology listed above. If you have strong embedded or platform-validation experience, understand how to build validation systematically, and can work effectively across engineering disciplines, we'd like to hear from you. Equivalent practical experience is welcome where a formal degree isn't essential to the work.
Please note: We are not considering B2B, freelance, or independent-contractor arrangements for this position. If you believe quality should be engineered into the platform — not inspected into it at the end — we'd like to talk.