First 90 Days Ramp-Up Guide
Landing the offer is step one; succeeding in your new engineering environment is step two. Follow this battle-tested 30-60-90 day milestone roadmap to build momentum, minimize imposter syndrome, and ship impactful code.
Days 1 – 30: Absorb, Configure & Ship First PR
Goal: Eliminate environment friction, build trust, and deliver low-risk quick wins.
Clone Main Repo & Run Local Test Suite
Set up local dev environment, Docker containers, secrets (.env.local), and pass all unit tests without errors.
Ship First Good-First-Issue or Docs PR
Tackle a low-risk bug or outdated readme to familiarize yourself with CI/CD, staging deployments, and team branch strategies.
Schedule 15-Minute Intros with Cross-Functional Teammates
Meet your product manager, QA partner, designer, and engineering teammates to understand their workflows and pain points.
Establish Weekly 1-on-1 Cadence with Manager
Agree on meeting timing, shared agenda format, and explicit performance criteria for your first 90 days.
Audit Core Conversion Funnel & Customer Support Tickets
Map drop-offs, review recurring customer tickets, and identify top churn factors.
Days 31 – 60: Deliver & Collaborate Autonomously
Goal: Own sprint tickets end-to-end, provide constructive code reviews, and learn incident mitigation.
Deliver First Non-Trivial Feature End-to-End
Break down a multi-day sprint story, design the solution, write automated tests, and coordinate rollout behind a feature flag.
Actively Review Peer Pull Requests
Review at least 3 peer PRs per week, asking thoughtful clarifying questions on architecture, test edge cases, and maintainability.
Shadow an On-Call Incident or Support Rotation
Observe telemetry dashboards (Datadog/Grafana), bug triage queues, and blameless incident mitigation.
Write PRD & Lead Sprint Grooming for High-Impact Feature
Author user stories, establish success telemetry metrics, and guide engineering estimations.
Days 61 – 90: Own, Influence & Align for Promotion
Goal: Establish component ownership, pitch developer ergonomics improvements, and conduct quarterly review.
Establish Ownership of a Service or Sub-system
Become the primary go-to engineer for a feature area, refining technical debt and documenting operational runbooks.
Propose an Architectural or Workflow Improvement
Identify developer friction (e.g. flaky tests, slow build times, or missing telemetry) and pitch a pragmatic refactor.
Conduct 90-Day Alignment & Growth Review with Manager
Review milestone goals achieved, calibrate strengths and growth areas, and outline next 6-month promotion/growth roadmap.
Present Next-Quarter Product Roadmap to Stakeholders
Balance technical debt, regulatory needs, and revenue expansion opportunities.