This guide consolidates LinkedIn field notes into one crawlable article. The short posts are intentionally preserved as sections so the ideas can be referenced from scheduled LinkedIn CTAs and discovered through search.
Contents
- How to build a 30/60/90-day plan for an interview
- Interviewing for the Role Above Your Current Level
- How to plan your first 90 days at a new role
- Onboarding to Land: The First 90 Days at a New Senior Role
How to build a 30/60/90-day plan for an interview
As an experienced recruiter and reverse recruitment consultant who has helped hundreds land jobs across USA, Canada, Europe, and the GCC, here's what I see most often:
How to build a 30/60/90-day plan for an interview, even when you don't have insider context yet.
By second-round of a senior interview, you'll often be asked: "What would you do in your first 90 days?" Candidates who improvise on this question get filtered. Candidates who walk in with a credible plan move forward.
The structure that works:
Days 0–30: Listen and learn. Write 3–4 specific things you'd want to do in the first month. Examples: 1:1s with the team to understand current state and pain points. Audit the existing systems/processes you'd inherit. Review the last 6 months of customer feedback / sales data / team retention data. Set up a meeting cadence with adjacent leaders.
Days 30–60: Diagnose and pilot. What hypothesis would you test? Which 1–2 changes would you start in this window, small enough to run safely, big enough to learn. Examples: a pilot program with one segment. A pricing experiment. A team reorganization in one pod.
Days 60–90: Commit and scale. What decisions would you make based on what you learned? What would you stop doing, double down on, or build new? This is where you show strategic judgment.
Key: the plan signals process, not omniscience. Hiring managers want to see you'd ask questions before changing things.
Save this. The next senior interview you walk into, build this plan in advance.
Interviewing for the Role Above Your Current Level
Reverse recruitment consultant note. 10+ years inside HR. Hundreds of senior placements across USA, Canada, Europe, and GCC. Today's observation:
Interviewing for the Role Above Your Current Level
At some point in most senior careers, you interview for a role one level above your current title. Director interviewing for VP. VP interviewing for SVP or Chief. The mechanics of those interviews are different from interviewing laterally, and most candidates handle them badly.
Here's what works, drawn from interviewing patterns across 100+ stretch placements I've supported.
The two interview tracks
When you interview for a stretch role, the interviewer is running two evaluations in parallel:
Track 1. Can this person do the job?
Standard fit assessment. Skills, scope, outcomes, experience.
Track 2. Is this person ready for this level, or are they reaching?
Subtler. The interviewer is looking for signals about your operating maturity, scope-of-thought, and how you handle ambiguity.
Track 2 is what kills most stretch candidates. They prepare well for Track 1 and ignore Track 2.
The Track 2 signals interviewers watch for
How you frame your current role. Candidates ready for the next level talk about their current work in scope language ("I own X across the team"), not task language ("I do X"). The frame reveals operating altitude.
How you handle pushback. When the interviewer pushes back on your answer, do you defend, refine, or reconsider? Senior leaders refine and reconsider; junior leaders defend.
The questions you ask. Strategic, multi-stakeholder questions signal stretch readiness. "What does the next 18 months look like for this function?" reads as senior. "What's the dress code?" doesn't.
How you talk about your team. Senior leaders give credit specifically and take responsibility specifically. "The team shipped X, my role was making sure resources were unblocked." Junior leaders take credit broadly and dodge responsibility.
Time horizons in your answers. When asked about goals, your answer's time horizon shows your operating level. Director answers in quarters. VP answers in years.
The four moves that win stretch interviews
1. Don't apologize for the stretch.
The candidate who says "I know I'm reaching for this level" has just told the interviewer you're not ready. The candidate who says "I've been operating at this scope informally; this is the formal step" has demonstrated readiness.
2. Talk in the role's language, not your current role's.
A Director applying for VP needs to talk about team-of-teams scope, multi-functional alignment, and strategic positioning. If your answers stay tactical, the interviewer concludes you can't operate at the level.
3. Address the obvious gap directly.
If the role requires something you haven't formally done, managing managers, owning a P&L, board exposure, name it before the interviewer does. "Direct P&L ownership will be new for me. Here's how I've been preparing for it: [specific actions in the last 6-12 months]."
This is counter-intuitive. You think naming the gap makes them notice it. The opposite is true. Naming it shows self-awareness; ignoring it makes the interviewer wonder if you're aware at all.
4. Have a 30/60/90 plan calibrated to the higher level.
A Director's plan emphasizes team execution. A VP's plan emphasizes team direction and cross-functional strategy. Your plan tells the interviewer what level you'll operate at on Day 1.
The closing question
When the interviewer asks "Do you have any questions for us?" the question that wins stretch interviews is some version of:
"What would the most successful version of this hire have done by Day 90? And, what would the failed version have done that you'd have wanted to catch sooner?"
This question shows you're already thinking about success and failure modes at the new level. It's a senior question, asked by a senior candidate.
The deeper observation
Stretch interviews are won and lost on Track 2, operating maturity at the higher level. The candidate who comes across as already operating at the level (even if title hasn't caught up) lands. The candidate who comes across as aspiring to the level loses.
The good news: most senior professionals who are ready for the stretch have already been doing the work informally for 12-18 months. The interview is about making that visible, not about pretending to be something you're not.
How to plan your first 90 days at a new role
Reverse recruitment consultant note. 10+ years inside HR. Hundreds of senior placements across USA, Canada, Europe, and GCC. Today's observation:
How to plan your first 90 days at a new role (when you've finally landed).
The first 90 days at a new senior role shape the next 2-3 years. Most candidates either over-deliver too early or under-show in the first month. Here's the calibrated version.
Days 1-14. Listen, don't act.
Resist the urge to make changes in week 1. Your credibility comes from how you observe before you intervene.
1:1s with every direct report
Coffee with every key cross-functional partner
Read all existing strategy docs, OKRs, last 3-4 quarter reviews
Sit in on standing meetings without leading
Document everything. Don't propose changes yet.
Days 15-30. Diagnose, don't decide.
Identify 3 highest-leverage opportunities
Validate with 5-10 stakeholders to confirm you're seeing it right
Draft proposed approaches but don't commit
End-of-month: deliver a "what I'm seeing" memo to your manager
Days 31-60. Pilot, don't transform.
Pick the highest-leverage opportunity
Run a small pilot, limited scope, fast feedback
Don't try to overhaul systems yet
Demonstrate impact through pilot before scaling
Days 61-90. Execute and own.
Scale what worked from the pilot
Set up measurement systems
Establish your operating rhythm
Build the relationships that will produce 12-month results
The trap to avoid:
Most senior new hires fail by trying to deliver something visible in week 2-3. The work that endures comes from the listening phase. The instinct to prove value early often produces shallow wins that don't compound.
What to deliver to your manager at Day 30, 60, 90:
Day 30: Diagnosis memo with proposed initiatives
Day 60: Pilot results with scale recommendations
Day 90: Operating rhythm and 12-month plan
The candidates who keep their roles past the first year are the ones who used the first 90 days to listen and build before they delivered.
Save this for your landing.
Onboarding to Land: The First 90 Days at a New Senior Role
After 10+ years in HR and reverse recruitment, hundreds of senior professionals placed across USA, Canada, Europe, and GCC, a pattern worth naming:
Onboarding to Land: The First 90 Days at a New Senior Role
Most career advice ends at "you got the offer." That's where the harder work often begins. The first 90 days at a new senior role determine whether you'll be there in 2 years or 12 months. Most senior professionals don't get coached on this phase, they're expected to figure it out.
Here's what I've seen across clients who landed and stayed, vs those who landed and left.
The first-90-days failure modes
The patterns that produce 12-month exits:
Over-delivery in week 1-2. Candidates anxious to prove themselves try to make visible changes immediately. The team reads this as performative. Trust erodes before it's built.
Under-listening. Candidates rely on their last role's playbook. The new context has different stakeholders, different politics, different cultural norms. The playbook doesn't translate without listening first.
Wrong relationships first. Senior new hires often build relationships with peer leaders first because that feels like home. The strongest hires build down (with their team) and across (with cross-functional partners) before going up the ladder.
Big initiative before diagnosis. Announcing a major project in month 1 makes you look strategic. By month 6, when the project hasn't worked because it was based on incomplete information, the strategic reputation is replaced with "moves too fast."
Skipping the boring meetings. New senior hires often skip standing operational meetings to focus on strategic ones. The signal you're missing in operational meetings is what's actually working and not working day-to-day.
The 4-phase framework
Phase 1. Listen and Map (Days 1-14)
Goal: Understand the team, the work, the context.
1:1 with every direct report (45-60 minutes each)
30-minute intros with every key cross-functional partner
Sit in on all standing meetings without leading
Read all existing strategy docs, OKRs, last 4 board reviews
Note: don't propose anything yet
Phase 2. Diagnose and Validate (Days 15-30)
Goal: Identify the 3 highest-leverage opportunities and validate them with stakeholders.
Based on listening, identify what's working, what's broken, what's missing
Test your diagnosis with 5-10 stakeholders: "Here's what I'm seeing, does this match your view?"
Refine based on feedback
Day 30 deliverable: a structured "what I'm seeing" memo to your manager
Phase 3. Pilot and Learn (Days 31-60)
Goal: Test one initiative on a limited scope with fast feedback.
Pick the single highest-leverage opportunity
Design a small pilot, measurable, time-bound, low-risk
Run it. Learn from it. Iterate.
Don't scale yet
Day 60 deliverable: pilot results memo with scale recommendations
Phase 4. Execute and Establish (Days 61-90)
Goal: Scale what worked, set up the operating rhythm you'll use long-term.
Scale the pilot's successful elements
Set up measurement systems
Establish weekly/monthly cadence with team and stakeholders
Begin building the 6-12 month roadmap
Day 90 deliverable: operating rhythm document and 12-month plan
The relationship priority order
Most new hires get this backwards. The order that works:
Tier 1. Direct reports. Build trust here first. They're the people who execute your strategy. Without their trust, nothing happens.
Tier 2. Peer cross-functional partners. They make or break your success daily. Strong relationships here produce shared wins.
Tier 3. Your manager and skip-level. They evaluate you, but they're not the daily reality. Strong relationships here happen naturally if Tiers 1 and 2 are solid.
Most senior new hires reverse this, they spend disproportionate time managing up in the first 30 days. The execution suffers.
The internal narrative trap
After a long search, the brain is half-bracing for rejection in the new role. You may notice:
Over-explaining your decisions
Performing competence rather than just acting competently
Apologizing for things that don't need apology
Second-guessing your judgment
These patterns are residue from the search. They fade with time. Notice them. Don't let them shape the first impression you make at the new company.
The deeper observation
The first 90 days are partly about delivering value. They're more about establishing the operating model that will produce value for the next 24+ months. Senior professionals who slow down in the first month often run faster from month 6 onward.
The candidates who land and stay aren't the ones who delivered most in week 2. They're the ones who built the foundation that made everything afterward easier.
— Dr. Hosney Adel