Building an Employer Brand Developers Actually Respond To

Amazon’s internal developer tools organization was competing for engineering talent against companies like Google, Meta and Stripe, each with a well-developed story about what it means to build there. Our org had no clear employer brand of its own, and recruiters were messaging candidates without a consistent point of view.

The challenge

Understand how peer companies positioned themselves to engineers, and use that to rebrand our org’s story and give talent partners language that worked.

What I did

• Defined the competitive set. These were the companies recruiting the same developer profiles we wanted.
• Audited systematically. I went through career sites, developer content, job descriptions, social presence and event messaging.
• Organized it by theme. Compensation narrative, technical credibility signals, culture messaging and community investment, all in one repository.
• Sorted wins from gaps. Where competitors were strong, where they were weak, and where we had proof points nobody was talking about.
• Listened for what resonated. Aspirational language, career-arc stories and hard technical problems framed as opportunities.
• Turned it into recommendations. I shared concrete messaging guidance with talent partners, leadership and brand stakeholders.

What changed

The org’s employer positioning shifted from feature-level descriptions of what the team built to what a developer could become by working there, and talent partners adopted the new framework in their outreach.

What I took away

Engineers don’t join a product list. They join a story about who they’ll be in two years.