Tech Interview Preparation Module 2 – Research and plan your season
Running a season across several companies
Order applications so practice processes come first, line up offers inside one decision window, track every round and decide when to pause or withdraw.
What you will learn
- Read the clocks and the retry limits that employers publish
- Order applications so practice processes come before priority ones
- Plan start dates so that offers arrive inside one decision window
- Track every application, round and deadline in one place
- Decide when to pause, speed up or withdraw from a process
Before you start
What you’ll learn · Before you start
What you will learn
- Read the clocks and the retry limits that employers publish
- Order applications so practice processes come before priority ones
- Plan start dates so that offers arrive inside one decision window
- Track every application, round and deadline in one place
- Decide when to pause, speed up or withdraw from a process
Before you start
On this page
Start six applications in the same week and the offers will not arrive together: in this lesson’s invented season one process takes 3 weeks from application to offer and another 9, so a fast offer can expire before a slow one arrives. Run the season as one plan, not as six separate hopes.
The plan has four moves: practice process: A real application to an employer you would join but rank lower, started before the processes that matter most, so that your first real interview rounds carry less at stake. first, slow processes early and fast ones late so that the offers you care about are open together, one tracker, and rules for pausing, speeding up or withdrawing decided in advance. Order matters most where an employer limits retries: a rushed attempt can mean waiting six months or a year.
Not affiliated
MySmartCoPilot is not connected with Google, Amazon, Meta, CodeSignal or IIT Kanpur, whose rules are quoted from what each publishes, cited at the end. The worked season’s six companies are invented.
Employers run on published clocks, from days to a year
Official pages state how fast four processes move and how often you may try again:
| Source | How long things take | Limits and waits |
|---|---|---|
| Google: How we hire, and its interview tips | Roughly 6 to 8 weeks once interviews start; a decision can take several weeks more | Up to three applications in a rolling 30-day window; usually a year’s wait to reapply for the same type of role |
| Amazon: SDE II assessment and interview pages | Seven days to take the assessment, news within two days; an outcome within five business days of the interview loop: The final round of a hiring process: several interviews, often on one day or two, each with a different interviewer and focus, such as coding, design or behavioural questions. Also called the full loop or the onsite, even when it runs on video. More in “How tech hiring works, application to offer” | A retry six months after an unsuccessful assessment; a passed one may lead straight to the loop, if a recruiter confirms |
| Meta: full loop guide | Follow up if you hear nothing within a week of the interviews | Not stated |
| CodeSignal: its help centre | Not stated | One, two or three attempts in 180 days, depending on the assessment |
So processes started on the same day finish weeks apart, a rushed first attempt can cost six months to a year, and some results travel: during a CodeSignal cooldown period: The wait after an attempt at an assessment before the same assessment may be taken again; during it, a past score can usually be shared instead. More in “Online assessments: formats, rules, proctoring” you share a past score instead of testing again.
Checkpoint
Check: Published clocks and retry limits
Four moves keep the offers you want open together
Start everything at once and the fastest processes finish first, often at the employers you rank lowest, long before the offers you care about. Four moves fix the order:
- Practice first. Start one or two practice processes at employers you would join but rank lower, so that your first real rounds carry less at stake.
- Count back. Start each priority process its own number of weeks before the decision window: The week or two in which you want the offers you care about most to be open at the same time, so that you can compare them; each process starts early enough for its offer to arrive then., slowest first.
- One tracker. Keep every application, round, contact, deadline and next action on one sheet, checked every week.
- Rules decided early. Decide in writing when you will pause, speed up or withdraw, and take at most two or three final loops a week, a MySmartCoPilot suggestion.
The order of a season
Text description of the diagram
The diagram is a column of four boxes joined by arrows, in the order you start processes:
- First, one or two practice processes: real rounds where a stumble costs little.
- Next, the slow priority processes, which need the most weeks to reach an offer.
- Last, the fast processes, started a few weeks before the decision window.
- One decision window, in which the offers are open at the same time, so that you can compare them.
Read it from the top: practice, then slow priority processes, then fast ones. The fourth move’s rules come in three kinds. To pause is to ask for the next round two or more weeks later. To speed up is to ask for an earlier slot or a faster decision. To withdraw is to tell the recruiter you are leaving.
Campus seasons
On campus, the placement cell: The office of a college or university that runs recruitment on its campus: it registers students, schedules employers and applies the institute's placement rules. More in “Applications, referrals and campus drives”‘s calendar and rules decide much of the order. IIT Kanpur’s Students’ Placement Office, for example, follows a “One Student, One Job” policy: once a student is offered a job, they leave the placement process.
Checkpoint
Check: The four moves of a season
Count back from a decision window
A decision window is the week or two in which you want the offers you care about to be open together, so that you can compare them and tell each recruiter, honestly, about the other deadlines. A process’s start week is the window’s first week minus its weeks from application to offer. Here is an invented season of six applications with a window that opens in week 12:
// Start weeks counted back from a decision window, for an invented season of six applications. Practice processes
// start in weeks 1 and 2; every other process starts its own number of weeks before the window, so the offers you
// care about arrive together. Change the window or a process's weeks to an offer and press Run.
const windowWeek = 12; // the first week in which you want the offers you care about to be open
const processes = [
// [company (invented), weeks from application to offer, role in the season]
['Fjord Cloud', 3, 'practice'],
['Dune Analytics', 3, 'practice'],
['Aster Systems', 9, 'priority'],
['Cobalt Retail', 8, 'priority'],
['Birchwood Pay', 5, 'priority'],
['Ember Mobility', 5, 'priority'],
];
let practiceWeek = 1;
const rows = processes.map(([name, weeks, role]) => {
const start = role === 'practice' ? practiceWeek++ : windowWeek - weeks;
return { name, weeks, role, start, offer: start + weeks };
});
console.log(`Decision window opens in week ${windowWeek}`);
const byName = (a, b) => (a.name < b.name ? -1 : a.name > b.name ? 1 : 0);
for (const r of [...rows].sort((a, b) => a.start - b.start || byName(a, b))) {
const where = r.offer >= windowWeek ? 'in the window' : `${windowWeek - r.offer} weeks before the window`;
console.log(` apply week ${String(r.start).padStart(2)} ${r.name.padEnd(15)} ${r.weeks} weeks to an offer → offer in week ${String(r.offer).padStart(2)}, ${where} (${r.role})`);
}
const early = rows.filter((r) => r.role !== 'practice' && r.start < 1);
if (early.length) console.log(` too late for: ${early.map((r) => r.name).join(', ')}: move the window later or ask about faster dates`);
const inWindow = rows.filter((r) => r.offer >= windowWeek).length;
console.log(`${inWindow} of ${rows.length} offers would arrive in the window; the practice offers come first, on purpose`);Output
Decision window opens in week 12 apply week 1 Fjord Cloud 3 weeks to an offer → offer in week 4, 8 weeks before the window (practice) apply week 2 Dune Analytics 3 weeks to an offer → offer in week 5, 7 weeks before the window (practice) apply week 3 Aster Systems 9 weeks to an offer → offer in week 12, in the window (priority) apply week 4 Cobalt Retail 8 weeks to an offer → offer in week 12, in the window (priority) apply week 7 Birchwood Pay 5 weeks to an offer → offer in week 12, in the window (priority) apply week 7 Ember Mobility 5 weeks to an offer → offer in week 12, in the window (priority) 4 of 6 offers would arrive in the window; the practice offers come first, on purpose
Recorded with Node.js 24.21.0 on macOS 26 arm64. To run it yourself: mise exec node@24.21.0 -- node align.mjs
Runs on this device, in your browser. The first run downloads JavaScript (about 0.6 MB), which is kept for the next runs.
Your run, in this browser
The slowest processes start first among the priorities, in weeks 3 and 4, and the two 5-week processes wait until week 7, so all four offers that matter arrive in week 12, after the practice offers of weeks 4 and 5. Walk through it in the order you would apply:
- Week 1
Apply to Fjord Cloud, a practice process practice
Fjord Cloud takes about 3 weeks from application to offer. It goes first on purpose, so that your first real rounds carry less at stake than the ones that matter.
- Week 2
Apply to Dune Analytics, the second practice practice
Another process of about 3 weeks, started a week after the first, so the two practice processes do not crowd the same days.
- Week 3
Apply to Aster Systems, 9 weeks to an offer priority
Your first choice is also the slowest process, so it starts first among the priorities, at 12 − 9 = 3.
- Week 4
Apply to Cobalt Retail, and Fjord Cloud offers priority
Cobalt Retail takes 8 weeks, so it starts at 12 − 8 = 4. The same week the first practice offer arrives, 8 weeks before the window.
- Week 5
Dune Analytics offers practice
The second practice offer arrives, 7 weeks before the window. Offers that come this early are the cost of practising on real rounds.
- Week 7
Apply to Birchwood Pay and Ember Mobility priority
Both take about 5 weeks, so they wait until 12 − 5 = 7. Sent in week 1, their offers would have come in week 6, half a season before the window.
- Week 12
Four offers that matter, open together decision window
Aster Systems, Cobalt Retail, Birchwood Pay and Ember Mobility all reach their offers in the window, so you can compare them and tell each recruiter, honestly, about the others' deadlines.
The timeline has 7 events, from Week 1 to Week 12.
Weeks to an offer are estimates, so redo the count whenever a recruiter gives you real dates.
Key idea
Start each process at the window’s first week minus its weeks to an offer, and the offers you care about arrive together.
Checkpoint
Check: Counting back from a decision window
Ordering six processes, simulated with numbers Pro: opens with a Pro, Premium or Ultimate pass
The same six invented processes, started on three different plans, end a season with two offers open together or with four. A simulator runs each plan day by day, so the difference is measured rather than argued.
In this part:
- Six invented processes and their clocks
- Three plans, simulated day by day
- What counting back costs, and when not to
1 runnable example (JavaScript) · about 4 minutes
Opening this part with your pass…
This part opens with any MySmartCoPilot pass.
- Pro pass · 1 week₹79$2.99
- 30 days₹179$5.99
- 1 year₹1,699$45
One payment; a pass never renews. The price shown is the total you pay: no fees or charges are added at checkout.
Passes can’t be bought right now, so this part can’t be opened at the moment. The free part above stands on its own. If you have a pass, enter your licence key.
It also opens every other in-depth part in Learn and every Pro tool. Sales are final, except where the law gives you a right to withdraw, for example in the EU and the UK (refund policy).
Deadline clashes, pausing and withdrawing, decided in advance Pro: opens with a Pro, Premium or Ultimate pass
Offers rarely arrive in the order you planned, so the rules for a clash work best when they are written down before one happens. This part works a clash as a drill, then sets out when to pause, speed up or withdraw.
In this part:
- A deadline clash, worked as a drill
- Pause, speed up or withdraw: choosing with a table
- Campus seasons: rules that set the order
1 diagram · 1 runnable example (JavaScript) · about 11 minutes
Opening this part with your pass…Pro part. It opens with the same pass as the part above.
A tracker with day counts, and a weekly review Pro: opens with a Pro, Premium or Ultimate pass
A tracker turns a season from memory into a list of next actions. This part gives its fields, a program that computes the two day counts that drive each week, and a weekly review scored with a rubric.
In this part:
- The fields, and why each one is there
- Day counts that tell you what to do today
- The weekly review, scored with a rubric
- What to keep from the three parts
1 runnable example (JavaScript) · about 5 minutes
Opening this part with your pass…Pro part. It opens with the same pass as the part above.
Practise: clocks, moves and counting back
The self-check below returns to the clocks, the four moves and counting back. It picks the idea you have answered least well so far and brings a missed question back once:
Practice that adapts to you
Practise this lesson
9 questions about 9 ideas of this lesson. Each answer is explained at once, and what you get right is kept in this browser.
Interview questions
The warm-up is answered in full; the other three test the season’s plan under pressure:
-
Fresher to senior · Warm-up
Are you interviewing with other companies?
Answer honestly, in a sentence or two, with the dates that matter. "Yes, I am in two other processes, and one has a final round next week, so I wanted you to know in case an offer there comes with a deadline" is a complete answer. You do not have to name the other companies or say what they offer, and you should never invent a process to create pressure. The question usually comes from a recruiter planning a timeline, so the useful part of your answer is when you may need a decision. If you are not interviewing anywhere else, say so: it is not a weakness, and it tells the recruiter there is no deadline to plan around.
-
Fresher to senior
An employer offers you a job and wants an answer in five days. Your first choice holds its final round in nine days and usually decides about ten days after that. What do you do, step by step?
-
Fresher
You have six applications open, and two final rounds have landed in the same week as a university exam. How do you decide what to move, pause or drop?
-
Fresher to mid
Your first-choice employer asks candidates to wait about a year before reapplying for the same type of role. How does that change when and how you apply there during your season?
Then choose your answer to two follow-ups, and read why the others fall short:
Checkpoint
Interview round: other processes
Key takeaways
- Published clocks run from days to 6 to 8 weeks, and a failed attempt can start a wait of six months to a year.
- Four moves make one plan: practice processes first, slow processes early and fast ones late, one tracker, and rules decided in advance.
- A process starts in the window’s first week minus its weeks to an offer, so the offers you care about arrive together.
- On campus, the placement cell’s rules can end a season at the first offer.
Terms in this lesson
- decision window
- The week or two in which you want the offers you care about most to be open at the same time, so that you can compare them; each process starts early enough for its offer to arrive then.
- practice process
- A real application to an employer you would join but rank lower, started before the processes that matter most, so that your first real interview rounds carry less at stake.
References
- Our hiring process (How we hire) (Google Careers)
- Interviewing at Google: best practices, advice and tips (Google Careers)
- Online Assessment Prep: Software Development Engineer II (Amazon Jobs)
- SDE II Interview Prep (Amazon Jobs)
- Interviewing at Amazon: what to expect and how to prepare (Amazon Jobs)
- Software engineer full loop interview prep (links the Full Loop Interview Guide) (Meta Careers)
- What is a cooldown period and how does it impact my ability to take an assessment? (CodeSignal Help Center)
- Placement policy and internship policy (for companies) (Students' Placement Office, IIT Kanpur)
Related tools
Report a problem with this lesson
Kept only in this browser. Your Learn progress