The screening call

Four beats: what you are, what you own, one concrete proof, what you want next. Sixty seconds, not four minutes.

Do not walk your career chronologically. Starting at your first job and working forward is the single most common way this answer dies — by the time you reach the interesting part they have stopped listening.

This works because it names a real limitation without blaming a person, and then converts into a reason to want their job. Every good "why leaving" answer is secretly a "why you" answer.

Give the number with its structure attached, because the structure is where the leverage is. If your package has no PF and no deductions, your take-home and your cost-to-company are effectively the same figure — almost no Bangalore offer works that way, and the recruiter does not know it yet. The script below uses the worked example from R12: ₹12 lakh fixed, ₹1,00,000 a month in hand. Put your own two numbers in it.

That paragraph does four jobs at once: it is truthful, it is verifiable against your payslip, it teaches the recruiter that your effective rate is higher than your CTC looks, and it anchors before they anchor you. The full arithmetic is in R12.

Give the real number, then immediately give the shortest credible path: "It is X days on paper. I have a good relationship with my lead and I have negotiated buyouts before, so realistically I can be with you in [shortest honest figure]."

If your notice is long, this is the moment to plant the buyout: ask whether they reimburse it. Many companies do, it costs them almost nothing structurally, and it is the easiest concession you will ever win — but only if you raise it early rather than at offer stage.

Say it in the past tense if you can. "I am open to relocating" and "I have relocated" land completely differently — one is an intention, the other is a fact they can plan around. If you have not moved yet, a fixed date is the next best thing.

Never say "no, you are the only one." True or nearly true is fine here, but do not invent a specific company or a specific number: you may be asked to name it, and a fabrication that unravels ends the process.

Use the four-beat shape and rehearse it out loud tonight, because you will give this answer in every single loop you enter:

• Problem. A clinic-booking platform needed to take appointments online and keep every clinic's calendar in sync.
• Your role. You designed and deployed the service layer across four environments.
• The hard part. Four environments with different data, secrets and provider keys, plus a live dashboard over bookings, no-shows and reliability metrics.
• The result. Infrastructure cost down twenty percent.

No jargon the recruiter cannot repeat. "Service layer" is fine; "typed DTO validation at the boundary" is not — save that for R5.

Have three separate numbers ready and keep them consistent across every conversation, because they get written down and compared later. For the example profile: TypeScript six, React five, Node roughly five. If a number is smaller than the job asks for, give it and immediately give the strongest adjacent evidence rather than padding it.

Never dispute the observation — it is correct, and your resume does read frontend-first. Concede it in four words, then move the conversation to the part of your backend work that is hardest to fake: production ownership.

The shape is concede, quantify, prove, redirect. The proof has to be a system you ran, not a framework you touched.

Recruiters call at 3pm on a Tuesday while you are in a standup. The instinct is to take it anyway because you do not want to seem uninterested. Do not — a rushed screening call is where the bad number gets said out loud, and the number is the one thing you cannot walk back.

Rescheduling costs you nothing if you do it in one sentence, give a specific slot, and sound pleased rather than inconvenienced.

A third of the calls you take will be from a staffing firm, a consultancy, or a platform sourcer on Naukri, InstaHyre or Cutshort. The questions look identical to a company recruiter's. The stakes are not.

• Ask who the client is before you say a number. "Which company is this for?" If they will not name it, give a range instead of a figure — you cannot anchor properly against an unnamed employer.
• Never let two agencies submit you to the same company. Duplicate submission gets your profile rejected by both, and it happens constantly. Keep a note of every company each recruiter names, and say plainly: "I am already in process there through someone else."
• Ask whether it is payroll or contract. "Is this a direct role or C2H?" Contract-to-hire at ₹26 lakh is not the same offer as ₹26 lakh on the company's payroll — no ESOPs, different notice, and the conversion is a promise, not a term.
• The questionnaire before the call. Many recruiters now screen over WhatsApp or a form first — current CTC, expected CTC, notice, location, five lines on your last project. Treat it as the real screen, because it is: write it in a text editor, use the same numbers you would say out loud, and keep it to five lines.

Ask four, and pick ones a recruiter can actually answer. This is also your only free intel-gathering pass before R12, so make the fourth one about the band.

• What does the loop look like — how many rounds, and what is in them? This tells you whether you are walking into a machine coding round or a DSA round, which decides what you revise this week.
• Is this a new position or a backfill? A backfill means someone left; a new position means the team is growing and the scope is less defined.
• Who would I report to, and how big is the team? Four engineers and a founder is a different job from forty and an EM.
• What is the band for this role? Ask it plainly and early. Recruiters usually answer, and it is far cheaper to learn the ceiling now than after four rounds.

• Highest qualification and year of passing. <Your degree>, <your college>, <the year>.
• Any employment gaps? If none: None — <the month and year you started> to today, continuous. If there was one: <the months>, <the reason, in one line> — and continuous since <the date you went back>.
• Have you led a team? How many people?
• Are you interviewing for frontend, backend or full-stack roles? Answer full-stack, and if pressed say frontend-leaning full-stack — that is what your resume actually shows, and pretending otherwise gets exposed in R5.
• Are you comfortable with the office location and a five-day model?
• Do you have a passport? (Asked by service companies with onsite roles.)
• What is your date of birth / do you have a PAN? (Background verification prep.)