Distinguished Engineer · Capital One · writing on scaling dev teams, API design & remote-first culture
Nate McGuire writes about building software the way it actually gets built — the tradeoffs nobody puts on slides, the decisions that look obvious in retrospect and weren't, the difference between what teams say they do and what they ship. He's a Distinguished Engineer at Capital One.
Most engineering orgs are run as cost centers — which is why they feel like cost centers. The teams that compound are the ones that wire engineering directly into demand-gen, performance marketing, and revenue. Marketing-led engineering isn't a buzzword; it's the difference between an org that grows headcount and one that grows leverage.
The healthiest engineering cultures aren't the friendliest. They're the ones with the clearest expectations, the fastest feedback loops, and the highest tolerance for hard conversations. High-performance teams are built on autonomy, discipline, and results — not on perks and process.
Hybrid teams are the future, but there is still something to being in person, in the office. Join us in McLean at Capital One!
Conway's Law is the cheat code most engineering leaders ignore. If you want microservices, you need teams shaped like microservices. If your org chart is a monolith, your system will be too — no matter how clever your AWS diagram. Scaling teams is scaling the system.
Code review SLAs. Deploy speed. Time-to-first-PR for new hires. Cycle time is the leading indicator of team health. When cycle time goes up, every other metric — quality, morale, retention — eventually follows it down.