Your First 90 Days as a Manager-Level Software Engineer

Starting a new manager-level software engineer role in a global market is both exciting and daunting. The first 90 days set the tone for your long-term success. Whether you're moving across continents or joining a remote-first multinational, this guide will help you navigate the critical early phase with confidence. I’ve coached dozens of engineering managers through this transition, and the patterns are clear: those who succeed focus on relationships, context, and quick wins—not just on code.

Before Day One: Pre-boarding Essentials

Your first 90 days actually begin before you start. Use the period between offer acceptance and your first day to gather context. Here’s what to do:

• Review company culture materials: Read the employee handbook, mission statements, and any engineering blog posts. Look for mentions of collaboration style, decision-making processes, and performance expectations.
• Set up 1:1s: Request a pre-start meeting with your hiring manager to clarify objectives. Ask: "What does success look like at 30, 60, and 90 days?"
• Understand the team structure: Get an org chart if possible. Identify your direct reports, peers, and key stakeholders. Familiarize yourself with their time zones—global teams often span 12+ hours.
• Prepare your environment: Ensure your development tools, VPN, and communication platforms work. A common mistake is losing the first week to IT setup.

For more on preparing your job search, check out JobQuip's software engineer job listings to understand market expectations.

Week 1-3: Build Relationships and Learn the Landscape

The first three weeks are about listening, not leading. Resist the urge to propose sweeping changes. Your goal is to build trust and understand the current state.

Key Actions

• Schedule 30-minute 1:1s with every direct report, peer, and cross-functional partner. Ask: "What's working well? What's not? What should I know about the team's history?"
• Learn the product and tech stack: Read documentation, review recent PRs, and attend stand-ups. Don't just skim—ask clarifying questions to show you're engaged.
• Map the decision-making power: In global companies, decisions often involve multiple time zones and cultures. Identify who holds technical authority, who influences roadmap priorities, and how escalations work.
• Observe team dynamics: Notice communication patterns. Are teams using Slack over email? Do they prefer async updates or synchronous meetings? Adapt to their norms.

Common Mistake to Avoid

Becoming the 'hero coder' : As a manager, your value isn't in writing the most code. Jumping into production fixes without context can undermine your team's autonomy and create bottlenecks. Instead, shadow an on-call engineer to understand incident response.

Week 4-6: Establish Your Leadership Identity

By week four, you should have a clearer picture of the team's strengths and pain points. Now it's time to start shaping your role.

Define Your Management Style

Share a "leadership user manual" with your team: a one-page doc explaining your communication preferences, decision-making approach, and how you give feedback. Example: "I prefer async updates in the morning; for urgent matters, ping me on Slack. I value data-driven decisions but trust your expertise on design."

Set Quick Wins

Identify a small, visible improvement you can deliver within your first 60 days. This builds credibility and shows you understand the team's challenges. Examples:

• Reduce meeting overload by canceling a recurring sync that no longer serves a purpose.
• Improve PR cycle time by introducing a lightweight code review checklist.
• Unblock a dependency that has stalled a key feature.

Align with Peers

Meet with other engineering managers and product leads. Discuss cross-team projects and shared metrics. For global roles, cultural fluency matters—learn how different regions approach deadlines, hierarchy, and conflict.

Week 7-9: Drive Your First Strategic Initiative

Now you have the context to propose a strategic change. Focus on one area where you can make a meaningful impact that aligns with business goals.

Craft a 90-Day Review Deck

Prepare a presentation for your manager and skip-level, summarizing:

• What you’ve learned about the team, tech, and business.
• Key observations (e.g., technical debt, process gaps).
• Proposed priorities for the next quarter.

Example: Improving On-Call Experience

Many teams suffer from burnout due to poor on-call rotations. You could propose:

• Introducing a tiered escalation model.
• Automating runbooks for common alerts.
• Setting a max on-call shift duration.

Measure Impact

Use existing dashboards or create simple metrics to track progress. For instance, track reduction in mean time to acknowledge alerts after implementing a new runbook.

For inspiration on career paths, see JobQuip's software engineer career path guide.

Week 10-12: Solidify and Plan Ahead

The final stretch of your first 90 days is about sustaining momentum and looking ahead.

Conduct a Personal Retrospective

Reflect on:

• What worked well in your onboarding?
• What would you do differently?
• What relationships need more investment?

Set Goals for Days 90-180

Work with your manager to define objectives for the next quarter. These should be SMART and aligned with team OKRs. For example: "Reduce cycle time from deployment to production by 20% while maintaining current defect rate."

Invest in Team Development

Start coaching your direct reports. Schedule career conversations, identify growth areas, and create development plans. Early investment in your team pays off long-term.

Frequently Asked Questions

How do I handle time zone differences as a global engineering manager?

Use asynchronous communication as the default. Record important meetings, document decisions in shared platforms (e.g., Confluence, Notion), and rotate meeting times fairly. Tools like World Time Buddy help schedule inclusive syncs.

What if I discover critical technical debt in my first 30 days?

Document it thoroughly and share with your manager and team. Propose a phased approach to address it, but avoid unilaterally pausing feature work. Frame it as a risk that needs prioritization.

Should I expect to write code as a manager-level engineer?

It depends on the company. Some expect hands-on technical contributions, others focus on people leadership. Clarify during the interview process. Many managers find occasional code reviews or prototyping helpful for credibility, but your primary role is enabling the team.

How do I build trust with a team that's skeptical of a new manager?

Listen more than you speak. Acknowledge their past work and don't dismiss existing processes immediately. Show vulnerability by admitting what you don't know. Consistently follow through on commitments.

What are the biggest red flags to watch for in the first 90 days?

• Lack of clear onboarding plan.
• Frequent firefighting or crisis mode in the team.
• High turnover or disengagement among team members.
• Inconsistent expectations from your own manager.

If you encounter these, raise them early with your manager. Sometimes the role isn't right, and it's better to know quickly.

Quick Checklist for Your First 90 Days

| Week | Action Items | |------|--------------| | 1-3 | 1:1s with all team members and key stakeholders; learn tech stack; map decision flow | | 4-6 | Share leadership manual; identify quick win; align with peer managers | | 7-9 | Deliver a strategic proposal; start measuring a new metric; inform your career aspirations | | 10-12 | Retrospective; set next-quarter goals; begin coaching direct reports |

Remember, your first 90 days are the foundation of your reputation. Move with intention, stay curious, and lead with service. Good luck.

Looking for your next manager-level software engineer role? Browse software engineer jobs on JobQuip for global opportunities. For interview tips, check our software engineer interview guide.