Senior Software Engineer, TheFork

• 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
• You don’t need to have used every tool already. Strong technical foundations, curiosity, and fast learning matter more than exact stack matching
• 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 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

Desirable

• 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
• 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