Forward deployed engineer

What you'll do

• —Own customer deployments end to end — install the desktop app, connect GitHub, and stay until their first agent-run tickets are merging.
• —Make each customer's repo agent-ready: author the Project Context and conventions that stop Workers guessing, proven against real tickets in their codebase.
• —Wire the runtime layer — bring-your-own-subscription agents, remote-paired machines, connectors, and automations against our API.
• —Debug the whole seam in the field: desktop shell, worktrees, branches, and CI status flowing back to the board.
• —Turn what you learn on site into product changes you ship yourself, instead of leaving one-off scripts behind at every account.

What we're looking for

• —You already use Fredrin. Every applicant should arrive knowing how the board, worktrees, and review flow work — you'll be teaching it on day one.
• —Substantial experience shipping production software, and the presence to be the technical voice in the room with a customer's engineers.
• —Strong TypeScript and real git depth — branches, worktrees, rebases, and what breaks when many agents touch one repo.
• —Practical experience with AI coding agents in real work, plus comfort close to the OS: processes, file systems, shells, and CLIs.
• —Self-directed and clear in writing — you'll often be the only Fredrin person inside an account, and you unblock yourself.

How we work

• —Small team, high trust — you work directly with the founders and own whole problems, not tickets.
• —We use Fredrin to build Fredrin: most changes ship through the same agent-driven flow we sell.
• —Written-first communication, few meetings, and a bias for shipping something real every week.

Where you'll work

Every role at Fredrin is fully remote. We work async-first across time zones, with a written culture that cares about what you ship, not where you sit.