Job Opportunities API

Join our Movement and Champion Restaurant Culture! 💚   At TheFork we believe that the best things in life happen around the table. As the leading restaurant booking platform in Europe, we connect the broadest community of loyal diners with the world’s favorite restaurants. Powered by innovation and a deep passion for the restaurant industry, we create unique dining experiences across 11 countries. We’re part of the Tripadvisor Group and proud to be building a diverse, people-first culture where “respect”, “ownership”, “growth” and “better together” values thrive. If you’re passionate about food, technology, and making a real impact, your seat at the table is ready.  👉 Discover life at TheFork Hey 👋 I’m Pierre, and I’m building the Growth & GTM engineering team at TheFork. How do you feel about engineering roles where the job is not only to write code, but also to understand why we are building something and how it can create real impact? At TheFork, we help restaurants grow, manage demand, and connect with millions of diners across Europe. That sounds simple. In reality, there is a lot of complexity behind it. Restaurants need to onboard faster. They need to understand the value of our products. They need better data to make better decisions. They need software that reduces friction instead of adding more. Internally, our Sales, Customer Care, and Moderation teams are looking for modern tools and AI that solve real problems, making sure that actual leverage always comes before the trend. That’s where this team comes in. 💚 The Growth & GTM engineering team exists to unlock leverage across B2B growth and operational efficiency. Sometimes that leverage is a product feature. Sometimes it is an internal tool. Sometimes it is a data workflow. Sometimes it is an AI-powered automation, an MCP workflow, or a CLI-based prototype. And sometimes, the best engineering decision is to not build anything until we better understand the problem. This is not a role where engineers only receive tickets and implement them in isolation. I’m looking for an engineer who wants to get close to the business problem, understand the product context, contribute to technical decisions, ship reliable software, and learn from production. Someone who wants to be close to the problem, not just close to the code.   What you will do You’ll work on problems that sit at the intersection of product, engineering, data, operations, and AI. A few examples: Helping restaurants activate faster and get more value from TheFork. Improving monetization, upsell, product discovery, or referral loops. Exposing useful data and recommendations to restaurants or internal teams. Automating repetitive workflows for Customer Care, Sales, Moderation, or Operations. Building internal tools that help teams move faster without adding more process. Prototyping AI agents, MCP workflows, CLI-based automations, or internal copilots. Reducing operational costs by turning fragmented data and manual work into reliable systems. Some of these projects will be clean product features. Some will be scrappy prototypes. Some will require going deep into existing systems. Some will start with a messy business problem and no obvious solution. You won’t be expected to solve everything alone. You’ll work with experienced engineers, Product, Data, and business teams to understand the problem, contribute to the solution, and grow your ownership over time. That’s the job.   How we think about engineering We care about impact, but not in a vague “move metrics” way. We care about software that changes something real: a restaurant activating faster, a sales team saving time, a support workflow becoming simpler, a moderation process costing less, or an internal team making better decisions because the right data is finally available. We like engine