#61 Strong isn’t the same as obvious

A strong resume will get you into a recruiter conversation. Meeting the core competencies of the role gets you through it.

The hiring manager is where a lot of strong people wash out, because they’re asking something nobody earlier in the loop was: can I picture this person in the job? In my Monday staff meeting? With my particular mess?

Program owners are a good example. Ask about the program they’re proudest of and you get the timeline, the deliverables. Pilot in three sites in Q1. Twenty by the summer. Live across the network by Q4.

It’s a perfectly good answer. It’s also the one the hiring manager has heard from every program manager they’ve ever interviewed.

The hard part is buried in there. Pilots work in three sites because the people running those sites care, then die around site twelve, when operators who never asked for it have to keep it running on a busy Tuesday. Taking a scrappy fix and making it run across a whole network, without acts of heroics, is where a lot of organisations get stuck. The person telling the timeline did exactly that, and skipped straight past it.

Lead with that, and the hiring manager stops checking dates and starts asking how you did it. Same program. Same person. Very different conversation.

And it isn’t only program owners. Most of us skip the part of our experience that would be dead sexy to a hiring manager somewhere else, because to us it was just the job. So we never mention it.

Being easy to picture in the job is what gets you through the hiring manager.

This one is sneaky for Amazonians, because inside, the picture arrives for free. Internal moves tend to come with someone who has already seen your work, or talked to someone who has. And in most rooms, everyone already knew the problem you were solving, and what made it hard, so you could lead with scale and rigour and let people join the dots.

Outside, nobody has all the dots to join. Your skills and experience, and the scale you delivered them at, only count once the hiring manager can see them pointed at their problem.

One thing to try this week: take a job description you’re interested in and underline the problem, not the requirements. What’s breaking, growing or about to happen that made them open this role? Then look at the first story you’d tell. Does it answer that problem, or does it answer “tell me everything you’ve done”?

Previous
Previous

#62 Fungible was a complement at Amazon

Next
Next

#60 Are your interview stories a level behind?