1:1 Meeting Topics for Software Engineers: How to Talk Code and Career

TL;DR

In 1:1 meetings, focus on -code health over bug fixes and career alignment over promotion timelines. Prioritize 3 key areas: Technical Debt, Project Ownership, and Skill Gaps. Preparation is key to driving meaningful conversations.

Who This Is For

This article is for Software Engineers (SWEs) at FAANG-level companies or similar, earning between $180,000-$300,000 annually, seeking to leverage 1:1 meetings for career advancement and technical growth, typically within 6-18 months of their current role.

What Should I Discuss in 1:1 Meetings as a Software Engineer?

Answer: Focus on technical contributions, career aspirations, and team dynamics, not just operational issues.

  • Insight Layer: Utilize the SMART Framework (Specific, Measurable, Achievable, Relevant, Time-bound) for project discussions.
  • Scene Setting: In a quarterly 1:1 at Google, an SWE shifted from complaining about workload to proposing a "Technical Debt Reduction Initiative", securing additional resources.
  • Not X, but Y:
  • Not just bug fixes, but code health metrics (e.g., reducing average bug resolution time by 30% in 60 days).
  • Not generic skill wishes, but specific technology deep dives (e.g., mastering Kafka within the next 9 months).

How Do I Effectively Discuss My Career Aspirations?

Answer: Align aspirations with company needs, quantify achievements, and propose a "Career Sprint Plan".

  • Insight Layer: Apply Maslow's Hierarchy of Needs to ensure aspirations are met in order (security, recognition, growth).
  • Scene Setting: A Microsoft SWE used a data-driven approach to show how their aspirations to lead a team would fill a management gap, leading to a trial leadership project.
  • Not X, but Y:
  • Not asking for a promotion, but outlining a contribution roadmap leading to one (e.g., taking on 2 additional high-visibility projects within the next 12 weeks).
  • Not seeking vague feedback, but requesting targeted skill assessments (e.g., "How can I improve my architecture design skills?").

What Technical Topics Should I Prepare to Discuss?

Answer: Prepare to dive deep into 2 recent projects, focusing on architectural decisions and lessons learned.

  • Insight Layer: Use the 5 Whys Method to prepare in-depth analyses of project challenges.
  • Scene Setting: In an Amazon 1:1, an SWE's preparedness to discuss the trade-offs of using DynamoDB in a recent project led to a discussion on leading a database optimization task force.
  • Not X, but Y:
  • Not just project outcomes, but decision-making processes behind them.
  • Not all projects, but those with high visibility or complexity (e.g., focusing on a project that increased API throughput by 40%).

How Can I Ensure My Voice is Heard on Team and Company Initiatives?

Answer: Propose actionable initiatives aligned with company goals, and volunteer for cross-functional tasks.

  • Insight Layer: Leverage Influence Mapping to identify key stakeholders for your initiatives.
  • Scene Setting: A Facebook SWE suggested a "Code Review Quality Improvement" initiative, gaining support by involving multiple engineering leads.
  • Not X, but Y:
  • Not just suggesting, but leading small initiatives to build credibility.
  • Not solo efforts, but building a coalition of supporters across teams.

Preparation Checklist

  • Review Project Logs: Ensure deep knowledge of 2 key projects (Focus on architectural decisions).
  • Skill Gap Analysis: Identify 1 key skill to deepen (e.g., cloud computing) and propose a learning path.
  • Company Goal Alignment: Map your aspirations and projects to current company objectives.
  • Prepare SMART Initiatives: Have 1 actionable initiative ready (e.g., reducing deployment time by 20% in 90 days).
  • Work through a structured preparation system (the PM Interview Playbook covers "Effective Technical Communication" with real debrief examples, useful for 1:1 meetings too).

Mistakes to Avoid

| BAD | GOOD |

| --- | --- |

| Complaining About Workload | Proposing a "Work Efficiency Initiative" with Metrics |

| Vague Career Aspirations ("I want to lead") | "In 18 months, I aim to lead a team by first taking on a trial project within the next 6 months." |

| Unprepared for Deep Technical Discussions | Prepared to Discuss 2 Projects with Architectural Decisions and Lessons |

FAQ

Q: How Often Should I Bring Up Career Aspirations in 1:1s?

A: Every 3rd meeting, ensuring each discussion builds on the previous with tangible progress or new aspirations.

Q: Can I Discuss Non-Technical Topics in 1:1 Meetings?

A: Yes, but ensure they're job-adjacent (e.g., work-life balance in relation to project demands) and take up no more than 20% of the meeting.

Q: How Do I Handle If My Manager Isn’t Supportive of My Initiatives?

A: Realign or Reframe: Either ensure better alignment with company goals or reframe the initiative to address a more pressing company need, then escalate politely if still met with resistance.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.

Related Reading