Engineering Manager, Docs

Fern

12d•Onsite

About The Position

At Fern, we believe every software company should offer a world-class API. We're building the toolkit to make that possible. We enable customers like Square, ElevenLabs, and Auth0 to offer a best-in-class developer (DX) and agent experiences (AX). Our team is primarily ex-Palantir and ex-founders, working together from our office in Williamsburg, Brooklyn. We give builders the autonomy to take ownership, the speed to move quickly, and the support to do the best work of their careers. As a Software Engineering Manager at Fern, you’ll lead a small, high-leverage team of engineers building core product experiences used by thousands of developers. You’ll balance hands-on technical leadership with people leadership to own execution, quality, and team health while staying close to the code and customers.

Requirements

8+ years as a software engineer
3+ years as a software engineering manager
Strong written and verbal communication skills to solve technical problems with customers
Experience partnering with product designers
Experience building with TypeScript, Next.js, and Vercel

Responsibilities

Lead and grow a high-performing team: Manage, mentor, and develop a team of engineers as we scale. You’ll set clear expectations, give technical feedback, and help double the team this year by recruiting and interviewing engineer.
Be a technical leader, not just a people manager: This is a true player/coach role. You’ll review code, influence architecture, and help make sound technical decisions across the stack. You’ll write code alongside the team—digging in where problems are hardest, stakes are highest, or customer impact is greatest.
Build developer-facing web infrastructure: Fern is open source, and you can explore the repo we work in. You’ll lead work on a TypeScript-heavy Next.js application hosted on Vercel, thinking deeply about performance, scalability, reliability, and developer experience across the Fern Docs product.
Improve systems, not just outcomes: Identify where process, tooling, or architecture is slowing us down and fix it. This could mean improving CI, clarifying ownership, simplifying abstractions, or investing in reliability and observability.