Landing the job is step one. What you do in the first 30–90 days determines your trajectory at the company for years. Here's the playbook that separates engineers who ramp quickly from those who struggle to find their footing.
The First Week: Observe, Connect, Don't Optimize
The biggest first-week mistake is trying to prove yourself by shipping code or proposing improvements. You don't know enough yet. Your job in week 1 is to absorb.
Day 1–2:
- Complete all HR/IT setup before anything else — laptop, access, accounts, Slack, GitHub
- Read your team's README, wiki, and any "new engineer" onboarding docs
- Have your manager block 30 minutes daily with you for the first 2 weeks (ask for this proactively)
- Schedule introductory 1:1s with every teammate — 20–30 minutes each
Day 3–5:
- Clone the repo and get a local development environment running — this is your first task
- Read recent pull requests merged in the last 30 days — understand what the team is building
- Attend all team meetings silently — just observe patterns, don't contribute yet
- Ask your manager: "What would make my first 90 days a success from your perspective?"
What you're learning:
- How does the team communicate? (Slack vs email, async vs sync, formal vs casual)
- How are decisions made? (Top-down from manager, consensus, RFC process?)
- What's the deployment process? (How often do they ship? How long does a PR take to review?)
- What's the unwritten culture? (Hours people keep, how they handle failure, how credit is given)
The First Month: Build Credibility Through Small Wins
Goal: Ship one meaningful thing by end of month 1. Doesn't need to be a feature — a bug fix, a test improvement, a documentation update all count.
Technical ramp:
- Pick up one small well-scoped ticket from the backlog — ask your manager or tech lead to help you choose
- Read the architecture docs and draw your own diagram — nothing helps you understand a system like trying to diagram it
- Pair program with a teammate on at least 2–3 occasions — ask to shadow someone fixing a bug
- Write down every acronym, tool, and system you don't understand — review list weekly
Relationship building:
- Continue 1:1s with teammates — go deeper in round 2, ask about their work and what they find challenging
- Ask good questions in meetings — not "what should I do next" but "I've been thinking about X, does that map to how the team thinks about it?"
- Volunteer for small cross-team tasks when asked — cross-team visibility early is valuable
What to avoid:
- Rewriting existing code because "you'd do it differently" — you don't know why it was written that way
- Skipping the architecture docs because "you'll just figure it out from the code"
- Keeping your head down and never talking to anyone outside your immediate team
The First 90 Days: Demonstrate Independent Judgment
By 90 days, the expectation (explicit or not) is that you're ramping toward independent contribution — not just executing assigned tasks.
Technical goals:
- Own a feature or technical area end-to-end (even a small one)
- Be able to explain your team's system architecture to a new engineer
- Have context on the current quarter's roadmap and how your work fits in
- Know the team's deployment pipeline well enough to debug a stuck deploy
Relationship and influence:
- Have a 90-day check-in with your manager: "Here's what I've been working on and what I've learned. What are the most important areas for me to focus on in the next 90 days?"
- Identify your closest collaborators — the PM, the designer, the adjacent team — and invest in those relationships
- Start contributing opinions in team discussions (not just in 1:1s with your manager)
Avoid these 90-day mistakes:
- Waiting to be assigned work instead of pulling work from the backlog
- Not updating your manager on blockers (managers can't help what they don't know about)
- Optimizing for looking busy vs actually shipping things
The 30-60-90 Day Framework
Keep a running doc (Notion, Google Doc) with:
- What I've shipped: PRs merged, bugs fixed, docs written
- What I've learned: Architecture, process, people
- What I'm uncertain about: Where you still need guidance
- What I want to accomplish next: Self-directed goals for the next 30 days
Share this with your manager in your 30-day, 60-day, and 90-day check-ins. It signals maturity, self-awareness, and initiative — the same qualities that drive early promotions.
Getting Your Next Promotion Faster
Engineers who get promoted quickly in their first 12–18 months do three things consistently:
- Volunteer for high-visibility work — the projects leadership pays attention to
- Make their impact visible — write weekly updates, share wins in Slack
- Act at the next level before being promoted — do what a senior engineer does before your title changes
The interview got you in the door. What you do in the first 90 days determines everything after. Approach it with the same intentionality you brought to landing the job.
Use CareerLift.ai to continue practicing your communication and interview skills — as you grow and start interviewing for your next role, the practice compounds.