Your First 90 Days in a New Tech Job: A Week-by-Week Guide

You've accepted the offer, negotiated your start date, and now you're counting down to day one. Your first 90 days in a new tech job are critical—this probationary period determines not just whether you'll succeed in the role, but how quickly you'll be trusted with meaningful projects, considered for promotions, and integrated into the team's inner circle.

According to research from LinkedIn, new hires who actively build relationships and demonstrate early wins in their first three months are significantly more likely to receive positive performance reviews and stay with the company long-term. Yet most tech professionals approach onboarding passively, waiting to be told what to do rather than proactively shaping their integration.

This guide breaks down your first 90 days week by week, with specific actions for both in-office and remote tech roles across the United States and Canada. Whether you're joining a startup in Toronto or a Fortune 500 company in Seattle, these strategies will help you build credibility fast.

Days 1-30: Listen, Learn, and Build Your Foundation

Your first month is about absorbing context. You're not expected to revolutionize anything yet—your job is to understand how things work, who the key players are, and where the land mines are buried.

Week 1: Set Up Your Intelligence-Gathering System

In your first week, create a simple document to track:

• Key people and their roles – Go beyond the org chart. Who actually makes decisions? Who has institutional knowledge? Who are the connectors?
• Acronyms and terminology – Every company has its own language. Document terms as you hear them.
• Recurring meetings and their purpose – Which meetings are critical? Which are informational? Who drives the agenda?
• Unwritten rules – Does the team prefer Slack or email? Are cameras-on expected in video calls? Is 9 AM really 9 AM or does everyone drift in by 9:30?

Schedule 15-30 minute introductory coffee chats with at least 10-15 people across different teams in your first two weeks. Ask open-ended questions: "What do you wish you'd known when you started?" and "What's the most important thing I should understand about working here?" These conversations pay dividends for months to come.

Week 2-4: Identify Your Quick Win

By week two, you should be looking for a small, visible project you can complete in 3-4 weeks. This isn't about tackling the company's biggest problem—it's about demonstrating competence and building trust.

Good quick wins for tech roles:

• Documenting an undocumented process that the team references frequently
• Fixing a nagging bug or tech debt item that's been on the backlog
• Improving test coverage on a critical component
• Creating a dashboard or report that increases visibility into team metrics
• Streamlining a manual workflow with a simple script or automation

Key takeaway: Your first win should be something your manager or team lead has mentioned as annoying but not urgent enough to prioritize. When you solve it without being asked, you demonstrate initiative and good judgment simultaneously.

Days 31-60: Demonstrate Value and Expand Your Network

Month two is where you shift from observer to contributor. You've completed your quick win, you understand the team's rhythm, and now you're ready to take on more substantial work.

Navigating Your First Code Review or Design Critique

For developers, your first code review as the submitter is a cultural litmus test. In US and Canadian tech culture, feedback is expected to be direct but constructive. When you receive critical feedback:

1. Assume good intent – Even if the tone feels blunt, reviewers are trying to maintain code quality, not attack you personally
2. Ask clarifying questions – "Can you help me understand the reasoning behind this approach?" is always welcome
3. Avoid being defensive – Responding with "That's how we did it at my last company" immediately signals you're not adapting
4. Thank people for thorough reviews – Explicitly appreciate detailed feedback, even when it requires rework

When you're reviewing others' work, err on the side of asking questions rather than making demands. "Have you considered [alternative approach]?" lands better than "This should be done [different way]."

Building Relationships in Remote and Hybrid Settings

If you're working remotely—increasingly common in Canadian and US tech markets—you need to be more intentional about relationship building. According to Harvard Business Review, remote workers often struggle with visibility and are passed over for opportunities simply because they're not top-of-mind.

Strategies that work:

• Turn your camera on in meetings, even when others don't
• Contribute to team Slack channels beyond just work topics—share relevant articles, celebrate wins, participate in watercooler chat
• Volunteer for cross-functional projects that increase your visibility beyond your immediate team
• Set up virtual coffee chats with people you'd normally run into in an office
• If you're hybrid, be strategic about which days you're in-office—prioritize days with team meetings, collaborative work, or social events

In month two, aim to have meaningful interactions with at least three people outside your immediate team every week. This builds the cross-functional network that becomes invaluable when you need information, resources, or internal advocates later.

Understanding North American Workplace Communication Norms

If you're new to US or Canadian tech culture, certain communication patterns may feel unusual:

• Small talk matters – Brief personal connection ("How was your weekend?") before diving into business is expected, even in Slack
• Directness is valued – You don't need to apologize excessively or over-soften messages. "I need this by Thursday" is perfectly appropriate
• Speaking up is expected – Silence in meetings is often interpreted as disengagement. You don't need a perfect idea to contribute—asking good questions is equally valuable
• "Let me get back to you" is acceptable – You don't need to have all answers immediately. Saying "I need to check on that and I'll follow up by end of day" demonstrates professionalism

For more on communicating your wins effectively as you gain traction, see our guide on how to talk about your achievements without sounding arrogant.

Days 61-90: Own Your Role and Plan Ahead

By month three, you should be operating with increasing independence. Your manager should feel confident assigning you work without extensive hand-holding, and you should have a clear picture of how success is measured in your role.

Preparing for Your 90-Day Check-In

Most companies conduct a formal or informal review around the 90-day mark. Approach this proactively by preparing:

1. A summary of what you've accomplished – List specific contributions with measurable impact where possible
2. What you've learned about the role – Show you understand the priorities and challenges
3. Questions about expectations – "What would success look like for me in the next quarter?" and "Are there areas where you'd like to see me develop?"
4. Your initial goals for months 4-6 – Demonstrate forward thinking

Don't wait for your manager to schedule this conversation—request it yourself around day 80. This shows ownership and gives you time to course-correct if there are any concerns.

Common Pitfalls to Avoid in Your First 90 Days

Setting Yourself Up for Long-Term Success

As you close out your first 90 days, shift your mindset from "new hire" to "established team member." This means:

• Taking on a mentorship role – Even if you're junior, there's always someone newer who can benefit from what you've learned
• Contributing to team improvements – Now that you understand the systems, you can suggest refinements with credibility
• Building expertise in a specific area – Identify one domain where you can become the go-to person within 6 months
• Expanding your technical or domain knowledge – What skills will make you more valuable in this specific role?

According to the U.S. Bureau of Labor Statistics and Statistics Canada, tech professionals who invest in continuous learning and relationship-building in their first year see faster salary growth and career advancement than those who simply execute their immediate job requirements.

Your 90-Day Success Checklist

Use this final checklist to ensure you've covered all the essentials:

• ✓ Completed at least one visible project or meaningful contribution
• ✓ Had 1:1 conversations with 15+ people across different teams
• ✓ Understand your team's goals and how your role contributes to them
• ✓ Received and incorporated feedback on your work
• ✓ Identified at least one area where you can develop deeper expertise
• ✓ Built at least 3-5 relationships with people you can ask for help or advice
• ✓ Demonstrated you understand the company's culture and communication norms
• ✓ Scheduled or completed your 90-day check-in with your manager

Your first 90 days set the trajectory for everything that follows. By being intentional about building relationships, delivering early wins, and adapting to your new team's culture, you'll not only pass your probationary period—you'll position yourself as a valued, trusted team member ready for bigger challenges ahead.

And if you're still in the job search phase, remember that how you find the job matters too. Companies are more likely to invest in thorough onboarding for candidates who come through trusted channels. Learn more about why 70% of jobs never get posted and how working with human recruiters who actively market your profile can lead to better-fit roles where you'll thrive from day one.