Senior Software Engineer - B2B Tribe

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 hard part is not only writing the code, but figuring out what is worth building in the first place ?

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 ticket-taking role.

I’m looking for a senior engineer who wants to get close to the business problem, challenge proposed solutions when needed, choose the right level of investment, 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.

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 engineers who ask questions before building. We like prototypes when they help us learn faster. We like clean systems when the problem deserves long-term investment. We like boring, reliable software when reliability matters more than cleverness.

We also like AI and automation, but not as decoration.

AI is useful when it removes repetitive work, speeds up decision-making, improves internal workflows, or helps engineers increase their own leverage. If you are already using tools like Copilot, Claude, CLI agents, MCP workflows, or custom automations to work differently, you’ll probably enjoy this environment.

The goal is not to put AI everywhere. The goal is to use modern tools intelligently to solve real problems.

The technical stack used by the team

In the Growth & GTM team, we mainly work with:

• Node.js, TypeScript, React, GraphQL => minimum requirement.
• PostgreSQL, Elasticsearch.
• DBT, AWS Glue, Hightouch.
• Datadog, Grafana.
• GitHub Copilot, Claude, AI CLI tools, MCP workflows.

Across TheFork, you may also interact with Kubernetes, AWS, RabbitMQ, and some legacy PHP/Symfony services.

You don’t need to have used every tool already. Strong technical foundations, curiosity, and fast learning matter more than exact stack matching.

You Must Meet These Critical Qualifications

I’m not looking for someone who has already worked on every topic listed above.

I’m looking for someone with strong engineering foundations, good product judgment, curiosity, and enough pragmatism to know when to build properly and when to test something quickly.

You might be a good fit if:

• You are a senior backend or full-stack engineer.
• You have experience building reliable web applications, backend services, APIs, or distributed systems.
• You care about product and business impact, not only technical output.
• You are comfortable with ambiguity.
• You can take a loosely defined problem and turn it into shipped software.
• You enjoy working with Product, Data, Sales, Customer Success, Customer Care, and Operations.
• You are curious about AI, automation, agents, CLI tools, and modern engineering workflows.
• You care about reliability, maintainability, security, observability, and user trust.
• You communicate clearly in English.

Put another way: I’m looking for someone who gets energy from turning messy growth or operational problems into simple, useful, measurable software.

You Can Impress With These Additions

You may not enjoy this role if:

• You prefer fully specified tickets.
• You want to focus only on implementation.
• You are not interested in AI, automation, or changing how work gets done.
• You think internal tools are less valuable