Growth Intern

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 Growth Intern at Fate Labs, you’ll help us explain the product and find ways to reach the developers it is built for. You’ll work on product demos, written content, community conversations, and small experiments that help us understand what resonates.

You’ll spend time using Estelle and talking with the team so your work reflects the product itself. We’re interested in people who can turn an idea into something concrete, put it in front of an audience, and learn from the response.

Tools and practical skills

You’ll use Estelle and GitHub to understand product changes, then turn what you learn into demos, walkthroughs, and written content. Be comfortable recording your screen, editing a short video, making clear screenshots, and publishing a finished piece.

You’ll also work with spreadsheets and basic analytics to organize experiments and understand the response. Python, JavaScript, or SQL can help with small automations and analysis; you should be willing to learn enough of the developer workflow to demonstrate the product accurately.

What you’ll do

• Create short demos, walkthroughs, and posts that show a concrete use for Estelle.
• Find developer communities and conversations where our work is relevant, and contribute thoughtfully.
• Research how developers discover and evaluate new tools, then suggest experiments we can run.
• Help turn product updates and engineering work into clear, accurate communication.
• Track responses to your experiments and explain what you would keep, change, or stop doing.

What you should be comfortable building

• A short product walkthrough that starts with a real task, shows the workflow clearly, and explains the result without unsupported claims.
• A complete piece of developer-facing content, such as a tutorial, launch post, short video, or illustrated explanation, shaped for the audience and channel.
• A small distribution experiment with a defined audience, a way to track responses, and a written explanation of what you learned and would try next.

What you’ll bring

• You can show us something you made to get people interested in a product, project, community, or idea.
• You write clearly and can make a technical topic understandable without overpromising.
• You’re comfortable making a first version, sharing it, and improving it based on feedback.
• You pay attention to how an audience responds and can separate a useful result from a flattering number.
• You’re curious about developer tools and willing to learn the product in enough depth to demonstrate it.

Experience that would help

• Previous writing, video, design, community, or marketing work for a project, club, startup, or product. Independent work is useful evidence too.
• Examples of tutorials, newsletters, demos, events, or social campaigns where you can show the finished work and explain your contribution.
• Experience using a screen recorder, a video or image editor, a publishing tool, and a spreadsheet to take an idea through to a measured experiment.
• Basic experience with GitHub, a code editor, a command line, or coding agents, especially if you have helped someone else understand a technical tool.