Forward Deployed Engineer - FRA

Title: Forward Deployed Engineer - FRA Location: Paris, IDF, FR / Paris, Île-de-France, FR / Remote (US) Junior / early career. San Francisco. _"Hire people who make you never want to hire 'normal' people again." — Brian Chesky_ Every sales team has the same problem: find the right companies, qualify them, get there before anyone else. But no two teams solve it the same way - a rep at L'Oréal qualifies a lead nothing like a rep at Deel. Same problem, completely different workflow. Generic tools hand everyone the same generic workflow, which is exactly why every team using them plateaus in the same place. Leadbay qualifies leads for agentic workflows. Teams at L'Oréal, Saint-Gobain, Gerflor USA, Corgi, and Nespresso B2B have 3x'd their addressable market and 10x'd what they defined as a qualified lead. Those numbers are real because someone sat with each of those teams and built their specific workflow. Not a template. Theirs. Right now that someone is a founder. That is the bottleneck, and it is the entire reason this job exists. We raised $4.3M to become the first billion-dollar MCP-native company (Model Context Protocol) - and you'll build daily alongside the founders, [Ludo](LUDO_LINKEDIN_URL) (previous US investor in Startup who’ve worked with hundreds of CEOs) and [Milan](MILAN_WEBSITE_URL) (PhD in making AI work with limited data, exited Sepage to Travelsoft). **Founders' view on the role** One loop, four steps: Land → Listen → Ship → Expand. You land the account after signature. Signature is not success. Success is the day their reps open Leadbay before their CRM. You listen to what actually happens inside the account. Not what the customer requests on a call. What they do, where they hesitate, which lead they skipped and why. You ship. Specific skills, widgets, artifacts, lenses, qualification prompts, imports, connectors, prospecting agents - all powered by Leadbay AI. Power users start using them; some work, some don't; and suddenly you hit a 10x that couldn't be done before. That's when you help expand, and it compounds at company scale. Along the way, you build your own knowledge that helps the next account go 5 to 10x too. Some of it lives in one account forever. The best of it graduates into the product. Whatever the account size, you're always in front of the person who owns growth: a CEO, a C-level, a Head of. And no two weeks look alike. **What you'll do** * Land small accounts in 30-minute calls, and show them how to build what couldn't be done before. * Land large accounts over days in their offices, understand their growth strategy, and build the workflow with them. * Build everything that needs building inside our MCP product and MCP acquisition funnel. * Use your own MCP to become a living example of the most efficient sales rep in the world. * Here's what your first 30 / 60 / 90 days look like: 30 days meeting as many self-serve users as you can and shipping as many agentic systems as possible; 60 days building your library of what works; 90 days building your own skillset and walking into the offices of much bigger customers. **Who you are** Technically capable and socially skilled. Both. Not one. You can be in a room with a VP of Sales at 9am and writing Python at 2pm, and you're not faking either one. You probably have nothing on your CV that predicts success here. No FDE title, maybe not the right degree, maybe not much work experience at all. We care about what you've built and how you think. You spend evenings building AI skills, vibe-coding side projects, testing new tools, figuring things out because you enjoy it. You're usually the first person you know to try the new thing. You'd rather ship something hacky that works today than something clean next month. You're comfortable saying "I don't know, let me go find out" in front of a customer. Leadbay is part of a much bigger career journey (most likely toward becoming a YC founder). Ludo, Milan, and the broader YC ecosystem will help you grow fast. We're not a great fit for people who need to be told exactly what to do, struggle to make judgment calls, wait for constant validation, or care more about "whose fault is it?" than "how do we make it work?" We work low-overhead. One weekly team coordination meeting, everything else in service of doing the work. GitHub Projects, weekly iterations, English.