Fullstack Software Engineer, Alan

• 8+ years building scalable software, with full-stack experience across backend and frontend
• A strong product mindset. You want to understand the why before the how, and you enjoy working with members, ops, legal and marketing
• Ownership from start to finish: you frame the problem, ship the solution, and watch the numbers afterwards
• Comfort with ambiguity and complex problems. You help shape the scope instead of waiting for a spec
• Clear communication with non-engineers, in English (French is a plus, since our first market is France)
• Humility, curiosity, and a real interest in making healthcare more accessible
• If you're excited about this opportunity but don't check every box, we'd love to hear from you. Everyone, no matter how underrepresented, should feel free to apply, as it can only bring learnings or success

Desirable

• We're looking for a fullstack engineer to join the Shop crew. One brief: help our members choose what is right for them, when it is right for them, in a few clicks. Everything else, we figure out together
• The Shop crew is a fully autonomous product team that owns the whole lifecycle of the Shop: not just the code, but the whole business. Product managers, product marketers, ops specialists, designers, data scientists and engineers work side by side on one mission
• What we've built so far:
• An end-to-end optics experience: frames and lenses, virtual try-on, prescription scanning, and checkout priced against each member's coverage
• One commerce platform behind the whole Shop and its three verticals
• A growing well-being catalog: about 14 brands and 170 products today, thousands soon
• The Shop is growing fast: more products, smoother flows, and an experience that's more and more integrated into the rest of Alan for our members. The crew needs to grow too, and that means plenty of new opportunities for engineers
• The Shop is one of the most varied crews in Alan Engineering. In the same week, you might:
• 🔌 Build integrations with our customized e-commerce back office, our in-house virtual try-on, suppliers and partner opticians
• ️ Ship member-facing flows: dynamic catalogs, purchase flows tailored to each member's coverage, prescription scanning, returns, and out-of-pocket purchases like lens upgrades and extra pairs
• 🌿 Scale the catalog beyond optics, with discovery and personalized navigation that still work at thousands of products
• ⚖️ Navigate legal ground: e-commerce rules, invoicing, France's 100% Santé reform, and supplier compliance. Selling medical devices is not like selling socks
• 📣 Help products reach members in the Alan app, in campaigns, and through Mo, our AI health assistant. A shop that can't promote its products is just a warehouse
• 📦 Work with ops on orders, deliveries and customer service, so a two-day delay never surprises a member
• You won't just write code. You'll question supplier contracts, debate marketing copy, and debug prescription-scanning logic. Some days it feels less like building software and more like running a small business. That's the point. And the impact is direct: when someone orders their glasses faster, they literally see better, sooner
• Our stack: React and React Native on the frontend, Python/Flask and PostgreSQL on the backend, all in one monorepo. Saleor powers our commerce back office
• We deploy daily, and the engineers who make product decisions are the ones who build them
• We use AI coding agents every day to move faster and focus on the hard problems
• You own decisions, outcomes and a whole domain, and your incentive is to build what's best for members
• In our engineering team, we build the infrastructure, interfaces, and applications to provide first-class service to our members, health professionals, and even ourselves!
• Being an engineer at Alan means joining a team of talented, committed and passionate engineers, with a lot of product interaction
• We move fast, with a lot of ownership, and are proud to tackle big problems!
• Our process is very simple: those who make product decisions are the same ones who build them
• Our stack is React, Python/Flask, PostgreSQL in a monorepo. If you are not familiar with this stack but are a keen learner, it is totally fine. We deploy daily and believe in distributed ownership - you build it, you own it