Real logo

Real Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 18 interview experiences · FREE TO READ

1.8 Rounds average
Average Typical difficulty
16.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Real.

Showing 3 of 18
Real logo
Real

Software Engineer

Engineering · half a year ago

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 logo
Real

Senior Software Engineer

Engineering · nearly a year ago

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 logo
Real

Software Engineer

Engineering · nearly a year ago

Entry Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Take home
Interview formats
Coding Technical

After filling out an application, I was given a calendar invite weeks in advance. Then I had a live coding assessment where a recruiter watched and recorded me. I then received a rejection email, which I appreciated since I expected to be ghosted. I was prepared for the interview until I joined the call and couldn't share my full screen. This put me at a disadvantage as I couldn't see or read the screen, leading to a terrible experience and first impression. My advice to candidates is to not use a computer with multiple screens, as the instructions say to share your full desktop. You could lie and say you shared them all, but this rule can impact you if you honestly follow it and have a large monitor. Be ready to code a lot, including the initial setup. The time given isn't enough unless you can recall everything instantly. My advice to interviewers is to consider neurodiverse people who follow instructions literally. Your coding exercise would have been easier if the environment was better. You should also consider offering take-home projects, as some people have disabilities.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

Real Software Engineer Interview Questions

Quoted word for word from Real interview reports.

Build a REST application and then zip it up for uploading to a shared Google Drive.

Read reports

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 reports

Can you explain python internals, GIL, asyncio, and multiprocessing?

Read reports

How would you approach matching movie records across different CSV files with disparate data structures and columns, given the primary objective is simply to pass the test by matching at least one record?

Read report

Describe your understanding of object-oriented programming (OOPs).

Read report

Formats, difficulty and experience

Across all 18 Real interview reports.

Interview formats

Coding 47.1%
Technical 32.4%
System Design 8.8%
Behavioral 8.8%
Other 2.9%

Interview difficulty

Easy 33.3%
Average 55.6%
Difficult 11.1%

Candidate experience

Positive 16.7%
Negative 77.8%
Neutral 5.6%