Embedded Software Engineering Manager

Location: Antwerp or Amsterdam

Experience: 5+ years in embedded software development, including 2+ years managing embedded or firmware engineers

Lead the firmware that makes our earwear smarter

Loop’s portfolio is growing across connected and standalone products. Behind every one of them is firmware that has to work flawlessly, from the first board bring-up to mass production and every update after that.

As our Manager, Embedded Software Engineering, you’ll lead the team that makes that happen. You’ll own how firmware gets engineered across Loop’s products, from development and launch through sustaining releases in the field. That includes how the team works: as AI capability moves, you’ll change how the whole team designs and verifies firmware, and set the standard for how AI is used.

This role is for someone who is equally comfortable growing engineers and challenging a firmware design on its merits. You’ll set the standard, build the team, and make sure what we commit to actually ships, on time and at quality.

The Role

You’ll lead embedded software across Loop’s connected and standalone products, owning predictable delivery, engineering quality, and team capability.

You’ll combine technical credibility with people leadership. Product defines what we build, Programme Management defines when it lands, and you define how it’s engineered. That includes the engineering practices of the discipline. You’ll set coding and review standards, and you’ll also keep reshaping how the team designs, develops, and verifies firmware as AI tools mature. Detailed architecture and subsystem design authority stay with our senior engineers, and part of your job is growing them into that technical leadership.

While the team is small, you’ll stay hands‑on where it matters. As the team grows, you’ll delegate more, while making sure you never become the critical‑path dependency.

What You’ll Do

• Lead, coach, and develop a team of embedded software engineers, setting clear level‑referenced expectations and addressing performance early.
• Plan workforce, capacity, tooling, rigs, fixtures, and lab resources to meet commitments, managing priorities and costs within Loop’s approval policy.
• Own firmware delivery across development and sustaining work, including bring‑up, manufacturing and test firmware, launch readiness, field issues, security updates, and sustaining releases.
• Ensure clear ownership and acceptance evidence for factory firmware, flashing, provisioning, and version compatibility.
• Estimate and resource work, surface risk early, and own release readiness decisions, including rollout, pause, and rollback.
• Maintain strong engineering standards across coding, review, testing, CI, hardware‑in‑the‑loop (HIL), security, and traceability, working within Loop’s Requirements and Risk Management Frameworks.
• Set the team’s standard for how AI is used in firmware development and verification, with clear guardrails for quality, security, and traceability in a hardware‑dependent environment.
• Represent embedded software in programme, design, build‑readiness, and sustaining forums, owning firmware estimates, dependencies, risks, and readiness judgement.
• Drive cross‑system decisions with Engineering, Quality, Industrialisation, suppliers, silicon vendors, and manufacturing partners.
• Lead architecture and design reviews that reach a conclusion on trade‑offs, and translate roadmap objectives into clear technical direction.

You won’t

• Commit to milestones without the resourcing and risk picture to back them up.
• Let a slip surface on the milestone date instead of before it.
• Take design authority away from the senior engineers who own it.
• Become the bottleneck your team has to wait on.
• Treat manufacturing and test firmware as an afterthought.
• Let a field defect sit without a severity, a root cause, and a decision.
• Leave performance conversations for later.
• Stay quiet in a cross‑functional forum when firmware has a risk to raise.

How You’ll Succeed

You deliver what you commit to. Firmware milestones land within the agreed window, and when something does slip, people hear it from you early. Manufacturing and test firmware is locked ahead of every design‑validation build and stays that way. Critical defects don’t reach production, and every issue reported from the field gets triaged within a sprint with a clear decision to fix or accept it.

Your team gets stronger with you. Every critical subsystem has a second engineer who knows it, every engineer has a development plan, and new joiners have their first contribution reviewed and merged within four weeks. People want to stay and grow here. The way the team engineers keeps moving too. As AI capability d