1:1 미팅 영어 완벽 가이드: Career Growth 대화부터 피드백 기술까지

[미팅 시작 — 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 (친한 매니저와):
  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."

[Career Goal Discussion — 단기/장기 목표 공유]

단기 목표 (6개월):
  "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."

장기 목표 (1-2년):
  "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."

구체적 요청:
  "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."

[Promotion Discussion — 전략적 접근]

Step 1: 대화 시작 (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: 성과 제시 (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: 명확한 질문 (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)
  "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."

[SBI Feedback Model — 피드백 전달 템플릿]

구조: Situation → Behavior → Impact

예시 1 (긍정적 피드백):
  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."

  전체: "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."

예시 2 (개선 피드백):
  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."

  전체: "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?"

[Discussing Workload and Burnout]

약한 표현 (비추천):
  "I'm really stressed out and can't handle all this work."
  → 구체성이 없고, 문제 해결보다 불만 토로로 들릴 수 있음

강한 표현 (추천):
  "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?"

핵심 구조:
  1. Signal ("I want to flag something..." / "I'd like to bring
     up something that's been on my mind...")
  2. Facts (구체적 업무 나열)
  3. Impact (지속 시 어떤 문제가 생기는지)
  4. Solution (함께 해결할 방향 제안)

[Requesting a Role Change or Project Transfer]

접근 1: 성장 프레이밍
  "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?"

접근 2: 회사 니즈와 연결
  "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?"

피해야 할 표현:
  ✗ "I'm bored with my current work."
  ✗ "This project is going nowhere."
  ✗ "I don't want to work with this team anymore."

[Self-Assessment Writing Patterns]

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

패턴 2: "I contributed to [goal] by [specific action], resulting
         in [measurable outcome]."
  예: "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."

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

개선 영역 기술:
  "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."

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]

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]

[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."

[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."

[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."

[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]