First 90 Days at Your First IT Job: How to Make a Strong Start

The first 90 days set a reputation that takes 18 months to change. Five habits separate the freshers who get high-trust work early from the ones who get parked on documentation tickets.

Habit 1: ship something small in week two

A bug fix, a small UI tweak, a unit test for an existing module. The point is not the size — it is establishing the pattern that you commit code, open PRs, and respond to reviews. Managers remember the first PR.

Habit 2: take notes obsessively

Onboarding repeats the same answers for every newcomer. Senior engineers tire of explaining the same things three times. A personal wiki with every login, every deployment command, every “gotcha” you hear is a productivity multiplier and a goodwill builder when you share it.

Habit 3: ask one good question per day, not five mediocre ones

Batch your blockers. Try for 30 minutes, then ask. Phrase questions with context: “I want to do X, I tried Y and saw Z, my hypothesis is W — what am I missing?” This format gets respect and useful answers.

Habit 4: be early to standups, on time to reviews

Punctuality at remote-first companies is the silent signal that you respect the team. Two minutes early to every meeting, camera on, prepared. This single habit accounts for an outsized share of “they have a good attitude” feedback.

Habit 5: ask for a 30-day feedback chat

Schedule it yourself. Ask your manager two questions: what is going well, what should I do more of, what should I change. The conversation creates a goal-setting moment and signals that you take growth seriously.

What to avoid

• Office politics — listen, do not participate.
• Public criticism of code or processes — earn that right after six months.
• Comparing to college friends’ offers — different ladders, different speeds.