Introduction
Somewhere in the final round of a regulatory affairs interview process, particularly for specialist, manager, or director-level roles, a hiring manager may ask a candidate to walk through what their first 30, 60, and 90 days on the job would look like. It is a request that catches a lot of otherwise well-prepared candidates off guard, partly because it asks for something more concrete than the usual behavioral interview answer, and partly because it is genuinely easy to get wrong in either direction: too vague to be useful, or too confident about a role and a company the candidate has not actually started yet.
Why hiring managers ask for this
A 30-60-90 day plan is not really a test of whether a candidate can predict the future. Nobody expects a plan built before day one to survive contact with the actual job unchanged. What a hiring manager is genuinely evaluating is whether the candidate understands how a regulatory affairs role like this one typically ramps up, whether they think in terms of sequenced priorities rather than a flat list of tasks, and whether they have done enough homework on the specific role and company to make the plan sound grounded rather than generic. It also reveals how a candidate thinks about building credibility with a new team, since a plan that starts with sweeping changes on day one reads very differently than one that starts with listening and mapping the existing landscape.
This request tends to show up more often for roles above entry level, where a company is hiring someone to eventually own a specific area, an existing product line, a therapeutic area, a submission portfolio, rather than someone who will simply be trained into an established process. It is less common for pure entry-level or coordinator roles, where the ramp-up expectations are more standardized and less worth individualizing in an interview.
What the 30-day phase should actually contain
The first 30 days should be framed almost entirely around learning and relationship-building, and candidates who resist the urge to promise early wins here tend to come across as more credible, not less. Concretely, this means reviewing existing submission history, current product or pipeline status, and whatever internal processes and templates the team already uses, alongside meeting the cross-functional partners, clinical, quality, CMC, commercial, that the role will work with regularly. For a regulatory affairs hire specifically, this phase should also include understanding what regulatory commitments and deadlines are already in motion, since walking into an active submission cycle without first mapping what is already committed is a common and avoidable early misstep.
It helps to be specific about who the candidate would prioritize meeting and what they would specifically be trying to learn from each conversation, rather than a generic line about wanting to meet the team. A stronger answer might note reviewing the current regulatory intelligence process, understanding how the team tracks agency correspondence, or getting up to speed on a specific product's approval history, depending on what the role actually is.
What the 60-day phase should actually contain
By 60 days, a credible plan shifts toward starting to contribute directly, typically by taking ownership of smaller, well-defined pieces of work while continuing to build context on larger initiatives. This might mean independently handling a routine submission or amendment, taking primary responsibility for tracking a specific product's regulatory correspondence, or beginning to represent the function in a cross-functional meeting rather than just observing one. The key framing here is that the candidate is demonstrating early, contained value while still deferring to established processes and more senior team members on anything higher-stakes or less familiar.
This is also a reasonable point in the plan to mention identifying process improvements worth raising, without committing to having already solved them. Noticing that a particular tracking method seems inefficient, or that a template could be streamlined, and planning to raise it as an observation rather than a unilateral change, signals both initiative and the judgment to know that changing an established process before understanding why it exists that way is usually premature.
What the 90-day phase should actually contain
The 90-day mark is where a candidate can reasonably talk about taking fuller ownership of a defined piece of the role, whether that is a specific product, a category of submissions, or a particular process area, while being honest that full proficiency in a specialized regulatory function usually takes longer than three months to reach. This is not the moment to promise mastery; it is the moment to describe a realistic trajectory toward it, along with an intention to check in with the manager about how the ramp-up is actually going relative to what both parties expected going in.
A strong closing note in this phase is proposing a check-in conversation with the hiring manager around this point, framed as a chance to calibrate whether the plan matched reality and adjust from there. It signals that the candidate sees the plan as a living document and a two-way conversation rather than a rigid contract, which is exactly the right instinct for how these plans actually get used once someone starts.
Common mistakes that undercut an otherwise good plan
The most common mistake is being too generic, describing a plan that could apply to almost any job at almost any company rather than reflecting real knowledge of the specific role, product area, or regulatory environment involved. A close second is the opposite problem: promising specific, substantive achievements, a completed submission, a fully redesigned process, within a timeline that is not realistic given how long access provisioning, internal onboarding, and simply learning a new company's systems and history actually take.
Overpromising on day-one changes is another frequent misstep. A plan that proposes overhauling an existing process before the candidate has even seen how the current team works signals a lack of humility that experienced hiring managers tend to notice immediately, even when the underlying instinct to improve things is a genuinely good one. The fix is not avoiding the topic of improvement entirely, but sequencing it correctly: observe first, propose second, implement only with buy-in and usually later than 90 days.
How to make the plan specific without pretending to know things you can't
The tension every candidate has to navigate is that a generic plan reads as unprepared, while a plan that assumes too much specific knowledge of the company's internal processes reads as presumptuous, since the candidate genuinely does not yet know how this particular team operates. The way through that tension is to be specific about categories and approach while staying appropriately tentative about specific conclusions. Rather than saying a candidate would fix the team's regulatory intelligence tracking process, a more credible version says the candidate would spend early weeks understanding how the team currently tracks regulatory intelligence and would look for opportunities to strengthen it once that picture is clear.
Drawing on research done before the interview strengthens this considerably. If a candidate knows from the job posting or earlier interview rounds that the role involves a specific therapeutic area, a particular submission type, or a known organizational challenge, weaving that detail into the plan, without overstating confidence about internal specifics the candidate cannot actually know, demonstrates real engagement with the actual role rather than a plan copied from a generic template. Interviewers can generally tell the difference between a plan built around genuine research into the role and one built around a formula pulled from a career advice article, so specificity grounded in what is publicly knowable is worth the extra preparation time.
Handling follow-up questions about the plan
A hiring manager who has asked for a 30-60-90 day plan will often probe a specific piece of it, asking how a candidate would handle a particular scenario that falls within the plan's early phase, or pushing on why a candidate prioritized one relationship or task over another. These follow-ups are usually not adversarial; they are a genuine attempt to see how the candidate thinks under mild pressure and whether the plan reflects real reasoning rather than a memorized script. Answering these well means being willing to say plainly that a particular detail would depend on information the candidate does not yet have, rather than inventing a confident-sounding answer to a question that a first-week hire genuinely could not answer with certainty.
It also helps to treat these follow-up questions as an opportunity rather than a trap. A candidate who responds to a challenging follow-up by thinking out loud, walking the interviewer through how they would gather the missing information and who they would ask, often demonstrates more useful signal about their actual working style than the original plan did, since it shows real-time judgment rather than a rehearsed answer.
Tailoring the plan to the specific role level
A plan for an individual contributor specialist role should stay close to the ground: specific submission types, specific products, specific internal processes to learn. A plan for a manager or director-level role should still include a learning phase, but can reasonably layer in more emphasis on understanding team dynamics, existing direct reports' strengths and development needs, and how the function is currently perceived by cross-functional partners, since a chunk of a leadership role's first 90 days is genuinely about building that broader organizational picture rather than executing individual tasks.
Conclusion
A 30-60-90 day plan is less about predicting the future accurately and more about demonstrating that a candidate understands how credibility gets built in a new regulatory affairs role: through listening before acting, taking on contained early wins before bigger ones, and treating the plan itself as something to revisit and adjust once the job actually starts. Candidates who prepare one thoughtfully, specific enough to show real homework, humble enough to acknowledge what they don't yet know, tend to stand out in exactly the way this question is designed to reveal.