Starting a new tech job? Learn how to ace your first 90 days with this actionable 30-60-90 day plan. Includes real examples, weekly prompts, and proven strategies to earn trust, build influence, and set yourself up for early promotions.
Let me tell you a quick story.
A few years ago, I joined a tech company as a Site Reliability Engineer. It was one of those moments where excitement meets pressure. I had to prove myself. But I also knew this: the first 90 days are your best chance to shape how people see you for the next 900.
Fast forward nine months, and I wasn’t just part of the team—I was leading one. And it wasn’t because I worked late nights or said yes to everything. It was because I had a plan.
This post is that plan. Whether you’re in your first tech job or switching to a new company, these 90 days can be your launchpad for faster growth, influence, and even early promotions.
Let’s break it down in depth, phase by phase, with real examples, psychological insights, and proven tactics.
Phase 1: The First 30 Days – Foundation & Observation
✅ Your Mindset: Learn before you lead
In your first month, your primary job isn’t to impress people with your technical wizardry. It’s to listen, observe, and absorb, simply keep your mind open. You’re building your foundation. Think of yourself as an anthropologist—study the rituals, understand the unwritten rules, and identify power dynamics, understand the work culture of the team where you are going to work, and understand colleagues. Your first 90 days can make you or break you; prepare such a mind.
Core Objectives:
- Understand the company culture
- Learn how your team operates (meetings, deployment cycles, review practices)
- Build relationships with key stakeholders
- Familiarize yourself with systems, codebases, and tools
Tactics:
1. Schedule 1:1s Early
Set up short, informal introductions with your manager, immediate team, and at least a few people from related departments like QA, product, and design. Ask questions like:
- “What’s something you wish you knew when you started here?”
- “What makes someone successful in this team?”
- “How do you prefer to communicate—Slack, email, Zoom?”
Document what you learn. These will help you align your approach and avoid pitfalls.
Example: When I joined a fintech startup, I learned from an early 1:1 with the DevOps lead that the team preferred async updates over live meetings. So instead of pushing for standups, I focused on rich Slack updates—which was noticed and appreciated.
2. Decode Success
The biggest mistake you can make is assuming you know what success looks like. Ask your manager:
*”If we were to look back 90 days from now, what would you consider a successful ramp-up for me?”
Not only does this give you clarity, but it also shows initiative and maturity.
3. Learn the Tools and Tech
Don’t just skim the README. Dive deep:
- Clone the repos
- Understand the CI/CD flow
- Set up the local dev environment
- Explore staging vs production environments
Create a checklist for all the tools and permissions you need access to. If you find gaps in the onboarding docs, offer to improve them—that’s a win-win.
4. Shadow Before You Solve
Join design reviews, code walkthroughs, and incident response retros. Ask questions respectfully. Most senior engineers will gladly explain context if they see you’re genuinely curious.
5. Observe Communication Dynamics
- Who drives decisions in meetings?
- How are disagreements handled?
- What’s the tone of internal communication?
This helps you model the behavior that resonates with the culture, while staying authentic.
Phase 2: Days 31-60 – Deliver & Build Credibility
✅ Your Mindset: Add value without asking for credit
Now, it’s the 2nd chapter of your first 90 days. You’ve built some context. Now it’s time to show that you can be trusted to get things done. This doesn’t mean working overtime. It means showing consistency, thoughtfulness, and ownership.
Core Objectives:
- Make a visible impact with a quick win
- Build confidence with peers and manager
- Demonstrate learning agility and accountability
Tactics:
1. Identify a Quick Win
Look for something that’s broken or inefficient but fixable within 2-3 days:
- Improve the deployment script
- Create a monitoring dashboard for a noisy service
- Automate a manual step in QA
Example: A developer I mentored recently cleaned up unused secrets in HashiCorp Vault. It took him two days, but the team had been ignoring it for weeks. That initiative helped build his reputation fast.
2. Own a Small Tool or Process
Don’t try to master everything. Pick one thing your team touches frequently:
- Is it Jenkins for builds?
- ArgoCD for deployments?
- Sentry for error logging?
Learn it deeply. Document it. Start becoming the person others go to for it.
3. Improve Documentation or Onboarding
The bar is often low for documentation. Just by improving onboarding steps or clarifying README instructions, you add lasting value.
4. Ask for Small Responsibilities
Request ownership of a sprint task or internal service. Make sure it’s visible and relevant. Then execute reliably.
Pro Tip: Underpromise, overdeliver—but communicate throughout. Don’t disappear for two weeks on a task.
5. Contribute in Retros and Planning
Start speaking up in retros. Share what you observed, what confused you, and any ideas for small experiments. Be constructive, not critical.
Example: In my second month at a new role, I suggested reducing the size of a staging environment to save costs. It wasn’t groundbreaking, but it sparked a broader FinOps discussion that positioned me as thoughtful about business impact.
Phase 3: Days 61-90 – Influence & Strategic Visibility
✅ Your Mindset: Move from executor to collaborator
You’ve proven you can learn and execute. Now it’s time to level up. Promotions aren’t just about skill—they’re about trust, visibility, and alignment with broader goals.
Core Objectives:
- Show strategic thinking
- Influence peers and adjacent teams
- Get feedback that sharpens your growth path
Tactics:
1. Present Something to the Team
It could be:
- A tool you evaluated and tested
- A bug you fixed with learning attached
- A proposal to improve something that affects multiple teams
Even informal sessions matter. It builds your brand and shows communication ability. Be presentable, it means that you can present your works and initiatives.
2. Connect Business with Engineering
Too many engineers focus only on code. Promotions happen faster when you align with customer impact.
Ask your PM or Customer Support rep:
“What’s a technical issue our customers repeatedly face?”
Find a way to improve it, or surface it better in metrics and logs.
3. Represent the Team Outside the Team
Volunteer to:
- Join an interview panel
- Represent engineering in product sprint reviews
- Contribute to inter-team Slack channels
This increases your sphere of influence.
4. Ask for Feedback Before Review Cycles
Before your 90-day check-in, proactively ask your manager:
“What would you like to see more of from me?”
Then act on it. Feedback without execution is a wasted opportunity.
5. Create a Vision for Your Next 90 Days
Prepare a small document or 2-slide summary:
- Wins so far
- Lessons learned
- Areas of growth
- What do you want to own next
This is the single most powerful way to frame yourself for early leadership opportunities.
Bonus Section: Common Mistakes to Avoid
- Trying to Be a Rockstar Too Soon
Don’t rush to prove brilliance. People promote those they trust—not just those who’re technically good. - Overpromising
Wanting to help is great, but never commit to things you don’t fully understand. Say: “I’ll need to check and get back” instead. - Staying in Your Lane Too Long
By Day 60, start looking beyond your Jira board. Ask what upstream and downstream teams are solving. Show interest. - Being Passive in 1:1s
Your manager isn’t a mind reader. Share what’s working, what’s not, and what you’re curious about.
Templates You Can Use
📌 30-60-90 Plan Template (Tech-Focused)
| Phase | Focus | Action Items | Success Metrics |
|---|---|---|---|
| Days 1-30 | Learn & Observe | 1:1s, Read Docs, Shadow Teams, Map Systems | Internal network built, onboarding gaps identified |
| Days 31-60 | Contribute | Quick Wins, Own Process, Improve Docs, Ask for Tasks | Contributions merged, feedback received |
| Days 61-90 | Influence | Present Demos, Get Feedback, Align with Business Goals | Visibility across team, roadmap alignment |
🧠 Weekly Reflection Prompts
- What did I learn this week?
- What blockers did I face?
- Who did I connect with?
- How did I add value?
- What will I improve next week?
Keep this in Notion or Google Docs. It becomes your promotion journal.
Final Thoughts: Promotions Begin on Day One
The first 90 days aren’t about becoming a hero. They’re about building trust, showing curiosity, learning the context, and delivering impact—slowly but steadily.
People will remember how you made them feel, how reliable you were, and how you made their work easier.
If you’re intentional, you won’t just thrive in your new job. You’ll grow into a role that’s bigger than what you were hired for.
Because career growth isn’t magic. It’s momentum, built day by day.
So take a deep breath. Make your plan. And begin.
If you’d like a free Notion template or editable Google Sheet for your 30-60-90 plan, drop a comment or send a message. Let’s grow together.