Lead Software Engineer
Il y a 8 heures
Arrondissement of BrusselsCapital, Brussels, Belgique
Portage Ventures GP Inc.
Temps plein
Gratuit avec email ou Google
Enregistrez cette offre et organisez votre recherche
Créez un compte gratuit pour enregistrer des offres d'emploi, créer des alertes et revenir à cette liste depuis votre tableau de bord.
Gratuit avec email ou Google
ph3Who we are : /h3 pWe’re Qover, a leading insurtech scale-up that has raised $70 million. /p pWith an international team of 160+ colleagues based in Brussels, we help companies orchestrate digital embedded insurance experiences. /p pSince Qover was founded in 2016, our co-founders had a clear vision of the future of insurance: it must be simple, transparent and accessible across borders – a global safety net . /p pWe’re well on our way to building that safety net, with a platform that protects millions of users across 32 European countries. We work with top brands like Revolut, Mastercard, BMW, Canyon, Monzo and many others. /p pVisit our website for more about what we do /p h3The Opportunity: Your Next Big Leap /h3 pAs a Lead Software Engineer, you will lead one of our 5 product engineering teams as a people leader and technically credible player-coach. Accountable for your team’s delivery, technical quality, production ownership, and growth, you will partner closely with Product and Design. You will stay close to the code, the customer problem, and operational reality. /p pYou will initially lead a core product engineering team (e.g., our Policy Management Platform or another strategic domain). You’ll help power embedded insurance experiences used by top global brands. /p h3Lead the Charge: AI-Assisted Engineering /h3 ul libCultivate a thoughtful AI culture: /b Use agents intentionally for implementation, debugging, and documentation. /li libEstablish responsible guardrails: /b Maintain rigorous human review, testing, and ownership of AI-generated output. Manage data sensitivity. /li libCoach for excellence: /b Emphasize strong technical specs and recognize when human judgment outweighs automation. /li libMeasure what matters: /b Focus on outcomes like reduced toil and improved delivery flow over simply tracking tool adoption. /li libScale best practices: /b Collaborate with Principal and Platform engineers to refine reusable tooling across the organization. /li /ul h3Your Impact: What You’ll Do /h3 pYou will own engineering outcomes end-to-end, contributing from discovery and technical design through implementation, deployment, monitoring, and continuous improvement. /p h3Foster Talent Drive Delivery /h3 ul libChampion team execution: /b Partner with the PM to turn priorities into realistic plans with a predictable, high-quality shipping cadence. /li libCultivate engineering growth: /b Mentor and develop your team through consistent feedback, performance management, and dedicated coaching. /li libBuild a high-trust culture: /b Promote psychological safety and accountability. /li libCollaborative leadership: /b Work with fellow Engineering Leads to optimize cross-team workflows without unnecessary bureaucracy. /li /ul h3Stay Rooted in Technical Excellence /h3 ul libPlayer-coach mentality: /b Engage with the codebase for credible technical guidance—participating in designs, reviews, and incident resolution. /li libElevate the quality bar: /b Own standards for code quality, automated testing, security, observability, and maintainability. /li libOperational Resilience: /b Run and iterate on what you build, leading blameless post-mortems and fixing recurring debt. /li libPragmatic decision-making: /b Balance speed, security, and technical debt to deliver maximum product value. /li libLeverage expertise: /b Partner with Principal Engineers on complex missions while keeping daily technical ownership within your team. /li /ul h3Bridge Product and Engineering /h3 ul libStrategic partnership: /b Act as the PM's technical counterpart, collaborating on scoping and sequencing to prevent delivery surprises. /li libMeaningful discovery: /b Provide technical perspective to translate vague requirements into robust software solutions. /li libDesign alignment: /b Explicitly discuss usability and technical feasibility trade-offs with Designers. /li libTransparent communication: /b Articulate technical trade-offs to stakeholders, justifying decisions with a focus on practical outcomes. /li /ul h3Optimize the Ecosystem /h3 ul libEliminate friction: /b Reduce operational toil, recurring bugs, and unnecessary hand-offs. /li libChampion shared tooling: /b Integrate shared platform capabilities and security best practices. /li libEmpower autonomy: /b Help engineers become confident decision-makers, reducing reliance on any single individual. /li /ul h3Your Arsenal: The Skills You Bring /h3 ul libTechnical leadership and depth: /b 7+ years building and operating production systems. Strong engineering fundamentals. Hands‑on enough to guide design, review code, and solve complex problems. Qover’s platform relies on TypeScript, Node.js, React, and MongoDB, but we welcome leaders from ecosystems like Java, C#, Go, or Python. Experience with distributed systems and API design is key. /li libEngineering ownership: /b Responsibility for quality, security, maintainability, and operability. You provide high-signal code reviews. /l