expedia group logo
Expedia Group· frontend role

Interview experience in Expedia for frontend role

Posted
24 Jan 2026
388 reads

Summary

I had an interesting frontend interview at Expedia where the main focus was on reviewing an existing React component for improvements and identifying issues.

How it went

Had an interesting frontend interview recently where the main focus wasn’t writing new code, but reviewing existing code. The interviewer shared a React component and asked me to walk through it like a real PR review. I had to identify performance issues, improper state management, missing keys, accessibility gaps, and suggest cleaner abstractions. They cared a lot about why something was wrong and how I’d improve readability, scalability, and maintainability. No trick questions—just real-world frontend thinking. Honestly, this felt more practical than typical DSA-heavy rounds. Good reminder that frontend interviews are evolving beyond just LeetCode.

Questions asked (1)

  1. 01

    React Component Code Review

    Other

    The interviewer shared a React component and asked me to walk through it like a real PR review. I had to identify performance issues, improper state management, missing keys, accessibility gaps, and suggest cleaner abstractions. They cared a lot about why something was wrong and how I’d improve readability, scalability, and maintainability.

How they prepared

I found something similar in PrepareFrontend for practicing the same.

Know someone preparing? Send it to them:WhatsAppLinkedInX

Interviewed at Expedia Group recently?

Write up your rounds while you still remember the questions. It helps the next person more than you would think.

Share your experience
Discussion 0

Questions for the author, or how your own interview compared.

Join the discussion

Sign in with Google to comment or ask the author a question.

No comments yet

Be the first to share your thoughts and start the discussion!