New York

October 15–17, 2025

Berlin

November 3–4, 2025

London

June 16–17, 2025

So you want to hire engineering force multipliers?

10x engineers, platform engineering, infrastructure, DevEx... What do they have in common? They're hard to hire, easily burned out, difficult to grow, and likely to fail. Let's talk about how to do it right.

Speakers: Hazel Weakly

Register or log in to access this video

Create an account to access our free engineering leadership content, free online events and to receive our weekly email newsletter. We will also keep you up to date with LeadDev events.

Register with google

We have linked your account and just need a few more details to complete your registration:

Terms and conditions

 

 

Enter your email address to reset your password.

 

A link has been emailed to you - check your inbox.



Don't have an account? Click here to register
June 25, 2025

I see you want to hire talent to work on platform engineering, or maybe internal developer tooling, or perhaps developer experience. Maybe you just need more kickass force multipliers on your team. Whatever it is, you’re solving for the overall generally intangible but admirable goal of “making life better for devs” and “creating exponential leverage”. That’s awesome; you’ve got one hell of a challenge ahead of you.

This role is extremely difficult to hire for. In my opinion, and in my experience, these roles have been the most difficult role in the company to hire for outside of senior leadership, and the most likely to fail; if there ever was a role that burns people out, it’s this one.

Come along with Hazel as we draw on her experiences building “cost-center” organizations that punch above their weight, creating healthy outlier teams that redefine the bar for excellence, and diagnosing hiccups that may occur along the way.

Key takeaways:

  • The hiring pipeline and interview loop — Identifying systems thinkers without scaring them away
  • Timing, politics, and the meta strategies of justifying cost-center engineering headcount
  • Getting to zero from negative — On-boarding rapidly when the role requires deep context
  • Avoiding mismatched expectations