Forward Deployed Engineer

About Fate Labs

Writing code is only part of engineering. Understanding a codebase, carrying decisions forward, and knowing whether a change works are just as important. We’re building Estelle to bring that work into one place.

Our goal is a software factory where agents and engineering teams can build on shared repository context, memory, review, and production feedback. There are hard problems across systems, product design, and how people work with agents. We’re a small team in Toronto, and we’re looking for people who want to take those problems on with us.

About the role

As a Forward Deployed Engineer at Fate Labs, you’ll work where the product meets a customer’s codebase. You’ll learn how a team develops software, find the work Estelle can help with, and build the integrations and workflows that make it useful in their day-to-day engineering.

This is a hands-on engineering role. You might spend one day tracing a repository indexing failure, another connecting an agent to a team’s tools, and the next turning a recurring deployment problem into a product improvement. You’ll work closely with the people building Estelle and help decide which problems we solve next.

Languages and tools

You’ll primarily write Python and TypeScript or JavaScript for integrations, scripts, and small applications. Expect to work with HTTP APIs, JSON, OAuth, Git, and command-line tools, and to use SQL when investigating how an integration reads or stores data.

You’ll work with Estelle, GitHub repositories and pull requests, and coding-agent environments such as Claude Code, Codex, or Cursor. Customer codebases will vary, so being able to read an unfamiliar stack and trace a problem across system boundaries matters.

What you’ll do

• Work directly with engineering teams to understand their repositories, development tools, and the constraints that shape how they ship.
• Build and debug integrations across code repositories, agent harnesses, APIs, and the systems a customer already uses.
• Take a deployment from initial setup to a working workflow, checking permissions, data boundaries, and failure cases along the way.
• Investigate problems from the underlying evidence: read the code, reproduce the issue, and trace what actually happened.
• Turn repeated customer problems into fixes, documentation, and setup patterns that the next team can use.
• Bring clear feedback to the product team, including what customers are trying to do, what gets in their way, and how we can tell a change helped.

What you should be comfortable building

• An API integration that authenticates correctly, handles pagination and rate limits, and recovers from a failed request without losing or duplicating work.
• A small Python or TypeScript service, script, or workflow that connects a customer’s repository and development tools to Estelle.
• A reproducible debugging setup: useful logs, a failing test or example, a clear explanation of the cause, and a fix another engineer can verify.

What you’ll bring

• You can build and troubleshoot software in Python, TypeScript, or another language you know well, and can explain the decisions behind your code.
• You’re comfortable working across unfamiliar codebases, APIs, authentication flows, and deployment environments.
• You listen carefully, ask useful questions, and can explain technical tradeoffs to both engineers and the people working alongside them.
• You can take an ambiguous problem, break it into testable steps, and keep moving without waiting for a complete specification.
• You care about whether an integration keeps working after the first successful demo.

Experience that would help

• Previous work as a software engineer, forward deployed engineer, solutions engineer, technical consultant, or developer supporting other engineering teams.
• Experience taking an API integration or internal tool from initial setup into regular use, including authentication, deployment, and support after launch.
• Hands-on work with CI/CD, webhooks, SQL databases, or production logs and monitoring.
• Experience helping a customer or another team adopt a technical product, with examples of the code you wrote and the problems you resolved.