A director at a mid-sized logistics firm once told a colleague of mine that by the time an internal vacancy hit the company's job board, she already had someone in mind roughly 70% of the time. Not because the process was rigged — because good managers plan headcount and successors months ahead, and by the posting date they've usually already had a hallway conversation, a coffee, or a "just checking in" call with the person they expect to apply. The posting exists to satisfy HR process and give everyone a fair shot on paper. The actual decision, in a lot of organisations, started forming weeks earlier.
This isn't a conspiracy against outsiders, and it isn't unique to any one industry — internal hires already know the systems, the politics, and the unwritten rules that take an external hire months to absorb, which is exactly why managers who can pre-identify a strong internal candidate usually prefer to skip the ramp-up risk entirely. The practical consequence for you is uncomfortable but useful: if you're only paying attention to internal roles once they're posted, you're competing for whatever's left of the decision, not shaping it. Getting ahead of that timeline is a skill, not luck, and it's one most men in their late twenties and thirties never bother to build deliberately.
Read the org chart like a weather forecast
Reorgs, new product launches, and leadership departures all throw off signals months before a role gets created. A VP announcing a new market entry at a town hall, a director quietly taking on a second team's reports, a colleague mentioning their manager's been "stretched thin since Dave left" — these are the equivalent of a pressure system building on a weather map. Nobody's told you a job is coming. But if you're paying attention to org announcements, quarterly all-hands decks, and who's covering what since the last departure, you'll often see the shape of an opening a full quarter before HR does. Track this the boring way: keep a running note of team changes, departures, and expansion announcements you hear about, and revisit it monthly rather than trying to remember it all in your head.
The mistake most men make here is treating this intelligence passively — noticing the signal and doing nothing with it beyond mentioning it to a friend over a pint. The move is to act on it early: request a 20-minute conversation with the hiring manager or their manager before anything's posted, framed honestly as interest in where the team is heading rather than a thinly veiled pitch for a job that doesn't exist yet. "I noticed the APAC expansion is picking up — I'd be interested to understand how the team's growing" opens a door that "can I apply when the role goes live" never does, because the first invites a conversation and the second waits for permission.
Visibility beats competence if nobody's seen the competence
This is the part that grates on a lot of technically strong men, and it's still true: doing excellent work that nobody outside your immediate team knows about doesn't move you toward the next role — it just makes you good at your current one. Cross-functional visibility is the actual lever. Volunteering for a working group that touches two or three departments, presenting your team's results at a skip-level meeting when the opportunity comes up, or simply being the person who answers a director's Slack question accurately and fast — these put your name in rooms where the next role's decision gets made, well before any posting exists.
Don't confuse this with self-promotion for its own sake, which reads as exactly what it is and works against you with most senior stakeholders. The distinction is doing genuinely useful cross-team work and making sure the right people know it happened — not manufacturing visibility through unnecessary meetings or copying six people on emails that only needed one recipient. A senior manager who's watched you competently run a cross-functional project for two quarters doesn't need convincing when your name comes up for a stretch role; they've already seen the evidence.
Building the relationship before you need it
The men who pull this off consistently share one habit: they've had a genuine, low-stakes conversation with the manager two levels up before there was anything to ask for. A quarterly 15-minute skip-level check-in, a question asked well in a cross-team meeting, a follow-up email after a project wrapped that flagged a specific insight rather than just "great working with you" — none of these read as networking in the transactional sense, and that's precisely why they work. Managers can smell a relationship that only exists because someone wants something from them, and it makes the eventual ask land worse, not better. Start these conversations six months to a year before you expect to need them, not the week after a role gets posted, because relationship-building compressed into two weeks reads exactly as what it is.
Keep a short list — five or six people across the organisation whose teams interest you, updated twice a year — and make sure each relationship has at least one genuine touchpoint in that window that isn't about you asking for anything. This sounds like more effort than most men are willing to put in for a job they don't currently have, and that's exactly the point: the people who do it face far less competition for the roles that matter, because most of their peers are still waiting for the posting to go live before they start thinking about any of this at all.
The mid-text reality check: this doesn't always work
None of this guarantees anything, and it's worth saying plainly: some managers genuinely do run a fair, open process regardless of who they've spoken to beforehand, and some organisations have policies specifically designed to prevent pre-selection — a formal skills assessment stage, a panel interview with people outside the hiring manager's chain, a documented scoring rubric. If your company runs a rigorous, structured internal process, spending months building pre-posting relationships buys you less than it would elsewhere, and your energy is better spent preparing a genuinely strong application and interview performance instead. Read your own organisation's actual track record — ask a few people who've moved internally recently how the process really went — before assuming the hallway-conversation model applies where you work.
What to do the moment the posting actually appears
If you've done the groundwork, the posting itself becomes a formality — apply promptly, but the real work already happened. If you haven't and a role you want suddenly appears, don't panic-apply immediately with a generic cover note; take 48 hours to message the hiring manager directly, reference something specific about the team's recent work, and ask a genuine question about scope or priorities before submitting your application. A late start with a sharp, specific approach still beats an early application that reads like every other one in the queue. Managers remember the candidate who asked a good question about the actual problem the role exists to solve — that's worth more at the interview stage than having applied six hours before anyone else did.