Ryan
Peterman

Most engineers measure their careers in years. Ryan Peterman measures his in impact. By the time most new grads are still figuring out how to navigate their first performance review cycle, he had already cleared four promotion levels at Instagram and landed the title of Staff Engineer - a rank that, at Meta, typically takes a decade or more to reach.

He did it in three years. And then he walked away.

The story starts at Amazon, not Instagram. Eight months into his first job out of college, Peterman noticed something: growth wasn't happening. Not for lack of talent. For lack of mentorship. He was at a small satellite office, far from the engineering center of gravity, with no dedicated guide to help him navigate the invisible rules of the industry. So he left.

Instagram was a different world. The mentorship was real, the challenges were real, and the growth followed. Within his first year, he led a project ambitious enough to force a complete rethink of their media message pipeline - cutting send latency in half. That earned him his Senior promotion. The Staff promotion came by following the same logic: pick problems large enough that solving them changes how the team works. Not just how one feature works. How the whole operation moves.

The newsletter followed naturally. Peterman had experienced what a difference mentorship makes. He had also noticed that most engineers - especially those at smaller companies, earlier in their careers, or in offices far from the action - don't have access to it. The Developing Dev launched to fill that gap. Not with generic advice, but with the kind of specific, honest guidance that good mentors actually give.

The growth was not overnight. It was Thursday nights. Every week, without exception, Peterman sat down - sometimes in Cancun at 3 AM on vacation, sometimes in San Francisco after a full day of engineering work - and wrote. By the end of 2024, the newsletter had more than tripled its subscriber base in a single year, going from 41,000 readers to 94,000. Page views went from roughly one million annually to over three million. He published 51 posts that year. Didn't miss a single one.

That discipline isn't an accident. Peterman approaches everything the way he approaches code: with a clear problem statement, a measurable goal, and no patience for half-measures. He once scheduled twelve SCUBA dives in a single vacation week. He studied the biographies of IC8+ engineers at Meta to understand what they had in common before deciding which team to join next. The conclusion? They were all in the right place at the right time when something grew enormously. So he moved to AI/ML Training Infrastructure. The pattern continues.

In 2025, Ryan Peterman left Meta. He had spent more than five years there, risen to Staff Engineer, switched from Instagram's Media Infrastructure to AI/ML Training Infra at exactly the right moment, and received the coveted month-long "recharge" sabbatical that Meta gives to employees hitting the five-year mark. He traveled. He thought. He came back with a decision.

His own words on LinkedIn: "I quit the best job I ever had to try and build what I wish existed in the world."

That statement has three things happening at once. First, the acknowledgment: it was a good job, by any measurable standard. Staff at Instagram is not a small thing. Second, the deliberate past tense: it's done. Third, the mission statement disguised as a goodbye post: build what he wished existed.

What he wished existed turns out to be two things. A podcast where engineers tell honest career stories - not curated success narratives, but the actual texture of how careers unfold. And a keyboard that doesn't compromise between ergonomics, portability, and aesthetics.

The Peterman Pod launched on YouTube, Spotify, and Apple Podcasts. Guests have included Ethan Evans, a former Amazon Vice President, Boris Cherny, who built Claude Code, and Leslie Lamport, a Turing Award winner who invented LaTeX and the Paxos consensus algorithm. That last one is a genuinely remarkable get for any podcast, let alone one that also covers how to get a Staff promotion faster.

Compose, his hardware company, is designing an ergonomic split keyboard. The pitch is simple: every existing ergonomic keyboard makes you choose between actually ergonomic layout, low profile, wireless connectivity, aluminum build quality, and portability. Compose promises all of them. The prototype features scissor switches - the same mechanism used in high-end laptop keyboards - with a foldable design that converts to a book-style cover for travel. An aluminum body. Entirely wireless. A Kickstarter campaign is forthcoming.

The project says something about how Peterman operates. A software engineer who notices a gap in the market, decides existing solutions don't meet the standard, and starts building - from scratch, in hardware. The same logic that drove him to leave Amazon in eight months. The same logic that led him to start writing at 3 AM from a hotel room in Mexico. If the thing you need doesn't exist, you build it.

Most software engineering content online falls into two buckets: abstract life philosophy ("follow your passion") or dry technical deep-dives disconnected from career reality. Peterman deliberately occupies neither. His newsletter is operational. It tells you what to do on Monday.

He gave a talk at UCLA where the central message was blunt: being good at your job does not guarantee a promotion. Promotions are decided by people. Which means visibility matters as much as output. Which means the engineer who writes the excellent code that nobody knows about is not in the same position as the engineer who writes excellent code and communicates about it effectively. It's not a cynical observation - it's a practical one. And it's exactly the kind of thing that good mentors say and nobody else bothers to.

On work-life balance, his position is similarly direct: it's personal. He spent long hours at Instagram and felt balanced because the work was genuinely interesting. He wasn't grinding reluctantly - he was engaged. His advice to engineers feeling stuck: if you aren't interested in what you're working on, don't settle. Not because the company owes you interesting work. Because career growth and personal engagement are closely linked, and staying on a team where neither exists serves nobody.

There's a pattern in how he studied the most senior engineers at Meta. He didn't ask who worked the hardest. He asked what they had in common structurally. The answer - being present when something grew enormously - informed a major career decision. That's the mind at work: applying analytical frameworks to questions most people treat as luck or personality.