Real Frontend Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 8 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Real.
Real
Senior Frontend Engineer
Senior Average Negative experience No offer 2 rounds
Interview process
Recruiter call Take home Offer
Interview formats
Coding
After a quick recruiter chat, I got a take-home coding challenge using the github users API. They gave 7 days, but the recruiter wanted it done in 3 days. It involved basic API fetching and displaying data, but also had vague requirements like making it 'production ready' with styling rated 'low to moderately' without any guidelines or mockups. I finished it in a day and got a rejection email days later with no explanation. No feedback, just a generic email. It felt like a waste of time, and the recruiter's comment about the team structure (a few US-based lead FE devs managing 20+ Indian devs) sounded chaotic. I'd recommend steering clear.
Confirmed questions1 question
- Can you display some data fetched from the GitHub users API?
Real
Frontend Engineer
Entry Average Negative experience No offer 1 round
Interview process
Take home
Interview formats
Coding
So, like some other folks, I got a take-home assignment. They gave me 7 days, but no real clue on how long I was supposed to spend on it. I kinda went all out, trying to make it super production-ready UI. Submitted it, and then... crickets. Haven't heard back at all. Honestly, don't bother with their interview process.
Confirmed questions1 question
- Complete a take-home task involving the development of a UI that interacts with the GitHub API.
Real
Frontend Engineer
Lead Average Negative experience No offer 2 rounds
Interview process
Recruiter call Take home
Interview formats
Coding Technical
I had a recruiter screen, then a take-home coding assessment which was forked from CodeScreen. The task was to use the Github API to retrieve a list of users and then build list and detail pages using vanilla React 18 with Typescript. They said it was pretty open-ended and to use frameworks and libraries I was comfortable with. I had 7 days to complete it, but they didn't communicate the expected time or effort. I submitted the assessment with what I thought was production-quality code, including routing with 404 & 500 error boundaries, mobile responsiveness with tailwindcss, and jest unit tests using @testing-library/react. After that, it was radio silence, and reaching out to the recruiter didn't yield any results.
Confirmed questions0 questions
No confirmed questions were included in this interview report.
Real Frontend Engineer Interview Questions
Quoted word for word from Real interview reports.
“Show some data from the GitHub users API.”
Read reports →“Could you display details for GitHub users by using the GitHub API?”
Read reports →“Build a React project that utilizes the Github API.”
Read reports →“Can you display some data fetched from the GitHub users API?”
Read reports →“Complete a take-home task involving the development of a UI that interacts with the GitHub API.”
Read report →“Complete a take-home project, which needs to have tests. You are permitted 7 days to finish.”
Read report →“For the first round, they provided a random API and asked me to implement search, sort, pagination, and then show the data in a table.”
Read report →“For the second round, which was system design, I was asked to build a feature like those seen on most documentation sites where pressing Ctrl+K opens a modal containing shortcuts. These shortcuts could lead to navigation, trigger actions, or perform a Google search.”
Read report →Formats, difficulty and experience
Across all 8 Real interview reports.