In the final round the hiring manager said three things clearly: you will join the retrieval platform team, your posting will be Hyderabad, and there is no night shift for this role. Nine weeks after joining, the student is in a different city, on a data-labelling and ticket-triage queue, on a rotating shift. He goes back to the manager and finds that the manager moved to another account six weeks ago. Nobody is lying to him. The letter he signed says something else, and the letter is the only thing that counts.
WHAT HE WAS TOLD (in the room) WHAT THE LETTER SAID (page 1)
"Retrieval platform team" Role: "AI Engineer - Trainee"
"Hyderabad posting" "Place of posting: as per
business requirement"
"No night shift for this role" (silent - no shift clause)
"Joining around July" "Date of joining will be
communicated separately"
Common in IT services and consultancy hiring, where a fresher is hired into a pool and allocated to whichever project needs bodies on the day they join. It also happens in GCCs and startups whenever the interviewing manager is not the manager you will report to. The people making the promises are usually sincere at the time; team plans, client contracts and their own jobs then change. Most damaging for students who chose one offer over another because of a spoken assurance about city or team. Linked modules: 6.9 (HR round, offer, BGV), 6.1 (How Indian companies actually hire), 6.8 (Resume, GitHub, LinkedIn, portfolio).
Three mechanisms combine, and only one of them involves anybody behaving badly.
1. The interviewing manager is often not the deciding manager. In a pooled hiring model, allocation happens after joining and is driven by which project has a slot. The person describing your future work may have no allocation authority at all, and may say so if you ask directly.
2. Silence in a document is not a promise; it is an open option. "Place of posting: as per business requirement" is not a trick clause — it is the company reserving flexibility it genuinely needs. A shift clause that is missing is not a guarantee against shifts. The absence of a term means the term is undecided, and undecided always resolves in favour of the party that writes the letter.
3. People move. The manager who promised the retrieval team was accurate about his own plan and then changed accounts. Nothing in the company's records connects his sentence to this student's file. Whatever was said has no owner once he leaves.
The deeper error is a wrong model of what an offer letter is. Students read it as a summary of the conversation. It is not a summary; it is the whole agreement, and any part of the conversation that did not make it onto the page has no standing. What you can enforce, and how, is a legal question and depends on your documents and your situation — but the practical position is simple enough: unwritten promises are not recoverable, and chasing them costs months you do not have as a fresher.
Convert promises into terms before you sign. It takes one email.
Step 1 — list every spoken promise, in the words they were said. Team, city, shift, joining month, technology, reporting manager, training track. Write them down the same evening, while they are still exact.
Step 2 — check each one against the letter. Mark PRESENT, PARTIAL or ABSENT. Anything not PRESENT is not yours yet.
Step 3 — send the plain request, once, and keep it warm.
"Thank you for the offer - I want to join, and I am accepting.
Three things came up in the final round that I could not find in the
letter, and I would like them recorded so there is no confusion later:
1 Place of posting: Hyderabad was mentioned. Could the letter name
Hyderabad, or name the cities it could be?
2 Team: the retrieval platform team was discussed. If allocation
happens after joining, that is completely fine - could you confirm
that in one line so I plan correctly?
3 Shift: I understood there is no night shift for this role. Could
the letter say whether shifts apply, and any shift allowance?
If any of these cannot be committed at this stage, please tell me and
I will accept as it stands. I would rather know now than assume."
Step 4 — read the reply as information, not as a formality. An amended letter is the best outcome. A written email from HR saying "allocation is decided post joining and posting can be any of these four cities" is the second best, and it is honest — save it. A refusal to put anything in writing, or a reply that avoids the question twice, tells you the promise was never a commitment; you may still accept, but now you accept with your eyes open.
Step 5 — if you have already joined and the work is not what was described. Do not open with the promise, because it cannot be proved. Ask for the written allocation and review process, do the assigned work visibly well for a stated period, and use the internal transfer or assessment route the company actually has. Keep a record of what you built anyway — that record, not the old promise, is what moves you.
Treat the offer letter as the entire agreement, because that is how everybody else treats it. Ask one question in the final round itself: "is the team and location decided at offer stage, or after joining?" — an honest interviewer will answer plainly, and the answer changes what you should expect. Get the joining month, the place of posting and the shift position written down before you accept, and accept graciously if they cannot be. Never decline a second offer on the strength of a spoken assurance in the first; decline on what is printed in both. Keep a dated note of every promise made to you, not to argue with later, but so you can ask about it clearly and early while goodwill still exists.
Q: "This letter says posting is as per business requirement. Are you comfortable with that?" Strong answer: say yes, then show you understood it — "I read that as allocation happening after joining, which is normal in a pooled model; may I ask what the usual cities are and when allocation is decided?" That answer tells the panel you read the document, you are not naive about it, and you can raise a concern without making a demand. Weak answer: "Sir you told me Hyderabad, so it is fine." It shows the candidate is relying on a conversation instead of a document, which is the exact habit that produces this War Room entry six months later.