Understanding the Role and First 90-Day Plans Questions
Demonstrating how a candidate translates a target role's scope and organizational context into a concrete plan for the first weeks and months on the job. Every question here anchors on an explicit transition: the candidate is joining, starting, or newly responsible for a role, or is designing the onboarding a new hire will go through. Covers self-onboarding (a listening and learning plan, stakeholder mapping, relationship building, interpreting seniority expectations, a 30/60/90-day or first-week/first-month plan, sequencing early quick wins against longer-term change); assessing what you inherit (auditing the health and maturity of the systems, data, documentation, processes or pipeline you are handed, ramping onto an unfamiliar codebase or on-call rotation, and turning that assessment into early priorities); reporting upward while ramping (a progress and escalation cadence, an early executive checkpoint, presenting the plan to stakeholders who disagree with each other); handling the incident, contingency or capability gap that lands while you are still new; and designing onboarding for someone else, from a single hire (ramp-up checklists, day-one access and readiness, mentorship, buddy and pairing schemes) up to a program that scales across teams and is measured for effectiveness. Does not cover: role responsibilities or success metrics discussed with no transition or newness anchor (see role-responsibilities-and-success-criteria); senior or staff-level judgment scenarios that do not involve starting or joining a role, even when they carry a project timeline (see senior-and-staff-readiness); technical, incident or domain execution that merely carries a rollout timeline and would read the same for a three-year incumbent (see the relevant technical topic); team training, upskilling or mentoring programs with no new-joiner anchor (see continuous-learning-and-professional-development); interpersonal or cultural working-style fit unrelated to planning (see team-fit-and-organizational-fit); and questions asking what the CANDIDATE would ask an interviewer, which no interviewer would pose.
Walk me through the 30/60/90 day plan you would put together for this role. What would you aim to have done by each of those marks, and how would you get your manager to agree it is the right plan?
In your first 30 days in this role, how would you structure discovery conversations with stakeholders across sales, marketing, customer success, product, and finance, and how would you turn what you hear from all of them into a set of prioritized actions?
Say that 30 days in, you realize your team is missing senior UX and data engineering capability, and it's slowing down validation and delivery. How would you close that gap over the next 100 days: what you'd hire for, how you'd sequence it, and what you'd do in the meantime with contractors or reallocating people?
An executive tells you they want a 100 day plan with no surprises and a guaranteed revenue number attached. How do you handle that conversation? Be specific about what you would commit to and what you would refuse to guarantee.
Imagine you're preparing an executive update at an early checkpoint, say 30 or 60 days in. Walk me through what you'd include: your top findings so far, the priorities you'd propose for the next stretch, the biggest risks you're watching, and any specific ask you'd bring to leadership, whether that's a decision or budget. How would you structure that into a tight, presentable brief?
Unlock Full Question Bank
Get access to all Understanding the Role and First 90-Day Plans interview questions and detailed answers.
Sign in to ContinueJoin thousands of developers preparing for their dream job.