Real Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 47 interview experiences · FREE TO READ
Which role are you interviewing for?
9 roles · 47 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Real.
Real
Software Engineer
Senior Easy Positive experience Accept offer 3 rounds
Interview process
Technical screen Technical screen Technical screen
Interview formats
Coding System Design Technical
The interview process had a good structure with clear instructions on what to expect next. There were 3 technical rounds in total: one for DSA, one for System Design, and a final round with the VP. Each round was 45 minutes, except for the VP round which was an hour. For the DSA round, practicing Leetcode Medium problems is recommended. I want to thank the HR and the team for keeping me updated promptly and providing clear guidance.
Confirmed questions3 questions
- A dynamic programming question in the style of Leetcode, with a slightly complex follow-up, was asked.
- For LLD, discussing the approach and selection of design patterns was sufficient; writing full code was not necessary.
- On HLD, expect theoretical questions covering threading, multiprocessing, and asynchronous programming.
Real
Senior Software Engineer
Senior Average Negative experience No offer 1 round
Interview process
Technical screen
Interview formats
Technical Coding
I interviewed for a Senior Software Developer role. The technical round involved a multithreading and a hashsets problem. I solved both correctly and explained my reasoning well. However, I got a generic rejection email saying they're moving on with other candidates. I asked for feedback but got no reply. For senior roles, people put in a lot of time preparing. A generic rejection without feedback isn't great for the hiring process. Being transparent and professional should be normal at this level.
Confirmed questions4 questions
- Can you discuss multithreading concepts?
- How would you approach problems involving hashsets?
- Explain asyncio.
Real
Senior Backend Engineer
Senior Easy Negative experience No offer 1 round
Interview process
Take home Technical screen
Interview formats
Coding Technical
So I interviewed with Real, and honestly, based on Glassdoor reviews, I really didn't want to waste my time, but I tried anyway, and guess what? It was the same old story. They asked me to build a website like IMDb.com, which I finished in about 40 minutes. When I asked if there was anything else, the interviewer just sounded like a robot and said to send the zip file if I was done. For your info, I used SOLID principles, a few design patterns, and abstraction, and my code was top-notch. Their review process is awful; they never tell you why you're rejected, just some generic 'we appreciate your interest.' Seriously, don't bother applying here.
Confirmed questions1 question
- Build a microservice or website that functions like IMDb.com
Real
Lead Frontend Engineer
Lead Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Take home
Interview formats
Coding System Design Other
I was contacted by a recruiter on LinkedIn, and then they gave me a take-home assignment. The recruiter was really rushing me. I tried to ask some important questions about how the app would be used and scaled, but I only got vague answers, which was super disappointing. You'd think they'd give you enough details if they expect you to spend 3 days building something, and then they reject you without any feedback. I know my stuff because I've built tons of customer-facing websites that get billions of visits. So, I decided not to add any complex stuff or premature optimization based on the limited info. I also included a system design section and added some tests to show I can do unit testing. I'm definitely reminding myself to never do a take-home project again; it's such a waste of time. Only do one if your onsite interview is already set up.
Confirmed questions2 questions
- Using the GitHub public API, show a list of users.
- On a different page, using the GitHub public API, display the user's organizations, repositories, and followers.
Real Interview Questions
Quoted word for word from Real interview reports.
“What is the Global Interpreter Lock (GIL) in Python and how does it affect performance?”
Read reports →“Write a program to match movies.”
Read reports →“Build a microservice or website that functions like IMDb.com”
Read reports →“Explain asyncio.”
Read reports →“Could you display details for GitHub users by using the GitHub API?”
Read report →“Explain the differences and use cases for multiprocessing in Python.”
Read report →“Build a REST application and then zip it up for uploading to a shared Google Drive.”
Read report →“Build a React project that utilizes the Github API.”
Read report →“Given CSV files containing movie data from various sources with differing record structures and columns, the task is to match movie records between these files, with the explicit instruction to "make the test pass" by successfully matching at least one record.”
Read report →Formats, difficulty and experience
Across all 47 Real interview reports.