Probation Period in Tech: What to Expect and How Not to Mess Up the First 3–6 Months

Probation is not a hazing ritual, and it is not a free pass to coast. In most Indian private-sector tech offers it is a defined window—often three or six months—where both sides check fit. Confirmation is common when you show up reliably. Trouble usually comes from silence, missed commitments, or attitude problems, not from failing to be a genius in week two.

This is advice for people starting a new full-time role. Internships converting to FTE have a different political dynamic; see converting an internship if that is your path.

Read the paperwork first

Before day one, find the probation length, notice period during probation, any training bond, and what “confirmation” requires. Some companies run a formal review; others confirm by default unless something goes wrong. Do not assume Silicon Valley folklore applies to your employer’s HR policy.

Also note leave rules and WFH expectations during probation. Showing up late every day while claiming “hybrid culture” is a fast way to earn the wrong reputation.

What managers actually watch

They rarely expect you to redesign the architecture in month one. They do notice whether you ask clarifying questions, finish small tasks, write updates without being chased, and treat teammates decently. Reliability beats flash.

Pick one early win that is visible and contained: a bugfix with a test, a dashboard your team already wanted, documentation for an onboarding pain. Announce it lightly in standup—“done, here’s the PR”—rather than waiting for someone to discover it.

Habits that keep you safe

• Agree on priorities weekly with your manager. If priorities thrash, write them down in chat so you have a shared record.
• Escalate blockers early. Sitting stuck for four days looks worse than a ten-minute ask on day one.
• Learn the team’s review and deploy norms before inventing your own process.
• Be careful with leave in the first weeks unless it is urgent—optics matter even when policy allows it.

For a broader new-job framing beyond probation legalese, the habits in the first 90 days still apply.

Mistakes that create unnecessary risk

Job hunting loudly from the office laptop on week three. Arguing every code review as a personal insult. Comparing your new team constantly to your previous company. Ignoring on-call or support rotations you agreed to. None of these require malice—people do them when they are anxious—and all of them are noticed.

If feedback arrives mid-probation, treat it as a map, not a verdict. Ask what “good” looks like in the next four weeks and check in. Defensiveness turns a recoverable gap into a confirmation risk.

If confirmation feels shaky

Ask for a candid mid-point conversation rather than waiting for a surprise. Document commitments you met. If the role is a clear mismatch, start a quiet, professional search—browse roles on CareerCola—without burning bridges. Leaving during probation is sometimes the right call; ghosting or badmouthing is not.

Probation rewards boring excellence: clear communication, finished work, and a steady tone. You do not need to impress everyone. You need to be someone the team is relieved to keep.