DEV Community: Yatharth Verma

The Bond Clause Trap: Why Companies Ask It, and How Students Should Actually Respond

Yatharth Verma — Thu, 06 Aug 2026 09:38:33 +0000

Somewhere in almost every Indian IT services HR interview, the question shows up in some version: "We have a service agreement — you're okay with that?"

Most students treat it as paperwork disguised as a question and answer on autopilot: "Yes, I'm fine with it." Technically correct, and still, this is one of the most consistently mishandled moments in the entire interview — not because the answer is hard, but because almost nobody understands what's actually being evaluated when it's asked.

What a bond clause actually is

Strip away the anxiety around the word "bond" and it's a fairly simple arrangement: the company invests real money training a fresher — often weeks of onboarding, tooling, structured learning programs — before that person generates any billable value. The service agreement is the company's way of protecting that investment, committing the candidate to stay for a minimum period, usually with a financial penalty for leaving early.

It's not unique to any one company, and it's not secretly exploitative — it's a fairly standard response to a fairly real cost. Training a fresher who leaves after four months is a sunk cost with no return, and at the scale Indian IT services companies hire, that adds up fast.

Understanding this changes how the question should be answered, because it stops being a trick and starts being a genuinely reasonable thing to have an informed opinion about.

What the question is actually testing

When an HR panelist asks if you're comfortable with the bond, they're rarely testing whether you've read the fine print. They're testing three things at once:

Whether you understand the terms, or you're agreeing blindly without knowing the duration, the penalty, or the conditions.

Whether you're going to be a flight risk — someone who takes the offer as a fallback while actively interviewing elsewhere and leaves the moment something better comes along.

How you handle a slightly uncomfortable, binding question — composure here is itself part of what's being read, separate from the content of the answer.

A flat "yes" with no hesitation can read as either genuine confidence or blind agreement, and panelists have heard enough of both to notice the difference in tone.

The wrong ways to answer it

Answering too fast, with no acknowledgment of the terms. This can read as not having actually registered what's being agreed to — panelists have sat through enough of these interviews to tell rehearsed compliance from informed agreement.

Hesitating visibly, or asking "how long is it again?" in the moment. If you don't already know the duration and terms of the bond before you walk in, that's a preparation gap the interview will expose.

Volunteering doubt. Saying something like "I guess so, if I have to" signals exactly the flight-risk concern the question exists to screen for.

How to actually answer it

The strongest version of this answer does three things in one breath: shows you know the terms, frames the commitment as reasonable rather than reluctant, and stays brief.

"Yes, I'm aware of the service agreement and the training investment behind it, and I'm fully comfortable with that. I see it as a fair trade for the training and the opportunity."

That's it. No extra qualifiers, no trailing exceptions, no over-explaining. The panel isn't looking for a paragraph — a longer answer here usually reads as less confident, not more thorough.

Why this deserves more attention than it gets

Most interview prep treats the bond question as a minor formality tucked between "tell me about yourself" and "do you have any questions for us." It isn't minor. In a process where the real differentiators between similarly-qualified candidates are thin, this is one of the few moments where a panelist forms a genuine judgment about reliability rather than competence — and reliability, for a company hiring thousands of freshers a year, matters as much as raw skill.

The students who handle it well aren't the ones with better legal knowledge of the terms. They're the ones who took thirty seconds before the interview to actually know what they were agreeing to, instead of planning to figure it out from the offer letter later.

The real lesson underneath this one

The bond question is a specific case of a broader pattern in campus placements: the questions that feel like formalities are often the ones doing the most evaluative work, precisely because candidates don't prepare for them the way they prepare for the "real" questions. Every hour spent optimizing a DSA answer that's already strong is an hour not spent making sure the twelve-second response to the bond question doesn't come out hesitant or hollow.

Companies aren't hiding the ball here. The terms are usually available if you look — offer letter templates, senior students who've been through it, sometimes even the interview itself if you ask directly. The gap isn't information. It's that almost nobody treats this question as worth preparing for at all, until it's already gone badly.

If you want to practice this exact question live — not read the model answer, actually say it out loud under real interview pressure — try a free mock HR round: interviewphodo.com

Every TCS and Infosys HR Prep Guide Gives You the Same Script. None of Them Fix the Real Problem.

Yatharth Verma — Tue, 04 Aug 2026 06:48:34 +0000

Search "TCS HR interview questions" and you'll find dozens of near-identical guides. Same forty questions, same model answers, word for word in some cases. "Are you willing to relocate?" — "Yes, I see it as an opportunity for growth." "What's your expected CTC?" — "I'm flexible with the standard package." Every guide hands you the correct line.

And yet, every placement season, capable students still freeze on exactly these questions. If the right answer is this well documented, this freely available, this repeated across every prep blog in existence — why does the failure keep happening anyway?

Because the scripts were never the problem.

What the guides get wrong

Read through enough of these HR prep resources and a pattern emerges — not in the students, but in the resources themselves. Every one of them optimizes for the same thing: giving you the correct sentence to say. None of them address the actual skill being tested, which isn't knowledge. It's delivery, live, under mild real-time pressure, to a stranger evaluating you as you speak.

That's a different skill than memorization, and it doesn't transfer the way content does. You can read "yes, I'm comfortable relocating" a hundred times and still hesitate when a real HR panelist asks you the question directly, because reading a script and performing it live under evaluation are not the same rehearsal.

This is exactly the gap coaching centers and question-bank PDFs were never built to close. They can hand you the words. They can't hand you the composure to say them cleanly on the first try, with no visible pause, when it actually counts.

Why the pause is the real tell

Watch how these guides describe the ideal answer to the bond or relocation question, and they all say some version of the same thing: be honest, don't over-explain, keep it brief. That's good advice on paper. It's also advice almost nobody follows under actual pressure, because the natural human instinct when asked a slightly uncomfortable question is to hedge — add a qualifier, soften the yes, explain the exception before you've even confirmed the rule.

The guides tell you not to do this. None of them tell you how to not do this, because "just be confident" isn't a method — it's the outcome you get after enough real repetitions, not a mental trick you apply once, cold, in the one interview that matters.

What this means for how people should actually prepare

If the failure point is live delivery under mild pressure rather than knowledge of the correct answer, then reading more model answers is close to useless past a certain point. What actually closes this gap is being asked the real question, live, out loud, without the script in front of you — enough times that the pause disappears on its own, the way it does with any other skill that only exists in the doing of it, not the reading about it.

This is also, not coincidentally, exactly the piece missing from every resource I found. Dozens of guides for the content. Almost nothing for the delivery.

Why I'm building toward the missing piece

I've been building live AI mock interviews specifically because of this gap. Not another question bank — there's no shortage of those, and adding one more wouldn't move the needle. What's missing is a way to actually rehearse the moment itself: live, out loud, with feedback on the pause and the hedge, not just the words.

Reading the correct answer to the bond question a hundred times won't stop you from hesitating the one time it's asked for real. Saying it out loud, badly, then better, then cleanly, enough times before it counts — that's the part every existing resource skips.

If you've been through a TCS or Infosys HR round recently, I'd genuinely like to know — did you know the "right" answer going in, and did it still come out differently than you meant it to? And if you want to actually rehearse that moment live before your next interview: interviewphodo.com

Why India's Campus Placement System Is Broken — And What Actually Fixes It It's not a talent problem. It's a measurement problem.

Yatharth Verma — Fri, 31 Jul 2026 08:19:29 +0000

Every placement season, roughly the same story plays out on campuses across India. A student who can solve a hard DSA problem in fifteen minutes walks into the HR round and falls apart on a question that has no code answer: "We have a two-year service agreement — are you okay with that?"

Colleges call this a placement success or failure. It's neither. It's the predictable output of a system that was never built to measure what it claims to measure.

The system optimizes for the wrong thing

Ask any final-year student what "placement prep" means and you'll get some version of the same answer: solve more DSA problems, memorize more HR question banks, do more mock GDs. That's not preparation for a job. That's preparation for a filter.

And that's the actual root of the problem — campus hiring at scale isn't really an assessment of who'll be a good employee. It's a filtering mechanism for companies processing thousands of applicants against a handful of open roles. DSA rounds filter on pattern-matched problem solving because it's cheap to standardize and scale, not because it strongly predicts who'll be good in the actual job. HR rounds filter on compliance and composure — will you sign the bond, will you relocate without friction, are you going to be a low-maintenance hire.

Once you see it as a filter instead of an assessment, the whole system makes a strange kind of sense. It also explains exactly why it fails so many capable students: they're optimizing for the job, while the system is optimizing for throughput.

The real cost isn't the rejections — it's the unequal prep

Here's what almost never gets talked about honestly: preparation for this filter isn't equally available.

A student at a tier-1 college with an active placement cell gets structured mock interviews, seniors who've been through the exact process, and curated question banks specific to the companies visiting that year. A student at a tier-3 college, often with just as much raw ability, gets a PDF of "top 50 HR questions" circulating on WhatsApp and has to figure the rest out alone.

The gap isn't ability. It's access to realistic practice and honest feedback. And that gap is exactly where the entire coaching-center industry has built itself — charging real money for something that, structurally, should not need to be scarce or expensive. A mock interview is not a rare resource. It's an information-and-availability problem, and information-and-availability problems are usually the ones technology is good at closing, not widening.

The trap questions deserve to be named honestly

The bond clause question. The relocation question. The "what's your expected CTC" question. These get treated like minor formalities, but they carry real weight — a badly handled answer here can undo a strong technical round, and nobody formally teaches how to navigate them.

Part of why they trip people up is that they're dressed as small talk but function as evaluation. A recruiter asking about relocation isn't making conversation — they're checking whether you'll be friction later. A recruiter asking your expected CTC isn't negotiating — they're checking whether you understand the market and whether you're going to be difficult about a number that's usually already fixed by the package band.

Students aren't failing these because they lack the right answer. They're failing because nobody ever explained what the question is actually testing.

What would actually fix this

Not more content. There's no shortage of "Top 50 HR Questions" PDFs floating around already. What's missing is three specific things:

Practice that mirrors real pressure, not just real questions. Reading a question and its ideal answer teaches recall. It doesn't teach composure under live, real-time pressure — which is the actual skill being tested. The gap between knowing an answer and being able to deliver it calmly, out loud, in the moment, is where most placement failures actually happen.
Feedback that's specific, not generic. "Be more confident" is not feedback. "You looked away from the camera every time you were asked about weaknesses, and your filler-word rate doubled during the salary question" is feedback a person can actually act on. Most students never get this kind of specificity because it requires either an expensive coach watching closely, or a system built to measure it directly.
Equal access, regardless of which college or which city. The single biggest lever here isn't a better question bank. It's making high-quality, realistic, feedback-rich practice available to a student in a tier-3 college in the same way it's available to a student at a top-tier campus with an active placement cell — without the cost structure that currently gates it behind expensive coaching.

Why I'm building toward this instead of writing about it from the sidelines

I didn't start out trying to write a critique of campus placements. I started out trying to fix one specific piece of it — building an AI that actually interviews students live, gives them specific, real feedback on posture and filler words and composure, and trains them on the India-specific trap questions nobody formally teaches. That work is what forced me to actually understand how broken the underlying system is, not just how frustrating it is to go through.

I don't think AI replaces the value of a real placement cell, or a senior who's been through the exact process before you. But I think the gap between a student who has access to that support and one who doesn't is exactly the gap technology should be closing right now, not widening.

I'm building InterviewPhodo to close exactly that gap — live AI mock interviews with real feedback, built around the specific questions Indian campus recruiters actually ask. If you've been through this process recently, I'd genuinely like to hear what actually tripped you up: https://interviewphodo.com

I Built a real AI InterviewerThat Interviews B.Tech Students Before Their Real Recruiters Do

Yatharth Verma — Wed, 29 Jul 2026 09:13:27 +0000

Every placement season, the same thing happens on campus.

A student walks into the TCS or Wipro HR round knowing every DSA answer cold, and then freezes on: "We have a 2-year bond and posting could be anywhere in India — are you okay with that?"

That's not a technical question. It's a trap. And nobody trains for it, because there's no cheap, honest way to practice it — the only feedback most students get is a rejection email, or a senior's half-remembered war story from two years ago.

I've spent the last few months building the thing I wish existed when I was that student: an AI that actually interviews you, live, in your voice, and tells you the truth about how you did.

Why I even started this

Before this, I built ApexGrab. That project taught me something I didn't expect it to: most "AI-powered" tools people ship are really just a chatbot wearing a costume. Type a question, get a text answer, call it intelligence. It's fine for a lot of things. It is not fine for interview prep, because the entire skill you're trying to build — staying composed, thinking on your feet, holding eye contact while your brain is short-circuiting — doesn't show up in a text box. It shows up under pressure, in real time, out loud.

So the bar for this one was different from day one: it had to talk, it had to listen, and it had to watch.

The stack nobody warns you about

The idea is simple to say and genuinely hard to ship: a live video/audio AI interviewer that responds like a person, not a script.

Here's roughly what's under the hood:

Google's Gemini Live API powers the actual conversational avatar — the part that listens, thinks, and responds in near real-time.
Pipecat handles the AI orchestration layer, stitching together speech-to-text, the model, and text-to-speech into something that feels like a conversation instead of a call-and-response loop.
Daily.co carries the WebRTC video/audio pipe, because building your own real-time media infrastructure from scratch as a solo founder is a fast way to burn a year.
MediaPipe watches posture and eye contact in the background, frame by frame, and turns "you looked away a lot" into an actual number instead of a vibe.
FastAPI on Railway and Next.js on Vercel run the actual product, with Supabase holding users, sessions, and progress data.

The genuinely hard part wasn't any single piece. It was latency. A human interviewer can pause for half a second and it reads as thoughtful. An AI that pauses for half a second reads as broken. Getting the whole pipeline — speech in, model thinking, speech out — to feel like a real back-and-forth took far more tuning than the actual "AI" part of the AI interviewer.

Building in the questions that actually matter

The technology was only ever half the problem. The other half was knowing what to ask.

Generic interview questions are everywhere. What's missing is the India-specific stuff that actually decides outcomes at campus placements: the bond clause question, the relocation question, the "what's your expected CTC" question that has no good textbook answer. I built the interviewer around these specifically — TCS, Infosys, Wipro, Accenture, Cognizant, HCL, Tech Mahindra, Zoho — because a generic "tell me about yourself" bot doesn't prepare anyone for the moment that actually trips students up.

It also remembers. Session to session, it tracks where a student is weak and turns the dial up there instead of repeating the same easy round forever. That part mattered more to me than the flashy avatar — repetition without adaptation is just expensive busywork.

Where it actually stands right now

I'm not going to pretend this is some polished unicorn story. It's live, it's real, and it's in the unglamorous phase every solo founder knows: getting the first real users, watching where they drop off, fixing what breaks, doing it again the next day. Founders' Circle pricing exists because early users take a risk on something unproven, and that risk should be worth their while.

What I can say honestly: watching a student go from stiff, one-word answers in session one to actually holding a real conversation by session three is the reason I keep building this instead of something easier.

What I'd tell someone starting the same thing

Build the boring infrastructure first. The avatar is the part people notice; the WebRTC pipeline, the auth, the payment retries are the part that decides whether any of it works at 11 PM when a student is trying to prepare the night before their interview. Nobody claps for that work. It's the whole product anyway.

If you're a B.Tech student prepping for placements, or just curious how a live AI interviewer actually holds up under real conversation, I'd genuinely like to know what you think: interviewphodo.com