Why Duolingo?
I’ve been using Duolingo to learn English. Before this interview, I was also learning Spanish on the same platform. The product I’m interviewing to build infrastructure for is literally the product that’s helping me grow.
A Challenge Worth Taking
When I decided to interview with Duolingo for a Senior Platform Engineer role, I wasn’t just looking for a job. I was looking for a challenge that would push me beyond my comfort zone.
For the first time, I would be:
- Interviewing entirely in English with native speakers
- Meeting a pure US engineering team
- Operating at the Staff Engineer level
- Traveling internationally for better network stability (Bangkok, actually!)
These weren’t small things for someone whose primary experience has been in China, building infrastructure at scale for companies like Beike (1000+ microservices) and GLOCASHIER ($1B+ payment systems).
But challenges are how we grow.
The Interview Structure: Respect Through Process
The process itself was well-designed:
- Recruiter screen: Clear expectations, transparent about the pipeline
- Technical validation round: Focused on real problem-solving
- Virtual on-site: Four consecutive rounds over 3 days
- Code Review
- System Design
- Infrastructure Design
- Communication & Collaboration
What struck me most was the transparency. The recruiter was upfront when I finished first Ops round: “There’s another candidate ahead of you in the pipeline.” Not hidden. Not a gotcha. Just honest.
This honesty set the tone for everything that followed.
Round 1: Code Review - What Clear Thinking Reveals
The first round tested code quality, performance optimization, and communication.
I walked through the code carefully, thinking aloud about:
- N+1 query patterns and their impact at scale
- Thread-safety concerns and idempotency
- Trade-offs between performance and maintainability
- How to deliver critical feedback respectfully
The key insight: It’s not about being right. It’s about thinking clearly and explaining well.
I made sure to:
- Ask clarifying questions before diving deep
- Explain the WHY behind each concern, not just the WHAT
- Connect technical issues to business impact
- Show respect for the original implementation while identifying improvements
Outcome: Two positive confirmations that my approach was solid.
Round 2: System Design - Learning Through Iteration
This round tested my approach to large-scale architecture.
I designed a system for managing notifications at a 100M user scale, with an interesting constraint: 80% of users are inactive, generating zero events.
My initial approach was too simple. When questioned, I realized that event-driven architecture alone wouldn’t catch silent users. So I pivoted to a hybrid solution:
Real-time path (for 20% active users):
- Event-driven, immediate detection
- Smooth load distribution
Batch path (for 80% inactive users):
- Scheduled scanning is necessary
- Sharded to prevent database overload
- Redis for efficient deduplication
Key learning: Good design isn’t about choosing one perfect pattern. It’s about understanding constraints, making trade-offs explicit, and building solutions that match your actual problem, not just following industry best practices.
Round 3: Infrastructure Design - Where Stories Matter
This round asked me to describe infrastructure I’ve designed or managed.
I shared two stories:
Story 1: Beike Kubernetes Migration
Challenge: Migrate 1000 microservices from VMs to Kubernetes without downtime. Not technically trivial, but the real problem was organizational.
The human side: I had no formal authority over 1000 engineers. How do you get buy-in?
Approach:
- Listen to concerns (people’s fears are usually valid)
- Prove it works (5-service pilot showing 8x faster deployments)
- Build enabling infrastructure (KeBoot framework for self-service)
- Celebrate wins (peer influence stronger than mandates)
Results: 40% cost reduction ($800M/month), 24x faster deployments, 99.99% uptime, voluntary adoption across 1000 services.
Leadership lesson: Influence comes from listening, enabling, and celebrating. Not commanding.
Story 2: GLOCASHIER - Pragmatic Architecture for a Startup
Challenge: Build a payment system from zero handling $1B+ annual volume with a 10-person team.
Key decisions:
- ALB instead of API Gateway (simpler, sufficient)
- EC2 instead of EKS (team expertise matters)
- RDS instead of DynamoDB (ACID transactions required)
Philosophy: Build for today, architect for tomorrow. Don’t pay complexity costs for scale you don’t have yet.
Result: 99.99% uptime with a tiny team. Room to scale as the business grows.
Leadership lesson: The right choice depends on your constraints. There’s no single “best architecture”—only the right architecture for YOUR situation.
Round 4: Communication & Collaboration - Authenticity as Strength
This final round focused on how I think, communicate, and lead.
Questions explored:
- How do I influence teams without formal authority?
- How do I handle conflict and disagreement?
- How do I grow others?
- How do I respond to feedback?
I shared the same Beike stories, but deeper—focusing on the human dynamics:
- How I learned to listen before advocating
- How I discovered that respecting different perspectives leads to better solutions
- How celebrating others’ wins builds stronger teams
- How I’ve grown by receiving (and acting on) critical feedback
Key insight: Communication isn’t about being articulate. It’s about being honest, listening genuinely, and showing respect.
The Unexpected Cultural Bridges
Throughout this experience, something profound emerged: transparency and respect transcend cultural and language barriers.
Coming from China, I expected a more adversarial interview style. Instead, I experienced:
Transparency:
- Clear process expectations
- Honest about pipeline position
- Direct feedback (when given)
- Explicit about what they’re evaluating
Respect:
- Engineers engaged with genuine curiosity
- Space to think and pause
- Questions that showed they cared about my perspective
- Treatment as a peer, not a test subject
On language: I came in worried about my English. But here’s what I learned: when people respect you, language becomes secondary to thinking.
The engineers didn’t care about perfect pronunciation. They cared about:
- Are you thinking clearly?
- Can you explain your reasoning?
- Are you listening and adapting?
My slightly-accented English wasn’t a barrier. It was just… me.
The Outcome: What “No” Taught Me
After four rounds, the decision came back: “We’ve decided to move forward with other candidates at this time.”
The recruiter was transparent: There was another candidate ahead in the pipeline.
Did that sting? Yes. 💔
But here’s what happened next: I realized I’d already won.
Not the job, obviously. But something more valuable:
I proved to myself that I belong at this level.
Four engineers spent real time with me. They engaged authentically. Two explicitly said they enjoyed our conversations.
The rejection wasn’t about being “not good enough.” It was about timing—someone else was further along.
What This Experience Revealed
1. You’re Stronger Than You Think
I came in with imposter syndrome about my English. I left knowing that authentic communication matters more than perfect language.
2. Real Experience is Underrated
I didn’t memorize algorithms or follow templates. I talked about leading migrations, building startups, and handling real constraints. That resonated in ways generic system design approaches don’t.
3. Vulnerability is Strength
My best moments came when I:
- Admitted uncertainty and thought through problems aloud
- Asked clarifying questions instead of assuming
- Shared my learning journey honestly
4. Culture is Built Through Small Moments
The recruiter was honest about the pipeline position. The way engineers asked genuine questions. The way the rejection was delivered was with respect and an open door.
These small moments revealed a company’s culture more than any mission statement could.
5. Failure Isn’t Final
The message was clear: “We’d like to stay in touch for future opportunities.”
That door isn’t closed. And even if it were, this experience opened doors I didn’t know existed.
What’s Next
I didn’t get this particular job. But the experience shifted something fundamental in how I see myself as an engineer and leader.
I’m actively interviewing with other companies. I’m also staying in touch with the team that gave me this opportunity—in 6-12 months, maybe circumstances will align differently. But whether they do or not, I’m grateful for what this process taught me.
The lessons I’m carrying forward:
✅ Lead with listening, not commanding ✅ Make trade-offs explicit, not hidden ✅ Build for today, architect for tomorrow ✅ Celebrate others’ success as your own ✅ Treat people with genuine respect ✅ Communicate authentically, not perfectly
I came into this interview worried about my English, my background, and my fit. I’m leaving knowing that authenticity and clear thinking matter more than perfection.
That’s a lesson worth traveling across the world for.
Reflecting on It All
Mission alignment is real. I came into this interview using Duolingo daily to improve my English and Spanish. When you interview with a company whose mission matters to your own life, everything feels different.
The most surprising thing about this whole experience wasn’t what I learned about Duolingo or interviewing. It was what I learned about myself.
I learned that:
Clear thinking beats perfect English. I don’t need to sound like a native speaker. I need to think clearly and explain my reasoning well.
Real experience is valuable. Nobody cares if I’ve memorized algorithms. They care about the 1000 services I migrated. The payment system I built. The teams I’ve led.
Vulnerability is strength. My best moments came when I admitted uncertainty, asked clarifying questions, and thought through problems aloud.
Culture matters. The way I was treated—with transparency, respect, and genuine curiosity—shaped my entire experience. That’s how good companies work.
A Note
I’m sharing this because it matters. Not just for me, but for anyone navigating interviews across cultures and languages. The first time validate my English, get in touch with multi culture team for the first time. And most importantly, Duolingo is a great App that I’m using to learn English previously and learning Spanish currently.