GTM 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 GTM Engineer at Fate Labs, you’ll help connect the product we’re building with the engineering teams who need it. You’ll work with the founders on finding prospective users, learning how they develop software, and showing where Estelle fits into their workflow.

The role combines product understanding with practical commercial work. You’ll build outreach, run technical demos, support evaluations, and bring what you learn back to engineering. You’ll help develop a repeatable approach from the conversations and experiments you run yourself.

Tools and technical fluency

You’ll use Estelle, GitHub, and coding-agent environments to understand and demonstrate the product. Be comfortable opening a repository, working through an installation, making an API request, and explaining the steps of a developer workflow.

Python or JavaScript is useful for small demos, API scripts, and automating repetitive research or outreach tasks. You should also be comfortable organizing prospects and follow-ups in a structured pipeline, and using spreadsheets or SQL to investigate the results of an experiment.

What you’ll do

• Find and research engineering teams whose workflows could benefit from shared repository context, memory, and agent tooling.
• Write thoughtful outreach that starts with a specific understanding of the team and its work.
• Run product conversations and demos, ask good questions, and help prospective users evaluate Estelle against a real task.
• Follow opportunities from the first conversation through evaluation and adoption, keeping next steps clear for everyone involved.
• Build useful examples, technical explanations, and sales materials with the people developing the product.
• Track what you try and what happens, then use that evidence to improve our messaging, outreach, and product priorities.

What you should be comfortable building

• A working product demo built around a specific engineering problem, with a clear setup and an explanation of what the product did.
• A focused outreach campaign: a researched audience, relevant messages, organized follow-ups, and a record of what led to useful conversations.
• An evaluation plan with a prospective user that defines the task they want to accomplish, the setup they need, and how both sides will judge the result.

What you’ll bring

• You can understand a technical product well enough to explain how it works, where it fits, and where its limits are.
• You’re comfortable starting conversations, building relationships, and following through without relying on an established pipeline.
• You communicate clearly in writing and in a live conversation with engineers.
• You can organize a set of opportunities, make sensible priorities, and learn from both positive and negative responses.
• You’re interested in how developers actually use coding agents and what makes a new tool worth adopting.

Experience that would help

• Previous work in technical sales, solutions engineering, developer relations, product-led growth, or customer-facing work for a software product.
• Experience running technical demos or product evaluations and following the conversation through setup, feedback, and adoption.
• Examples of outbound research, partnerships, or customer communication where you can explain your contribution and the outcome.
• Building a small application, contributing to a codebase, or working closely enough with engineers to understand APIs, Git, and the software delivery process.