Complete Guide to English 1:1 Meetings: From Career Growth Conversations to Feedback Skills

• Introduction
• The Structure of a 1:1 Meeting and Its Core English Expressions
  • The Five-Stage Structure of an Effective 1:1
  • Opening the Meeting: Personal Check-in Expressions
  • Formal vs. Informal: A Comparison Table
• Career Growth Conversations: Discussing Your Direction
  • Expressions for Sharing Career Goals With Your Manager
  • How to Open the Promotion Conversation
  • The Career Growth Questions You Should Be Asking Your Manager
• Giving and Receiving Constructive Feedback
  • The Skill of Giving Feedback: The SBI Model
  • Expressions for Receiving Feedback
  • Common Feedback Mistakes, and How to Recover
• Raising Hard Topics: Difficult Conversations
  • Talking About Burnout and Overload
  • Reporting a Conflict Inside the Team
  • Requesting a Project Change or Role Switch
• Preparing for the Performance Review
  • English for Writing Your Self-Assessment
  • Conversation Strategy in the Review Meeting
• 1:1 Meeting Email Templates
  • The Pre-Meeting Agenda Email
  • The Post-Meeting Follow-up Email
• Practice Scenarios for Real 1:1 Meetings
  • Scenario 1: Your First 1:1 With a Manager
  • Scenario 2: Being Honest About a Project Delay
  • Scenario 3: Discussing Salary and Compensation
• Handling Awkward Moments, and the Lines That Recover Them
• Practical Tips for Running Your 1:1 in English
  • Building a Meeting-Note Habit
  • Speaking With Confidence as a Non-Native Speaker
  • Adapting the 1:1 to Your Manager's Type
• A Collection of Common 1:1 Meeting Phrases
• Wrapping Up: Turn the 1:1 Into the Engine of Your Career
• References

Introduction

For developers working at a global IT company, or in any English-speaking environment, the 1:1 meeting (One-on-One Meeting) is the central channel for career growth. Held with your manager weekly or every other week, it is not a simple status report — it is a strategic conversation where you discuss the direction of your career, exchange feedback, and ask for the support you need.

According to Harvard Business Review, employees who have regular 1:1 meetings have a 67% lower attrition rate than those who do not. That is how valuable this time is, for the organization and for you personally. Leading that conversation naturally in English, however, is a challenge of another order.

This article follows the whole arc of a 1:1 meeting and pulls together the English expressions you can use at each stage, real conversation templates, and the mistakes people commonly make along with the recovery strategies for them. Asking your manager for a promotion, delivering constructive feedback, raising a difficult topic — everything here is built to be used at work immediately.

The Structure of a 1:1 Meeting and Its Core English Expressions

The Five-Stage Structure of an Effective 1:1

A 1:1 usually runs somewhere between 30 and 60 minutes. For an effective meeting, the five-stage structure below is the one to reach for.

Opening the Meeting: Personal Check-in Expressions

The first five minutes of a 1:1 are for asking how the other person is doing. The expressions here differ from the formal greetings of a team meeting: the tone is more personal and more candid.

[Opening the Meeting — Check-in Expressions]

Formal:
  Manager: "How are things going for you this week?"
  You:     "Things are going well, thank you. I've been focused on
            the migration project and making solid progress."

Semi-formal:
  Manager: "How's your workload feeling these days?"
  You:     "It's been manageable. I've found a good rhythm with the
            sprint tasks, though the on-call rotation last week was
            a bit intense."

Casual (with a manager you know well):
  Manager: "How's everything? Anything exciting going on?"
  You:     "Pretty good! I actually tried a new debugging approach
            that saved us a few hours. I'd love to tell you about it."

Formal vs. Informal: A Comparison Table

The right tone depends on your relationship with your manager and on the company culture. The same meaning can leave a very different impression depending on how you phrase it.

Career Growth Conversations: Discussing Your Direction

Expressions for Sharing Career Goals With Your Manager

The career growth conversation is the most important part of a 1:1 and the part most people struggle with. The key is to present a concrete goal together with a plan for reaching it.

[Career Goal Discussion — sharing short- and long-term goals]

Short-term goal (6 months):
  "Over the next six months, I'd like to focus on improving my
   system design skills. Specifically, I want to lead the
   architecture review for at least one major project."

Long-term goal (1-2 years):
  "Looking at the bigger picture, I see myself growing into a
   tech lead role. I'm particularly interested in building
   expertise in distributed systems and mentoring junior engineers."

A concrete request:
  "To help me get there, I was wondering if there are any
   cross-team projects I could contribute to. I think working
   with the platform team would give me valuable exposure to
   infrastructure challenges."

How to Open the Promotion Conversation

Asking for a promotion is not walking in and saying “please promote me.” It calls for a strategic approach: showing, with data, that you are already doing the work of the next level.

[Promotion Discussion — a strategic approach]

Step 1: Open the conversation (Opening)
  "I'd like to have a conversation about my career progression.
   I've been reflecting on my contributions over the past year
   and wanted to discuss where I stand in terms of growth."

Step 2: Present the evidence (Evidence)
  "Over the last two quarters, I've taken on responsibilities
   that align with the senior engineer expectations:
   - I led the database migration project that improved query
     performance by 40%.
   - I've been mentoring two junior engineers on the team.
   - I initiated and drove the adoption of our new CI/CD pipeline."

Step 3: Ask the clear question (Direct Ask)
  "Given these contributions, I'd like to understand what the
   path to promotion looks like for me. Are there specific gaps
   I should focus on, or do you feel I'm on track?"

Step 4: Follow up (Follow-up)
  "Would it be helpful if I put together a brief document
   summarizing my key accomplishments? I want to make it easy
   for you to advocate for me when the time comes."

The Career Growth Questions You Should Be Asking Your Manager

These are the 1:1 questions Harvard Business Review recommends, reframed for the context of a Korean engineer.

Exploring your growth direction:

• "What skills do you think I should develop to prepare for the next level?"
• "Are there any areas where you think I have untapped potential?"
• "What does success look like for someone at the next level in our organization?"

Asking for feedback:

• "What's one thing I could do differently to have a bigger impact?"
• "How do you think I handled the recent incident? What would you suggest I do differently next time?"
• "Is there anything I'm doing that I should stop or change?"

Expanding your role on the team:

• "Are there any upcoming projects where I could take on more ownership?"
• "I'd like to improve my cross-functional collaboration. Do you have suggestions on how I can build stronger relationships with other teams?"
• "Would it make sense for me to participate in the architecture review meetings?"

Giving and Receiving Constructive Feedback

The Skill of Giving Feedback: The SBI Model

The most effective framework for constructive feedback is the SBI (Situation-Behavior-Impact) model. You describe the situation, state the behavior you observed, and explain the impact that behavior had.

[SBI Feedback Model — a template for delivering feedback]

Structure: Situation → Behavior → Impact

Example 1 (positive feedback):
  Situation: "During yesterday's sprint planning..."
  Behavior:  "...you took the initiative to break down the
              large user story into smaller, actionable tasks..."
  Impact:    "...which helped the team estimate more accurately
              and gave everyone a clearer picture of the work ahead."

  Full: "During yesterday's sprint planning, you took the initiative
         to break down the large user story into smaller, actionable
         tasks. That really helped the team estimate more accurately
         and gave everyone a clearer picture of the work ahead.
         Great job."

Example 2 (developmental feedback):
  Situation: "In the last code review..."
  Behavior:  "...I noticed that the PR was submitted without tests
              for the edge cases we discussed..."
  Impact:    "...which meant the reviewer had to go back and forth
              several times, delaying the merge by two days."

  Full: "In the last code review, I noticed that the PR was submitted
         without tests for the edge cases we discussed. This meant
         the reviewer had to go back and forth several times, delaying
         the merge by two days. Going forward, could we make sure to
         include those test cases before submitting?"

Expressions for Receiving Feedback

Taking feedback is as much a skill as giving it. These expressions show a mature, receptive stance — neither reacting defensively nor passively agreeing with everything.

Acknowledging:

• "Thank you for that feedback. I appreciate you bringing it up."
• "That's a fair point. I hadn't considered it from that angle."
• "I really value your honesty. That's something I want to work on."

Clarifying:

• "Could you give me a specific example so I can better understand?"
• "When you say 'more proactive,' what would that look like in practice?"
• "I want to make sure I understand correctly. Are you saying that...?"

Committing to Action:

• "That makes sense. I'll start by doing X, and I'd love to check in on my progress at our next 1:1."
• "I'll work on that. Would it be helpful if I shared a plan for how I intend to address this?"
• "I hear you. Let me think about the best way to approach this and get back to you."

Common Feedback Mistakes, and How to Recover

Raising Hard Topics: Difficult Conversations

Talking About Burnout and Overload

Burnout is a real risk for developers. How you bring it to your manager, though, changes the outcome dramatically. Complaining that “there is too much work” and sharing the specific situation while looking for a fix together leave completely different impressions.

[Discussing Workload and Burnout]

Weak version (not recommended):
  "I'm really stressed out and can't handle all this work."
  → No specifics; reads as venting rather than problem-solving

Strong version (recommended):
  "I want to flag something about my workload. I'm currently
   juggling the API migration, on-call duties, and the new
   feature development. I've been putting in extra hours, but
   I'm concerned about the quality of my work if this pace
   continues. Could we prioritize together and perhaps
   redistribute some tasks?"

Core structure:
  1. Signal ("I want to flag something..." / "I'd like to bring
     up something that's been on my mind...")
  2. Facts (list the specific work)
  3. Impact (what breaks if the pace continues)
  4. Solution (propose a direction you can fix together)

Reporting a Conflict Inside the Team

When you bring a conflict with a colleague to your manager, keep the focus on behavior and impact rather than on attacking the person.

Opening lines:

• "There's a situation I'd like to get your advice on."
• "I'm looking for guidance on how to handle something with a colleague."
• "I want to be transparent about a challenge I'm experiencing on the team."

Describing the situation:

• "I've noticed that when we discuss technical decisions, we sometimes end up going in circles without reaching alignment. I think it's affecting our velocity."
• "I've tried to address this directly with them, but we haven't been able to find common ground. I'd appreciate your perspective on how to move forward."

What to watch for -- the do's and the don'ts:

• DO: describe observable behavior ("I've observed that...")
• DO NOT: judge the person's character or intent ("They're being difficult" / "They don't care about quality")
• DO: share what you have already tried ("I've tried X and Y...")
• DO NOT: use a tone that expects your manager to solve it for you ("You need to talk to them")

Requesting a Project Change or Role Switch

When you ask to move to another project or change roles, opening from the angle of a growth opportunity rather than dissatisfaction with your current role works far better.

[Requesting a Role Change or Project Transfer]

Approach 1: growth framing
  "I've really enjoyed working on the payments team and feel
   I've made meaningful contributions. At the same time, I'm
   keen to broaden my experience. I've noticed the platform
   team is working on some interesting distributed systems
   challenges, and I think contributing there would help me
   grow as an engineer. Would it be possible to explore that?"

Approach 2: tie it to a company need
  "I saw that the data engineering team is looking for help
   with the new pipeline project. Given my experience with
   streaming systems in my previous role, I think I could
   add value there while also developing new skills.
   What are your thoughts on that?"

Phrases to avoid:
  ✗ "I'm bored with my current work."
  ✗ "This project is going nowhere."
  ✗ "I don't want to work with this team anymore."

Preparing for the Performance Review

English for Writing Your Self-Assessment

When review season arrives, you have to write a self-assessment. The key here is a balanced approach: describe your results concretely, with numbers, and admit your growth areas honestly.

Achievement statement patterns:

[Self-Assessment Writing Patterns]

Pattern 1: "I demonstrated [skill] when I [specific action]."
  Ex: "I demonstrated technical leadership when I designed and
       implemented the new caching layer that reduced API latency
       by 35%."

Pattern 2: "I contributed to [goal] by [specific action], resulting
            in [measurable outcome]."
  Ex: "I contributed to our team's reliability goals by setting
       up automated alerting for critical services, resulting in
       a 50% reduction in incident response time."

Pattern 3: "I took ownership of [area] and [outcome]."
  Ex: "I took ownership of our onboarding documentation and
       revamped it completely, which reduced new hire ramp-up
       time from 4 weeks to 2 weeks."

Describing a growth area:
  "I recognize that I could improve how I communicate technical
   trade-offs to non-technical stakeholders. I plan to practice
   this by presenting at cross-functional meetings and seeking
   feedback from product managers."

Conversation Strategy in the Review Meeting

A review meeting is unlike a regular 1:1: it usually runs 30 to 60 minutes and covers everything you did over the past half-year or year. Without preparation you will leave out important results, or fail to respond effectively to your manager's assessment.

Pre-meeting checklist:

• A list of the main results and projects from the period
• Numbers and data for each result
• A record of the positive feedback you received (Slack messages, emails, and so on)
• Your own honest read on the areas that need work, and a plan for them
• Goals and career direction for the next period

Useful expressions during the meeting:

When you want to highlight a result:

• "One of the highlights for me this quarter was leading the migration project. I'm proud of how the team delivered it ahead of schedule."
• "I'd like to call attention to the mentoring work I did, which isn't always visible but had a real impact on the team."

When the assessment is not what you expected:

• "I appreciate the feedback. I'd like to understand more about your perspective on that area. Could you walk me through what you observed?"
• "I see where you're coming from. I'd also like to share some context that might be relevant."

When you want to confirm the next steps:

• "Based on our discussion, what would you say are the top two or three areas I should focus on going forward?"
• "How would you describe the gap between where I am now and where I need to be for the next level?"

1:1 Meeting Email Templates

The Pre-Meeting Agenda Email

Sharing the agenda before the meeting lets your manager prepare as well, and puts the meeting time to far better use.

Subject: 1:1 Agenda — March 8

Hi [Manager name],

Here are the topics I'd like to cover in our 1:1 this week:

1. Update on the API migration — on track for the March 15
   deadline
2. A question about the upcoming re-org and how it might
   affect our team
3. Career development — I'd love to discuss opportunities
   to get more exposure to system design

If there's anything you'd like to add, please let me know.
Looking forward to our conversation.

Best,
[Your name]

The Post-Meeting Follow-up Email

Sending a summary of what you discussed and the action items raises your manager's trust in you and puts what you committed to clearly on the record.

Subject: Follow-up from our 1:1 — March 8

Hi [Manager name],

Thanks for the great conversation today. Here's a quick
summary of what we discussed and our action items:

Discussion highlights:
- API migration is on track. You'll loop in the DevOps
  team for the deployment review.
- We agreed that I'll take the lead on the new monitoring
  dashboard project starting next sprint.
- Regarding career growth, you suggested I present at the
  next architecture review meeting as a stretch opportunity.

Action items:
- [Me] Draft a proposal for the monitoring dashboard by
  Friday
- [Me] Sign up for the architecture review slot in April
- [Manager] Connect me with Sarah from the platform team
  for a knowledge-sharing session

Please let me know if I missed anything or if you'd like
to adjust any of these items.

Best,
[Your name]

Practice Scenarios for Real 1:1 Meetings

Scenario 1: Your First 1:1 With a Manager

The first 1:1 after you join a new team, or after a new manager arrives, is the meeting that lays the foundation of the relationship.

[First 1:1 with a New Manager]

Manager: "I'd love to get to know you better. Tell me about
          your background and what brought you here."

You:     "Sure! I've been with the company for about two years,
          mostly working on the backend services team. Before
          this, I was at a startup where I wore many hats — from
          backend development to DevOps. What drew me here was
          the scale of the problems and the engineering culture."

Manager: "That's great. What's your preferred working style?
          How can I best support you?"

You:     "I appreciate having clear expectations and regular
          feedback. I do my best work when I have autonomy on
          the 'how' but clarity on the 'what' and 'why.' I also
          value having space to propose ideas and experiment."

Manager: "And what are your career goals right now?"

You:     "In the near term, I want to deepen my expertise in
          distributed systems. Longer term, I'm exploring
          whether I want to go down the individual contributor
          path toward a staff engineer role or move into
          engineering management. I'd love your perspective on
          both paths as we work together."

Scenario 2: Being Honest About a Project Delay

When a project is running later than expected, sharing the problem early instead of hiding it is the core of building trust.

[Communicating Project Delays Honestly]

You:     "I want to give you a candid update on the search
          feature. We've hit some unexpected complexity around
          the indexing logic. Based on what I know now, I think
          we'll need an additional week beyond the original
          timeline."

Manager: "Thanks for flagging that. What's causing the delay?"

You:     "The main issue is that the existing data model doesn't
          support the faceted search requirements we scoped out.
          We have two options: either refactor the data model
          now, which adds about a week but sets us up well for
          future features, or implement a workaround that ships
          faster but creates tech debt."

Manager: "What would you recommend?"

You:     "I'd recommend the refactor. The workaround would save
          us a week now but could cost us significantly more time
          down the road. I've already sketched out the revised
          approach and can share the design doc if you'd like to
          review it."

Scenario 3: Discussing Salary and Compensation

The pay conversation is one of the most sensitive topics in a 1:1. The key is to approach it logically, grounded in market data and your own contributions.

[Discussing Compensation]

You:     "I'd like to discuss my compensation. I've been
          reflecting on my contributions over the past year
          and also looked at market benchmarks for my role
          and experience level."

Manager: "Sure, I'm happy to have that conversation."

You:     "Over the past year, I've expanded my scope
          significantly — from owning one service to leading
          the architecture for our entire payments domain.
          I've also taken on mentoring responsibilities and
          led two critical incidents to resolution. Based on
          market data from Levels.fyi and Glassdoor, I believe
          my current compensation is below the median for
          someone in my role with my experience."

Manager: "I hear you. Let me look into this and get back to
          you with what I can do."

You:     "I appreciate that. Would it be helpful if I put
          together a summary of my key accomplishments and
          the market data I referenced? That way, you'll
          have everything you need when discussing this with
          leadership."

Handling Awkward Moments, and the Lines That Recover Them

Awkward moments do come up in 1:1s. Handling them naturally instead of freezing is an important part of being a professional.

Practical Tips for Running Your 1:1 in English

Building a Meeting-Note Habit

Writing notes before and after the meeting is what makes a 1:1 effective. In a meeting held in English especially, recording the key expressions and the feedback gives you something to draw on next time.

An example note structure:

[1:1 Meeting Notes Template]

Date: March 8, 2026
Attendees: [Your name] & [Manager name]

--- Topics Discussed ---
1. [Topic]: [Key points and decisions]
2. [Topic]: [Key points and decisions]
3. [Topic]: [Key points and decisions]

--- Feedback Received ---
- [Specific feedback point]
- [Action I'll take in response]

--- Career Development ---
- [Growth area discussed]
- [Next steps agreed upon]

--- Action Items ---
- [ ] [Owner] [Task] [Due date]
- [ ] [Owner] [Task] [Due date]

--- Notes for Next 1:1 ---
- [Topics to follow up on]
- [Questions to prepare]

Speaking With Confidence as a Non-Native Speaker

Running a 1:1 when English is not your first language is an added challenge. A handful of strategies, though, will raise your confidence considerably.

Before the meeting:

• Write your three key points out in English ahead of time
• The harder the topic, the more worth scripting in advance and rehearsing out loud
• Choose two or three key expressions you will use, and drill them

During the meeting:

• Put clarity ahead of speed. Speaking slowly is perfectly fine
• Always check anything you did not follow: "Could you repeat that?" or "Let me paraphrase to make sure I understood correctly."
• Use screen sharing or a document for anything complicated: "I prepared a few notes. Mind if I share my screen?"

After the meeting:

• Reconfirm what was discussed with a follow-up email
• Note down any new expression you used or picked up in the meeting
• Rehearse the expressions you want to use next time

Adapting the 1:1 to Your Manager's Type

Not every manager works the same way. Tuning your 1:1 approach to your manager's disposition pays off.

A Collection of Common 1:1 Meeting Phrases

Finally, here are the phrases that come up most often in 1:1 meetings, sorted by situation. Commit them to memory and you will have a natural response ready whatever comes up.

Managing the flow of the conversation:

• "Before we move on, I want to circle back to something you mentioned earlier."
• "I know we're running short on time, so let me quickly touch on one more thing."
• "Can we table this for now and come back to it next week?"
• "I want to make sure we're on the same page about..."

Agreement and empathy:

• "That resonates with me."
• "I'm fully aligned with that approach."
• "That's exactly what I was thinking."
• "I couldn't agree more."

Soft disagreement:

• "I see where you're coming from, but I have a slightly different perspective."
• "That's an interesting point. Have we considered the possibility that...?"
• "I hear you, and I want to push back gently on one aspect."
• "I think there's another angle we might want to explore."

Confirming the next steps:

• "So, just to confirm, the next step is for me to..."
• "Let me summarize what we agreed on to make sure I've captured everything."
• "What's the timeline you have in mind for this?"
• "Should I loop anyone else in on this?"

Wrapping Up: Turn the 1:1 Into the Engine of Your Career

A 1:1 meeting is not simply time to report your work to your manager. Used well, it becomes the single most powerful tool for accelerating your career. To summarize the key points:

First, prepare the agenda yourself. Do not wait for your manager to set it. Organizing the topics you want to discuss and sharing them in advance is the professional posture.

Second, do not be afraid of feedback. Constructive feedback is fuel for growth. Use the SBI model to give feedback concretely, and when you receive it, thank the person and build an action plan.

Third, do not avoid the hard conversations. Burnout, a role change, pay — even sensitive topics deepen your manager's trust in you when you frame and phrase them well.

Fourth, write it down and follow up. Recording what you discussed, doing what you promised, and confirming it by follow-up email is the habit that builds trust.

Fifth, practice the English steadily. Make the expressions in this article your own, one at a time. The point is not perfect English but clear, honest communication.

May your next 1:1 be the turning point of your career.

References

• 28 Questions to Ask Your Boss in Your One-on-Ones — Harvard Business Review
• How to Run Effective One-on-One Meetings — Teamflect
• Effective One-on-One Meetings: Free Template and Agenda — Asana
• How to Give Feedback in English: Tips and Phrases — Speak Confident English
• 60 Useful Performance Review Phrases — Culture Amp
• 200 One-on-One Meeting Questions Great Managers Ask — Fellow.ai
• Giving Constructive Criticism: Phrases and Tips — Target Training
• 53 Self-Assessment Phrases for Professional Development — Indeed