Google Behavioral Question 6: Mentoring Someone

🎯 Best Story: Junior iOS Developer Promotion

Full STAR Answer (2.5 minutes)

Situation (30s)

At LINE, my manager assigned me and a junior iOS developer to work on video autoplay management (similar to Facebook/X feed). I worked on Android, he on iOS. The junior was usually assigned simple tasks only, never handled a medium project end-to-end. His direct mentor (iOS senior) didn't believe in his abilities.

Instead of taking the lead myself, I proposed: "Let the junior be the main person in charge." His mentor and my manager were skeptical - they focused on results more than developing people. But I saw potential - he had ability but lacked confidence because no one let him try.

Task (20s)

• Convince manager and iOS senior to let junior lead
• Set up checkpoints to catch issues early
• Mentor him through the project
• Deliver the project successfully

Action (80s)

1. Guaranteed Success to Get Buy-In

• Told manager: "If project fails, I take responsibility"
• Created checkpoint system - if junior misses any point, I jump in immediately
• Extended deadline slightly so junior could learn gradually

2. Structured Mentorship Approach

Initial Planning (Week 1-2):

• Asked junior to prepare initial development plan and identify edge cases
• Asked questions, let him think carefully before answering
• Guided how to contact PM - be specific and transparent

Design Doc (Week 3):

• Asked junior to create design doc
• Guided which sections to add, how to draw clear diagrams
• Team reviewed his doc, provided feedback

Development (Week 4-8):

• iOS seniors mentored technical implementation (I don't know iOS deeply)
• I reviewed business logic and code structure
• Suggested how to write cleaner code

3. First Checkpoint - He Amazed Us!

Deadline was 2 weeks, but he delivered in under 1 week with:

• Deeply observed other apps for patterns
• Reasonable approaches to ambiguous situations
• Thoughtful edge case handling

Result (30s)

✅ Project delivered successfully - few bugs, especially on iOS side

✅ Junior promoted to mid-level after this project

✅ Manager and iOS senior changed their view - saw he just needed opportunity

✅ Team gained confidence in developing people, not just delivering features

✅ Personal satisfaction - helping someone grow is more rewarding than solo success

Learning: "People often have more capability than they're given credit for. The key is structured support, not just throwing them in or blocking them."

Key Follow-Up Q&A

Q: "What if the junior had actually failed at the first checkpoint?"

"I had a specific risk mitigation plan:

If he missed the 2-week checkpoint:

• I would have jumped in to help (as promised to my manager)
• We'd pair on the planning together
• I'd provide more structured guidance
• We'd add 1 more week to the timeline

If quality was insufficient:

• Review together what was missing
• Show examples of good approaches
• Give him another attempt with clearer guidance

If he was truly blocked:

• I'd take over as main owner
• He'd assist and learn by observing
• Still valuable learning experience

The key: The checkpoint system meant we'd catch issues early when they're fixable, not late when they're catastrophic.

Result: He actually exceeded expectations at first checkpoint, so we never needed the backup plan. But having it gave stakeholders confidence to let me try this approach.

The principle: Take calculated risks with strong safety nets. People surprise you when given real opportunity with proper support."

📚 Full Version: /mnt/project/5____Resolving_conflict_and_mentorship.md