RealSelf Software Engineer Interview Guide

The 60-second brief

As a Software Engineer at RealSelf, you will play a critical role in building and scaling the world's largest marketplace for medical aesthetics. Millions of consumers rely on the platform to research treatments, share reviews, and connect with certified doctors. Your engineering efforts will directly impact how seamlessly these users navigate complex medical information and make life-altering decisions. The engineering team at RealSelf focuses on high-impact, user-centric features, ranging from advanced search and recommendation engines to robust doctor-patient communication portals. You will work on optimizing database performance, developing clean APIs, and modernizing legacy systems to support a rapidly growing user base. This role requires a balance of strong technical execution and a deep empathy for the end user.

This guide is scoped to a Software Engineer candidate at RealSelf.

Focus areas

• Python
• SQL
• Coding Challenges (Take-home / Online submissions)

The RealSelf interview process

RealSelf candidates report 4 rounds over 3-5 weeks. The stages below are what candidates describe, not a published process.

HR Screen

Initial discussion about your background, career goals, and interest in RealSelf.

What to demonstrate

• Initial discussion about your background, career goals, and interest in RealSelf
• Depth in Python

How to prepare

• Be able to walk your CV end to end in two minutes, and say why this company specifically.
• Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.

Take-Home Assessment

Complete a technical assessment or solo coding challenge involving coding and database queries.

What to demonstrate

• Complete a technical assessment or solo coding challenge involving coding and database queries
• Depth in Python

How to prepare

• Answer aloud and timed: Design an algorithm to search and filter through user-generated reviews based on dynamic keywords and ratings.
• Answer aloud and timed: Create a utility to format and manipulate structured text inputs for rendering on a front-end interface.

Live Video Interviews

Walk through your solution and tackle real-time coding problems with senior engineers.

What to demonstrate

• Walk through your solution and tackle real-time coding problems with senior engineers
• Depth in Python

How to prepare

• Answer aloud and timed: Write a SQL query to retrieve and aggregate user engagement metrics from a multi-table database schema.
• Answer aloud and timed: Explain how you would design a backend service to handle high-traffic media uploads, such as patient before-and-after photos.

Interview Loop

Meet with engineering leaders, product managers, and potential teammates in an intensive interview loop.

What to demonstrate

• Meet with engineering leaders, product managers, and potential teammates in an intensive interview loop
• Depth in Python

How to prepare

• Answer aloud and timed: How would you structure a database schema to support a dynamic doctor search feature with multiple filtering criteria?
• Answer aloud and timed: Describe your approach to migrating a legacy monolithic application to a modern, service-oriented architecture without causing downtime.

Where candidates lose points

Prioritize clean code over speed

During your coding challenges, take the time to write clean, self-documenting code. Add helpful comments and explain your logic clearly to your interviewers.

Master your SQL

Make sure you are comfortable writing multi-table joins, group-by aggregations, and explaining database indexing strategies, as data queries are a key part of the evaluation.

Prepare your STAR stories

Have three to four solid behavioral examples ready that showcase your problem-solving, collaboration, and adaptability in past roles.

Ask thoughtful questions

Use the time at the end of your interviews to ask insightful questions about the company's technical roadmap, engineering culture, and team dynamics.

Questions & practice

Write a program to justify a given list of words into lines of a specific maximum width (Text Justification).

Medium · Coding and Algorithmic Problem-Solving

Approach

1. Restate the input: its shape, its size, and what is guaranteed about it.
2. Name the brute-force solution and its complexity before improving on it.
3. Choose the data structure from the access pattern, not from familiarity.
4. State the target complexity and say which constraint rules the naive version out.

Follow-up

• How does this change if the input no longer fits in memory?
• What is the worst case, and how likely is it on real data?

Implement a function to parse and clean a raw dataset, handling missing values and mismatched data types.

Medium · Coding and Algorithmic Problem-Solving

Approach

1. Restate the input: its shape, its size, and what is guaranteed about it.
2. Name the brute-force solution and its complexity before improving on it.
3. Choose the data structure from the access pattern, not from familiarity.
4. State the target complexity and say which constraint rules the naive version out.

Follow-up

• How does this change if the input no longer fits in memory?
• What is the worst case, and how likely is it on real data?

Create a utility to format and manipulate structured text inputs for rendering on a front-end interface.

Medium · Coding and Algorithmic Problem-Solving

Approach

1. Restate the input: its shape, its size, and what is guaranteed about it.
2. Name the brute-force solution and its complexity before improving on it.
3. Choose the data structure from the access pattern, not from familiarity.
4. State the target complexity and say which constraint rules the naive version out.

Follow-up

• How does this change if the input no longer fits in memory?
• What is the worst case, and how likely is it on real data?

Write a SQL query to retrieve and aggregate user engagement metrics from a multi-table database schema.

Medium · Databases and System Design

Approach

1. Name the grain you start from and join outward from it.
2. Check whether any join is one-to-many before aggregating, or the sums inflate.
3. Say which index the query would use, and what makes it unusable.
4. Handle the rows that do not match: that is usually the actual question.

Follow-up

• How does the query change if that join becomes one-to-many?
• What happens to this when the table is ten times larger?

How would you structure a database schema to support a dynamic doctor search feature with multiple filtering c

Medium · Databases and System Design

How would you structure a database schema to support a dynamic doctor search feature with multiple filtering criteria?

Approach

1. Name the grain you start from and join outward from it.
2. Check whether any join is one-to-many before aggregating, or the sums inflate.
3. Say which index the query would use, and what makes it unusable.
4. Handle the rows that do not match: that is usually the actual question.

Follow-up

• How does the query change if that join becomes one-to-many?
• What happens to this when the table is ten times larger?

Design an algorithm to search and filter through user-generated reviews based on dynamic keywords and ratings.

Medium · Coding and Algorithmic Problem-Solving

Approach

1. Fix the scope first: who calls this, how often, and what they do when it fails.
2. Name the read and write paths separately; they rarely have the same bottleneck.
3. Choose a partition key and say what query it makes expensive.
4. State the consistency you need, and where you are willing to be stale.

Follow-up

• What breaks first when traffic grows ten times?
• How does this behave when that dependency is down for an hour?

Explain how you would design a backend service to handle high-traffic media uploads, such as patient before-an

Medium · Databases and System Design

Explain how you would design a backend service to handle high-traffic media uploads, such as patient before-and-after photos.

Approach

1. Fix the scope first: who calls this, how often, and what they do when it fails.
2. Name the read and write paths separately; they rarely have the same bottleneck.
3. Choose a partition key and say what query it makes expensive.
4. State the consistency you need, and where you are willing to be stale.

Follow-up

• What breaks first when traffic grows ten times?
• How does this behave when that dependency is down for an hour?

Describe your approach to migrating a legacy monolithic application to a modern, service-oriented architecture

Medium · Databases and System Design

Describe your approach to migrating a legacy monolithic application to a modern, service-oriented architecture without causing downtime.

Approach

1. Fix the scope first: who calls this, how often, and what they do when it fails.
2. Name the read and write paths separately; they rarely have the same bottleneck.
3. Choose a partition key and say what query it makes expensive.
4. State the consistency you need, and where you are willing to be stale.

Follow-up

• What breaks first when traffic grows ten times?
• How does this behave when that dependency is down for an hour?

Read latency spikes on a sixty-second sawtooth

Medium · cache stampede · single-flight · ttl

The cached listing read path serves about 14k reads/second at an 85% hit rate. p99 sits at 35 ms for 57 seconds, jumps to 900 ms for 3, and repeats. During each spike the primary shows several hundred identical listing queries starting within the same millisecond, all carrying one large tenant's id. Cache entries use a 60-second TTL. Give the mechanism, the ordered checks, the fix, and the correctness hazard your fix must not introduce.

Approach

1. Match the period to a configured number before theorising about load. A spike every 60 seconds against a 60-second TTL is an entry expiring, and you confirm it by correlating spike timestamps with the entry's write time rather than with the traffic curve. If the period had matched a cron or a GC interval instead, this is a different investigation.
2. Establish the concurrency of the miss. Several hundred identical queries in one millisecond means the miss path has no coalescing: every request that arrives between expiry and repopulation recomputes. The herd size is that key's arrival rate times its recompute time, so at 1.2k reads/second for the hot key and a 250 ms recompute you expect about 300 concurrent misses, which matches what is observed.
3. Add single-flight on the miss path so one caller per key recomputes under a short-lived lock while the rest wait for its result. Prefer stale-while-revalidate where the read tolerates it: return the expired value immediately and refresh asynchronously, which removes the latency spike rather than serialising it into a queue of waiters.
4. De-synchronise the keys. Write TTLs with jitter, for example 60 seconds plus or minus 10%, so a deploy or a mass invalidation does not align every key on the same second and turn a per-key herd into a fleet-wide one.

Follow-up

• The same sawtooth appears on a key that is invalidated on write rather than expired. Is that the same bug?
• How does your answer change if the recompute takes 4 seconds instead of 250 ms?

Suggested practice checklist

Built from the rounds and topics RealSelf candidates report.

Day 1 — Map the RealSelf loop

• Write out the reported sequence: HR Screen, Take-Home Assessment, Live Video Interviews, Interview Loop.
• For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.

Deliverable: A one-page map of the 4 reported rounds, with the weakest marked.

Day 2 — Work Python

• Spend the session on Python, which RealSelf candidates report being tested on.
• Write one worked example in Python and time yourself on it.

Deliverable: One timed worked example in Python.

Day 3 — Work SQL

• Spend the session on SQL, which RealSelf candidates report being tested on.
• Write one worked example in SQL and time yourself on it.

Deliverable: One timed worked example in SQL.

Day 4 — Work Coding Challenges (Take-home / Online submissions)

• Spend the session on Coding Challenges (Take-home / Online submissions), which RealSelf candidates report being tested on.
• Write one worked example in Coding Challenges (Take-home / Online submissions) and time yourself on it.

Deliverable: One timed worked example in Coding Challenges (Take-home / Online submissions).

Day 5 — Answer out loud: Coding and Algorithmic Problem-Solving

• Answer aloud, timed: Write a program to justify a given list of words into lines of a specific maximum width (Text Justification).
• Answer aloud, timed: Implement a function to parse and clean a raw dataset, handling missing values and mismatched data types.

Deliverable: Spoken answers to 2 reported Coding and Algorithmic Problem-Solving question(s), under time.

Day 6 — Answer out loud: Databases and System Design

• Answer aloud, timed: Write a SQL query to retrieve and aggregate user engagement metrics from a multi-table database schema.
• Answer aloud, timed: Explain how you would design a backend service to handle high-traffic media uploads, such as patient before-and-after photos.

Deliverable: Spoken answers to 2 reported Databases and System Design question(s), under time.

Day 7 — Answer out loud: Behavioral and Culture Fit

• Answer aloud, timed: Describe a time when you had to work with a legacy codebase that lacked documentation. How did you approach understanding and refactoring it?
• Answer aloud, timed: Tell me about a time you had a disagreement with a Product Manager regarding a technical implementation. How did you resolve it?

Deliverable: Spoken answers to 2 reported Behavioral and Culture Fit question(s), under time.

Behavioural preparation

Behavioural rounds judge the decision you made and what it cost.

Describe a time when you had to work with a legacy codebase that lacked documentation. How did you approach un

Medium · Behavioral and Culture Fit

Describe a time when you had to work with a legacy codebase that lacked documentation. How did you approach understanding and refactoring it?

Approach

1. Pick a story where you made the decision, not one where you watched it.
2. State the situation in two sentences and spend the rest on the reasoning.
3. Give the blast radius: what could have broken, and what you measured.
4. Name the disagreement and how you resolved it with evidence.

Follow-up

• What would you do differently if you ran that again?
• How did you know your change caused the improvement?

Tell me about a time you had a disagreement with a Product Manager regarding a technical implementation. How d

Medium · Behavioral and Culture Fit

Tell me about a time you had a disagreement with a Product Manager regarding a technical implementation. How did you resolve it?

Approach

1. Pick a story where you made the decision, not one where you watched it.
2. State the situation in two sentences and spend the rest on the reasoning.
3. Give the blast radius: what could have broken, and what you measured.
4. Name the disagreement and how you resolved it with evidence.

Follow-up

• What would you do differently if you ran that again?
• How did you know your change caused the improvement?

Give an example of a project where you had to balance delivering a feature quickly versus writing perfect, opt

Medium · Behavioral and Culture Fit

Give an example of a project where you had to balance delivering a feature quickly versus writing perfect, optimized code.

Approach

1. Pick a story where you made the decision, not one where you watched it.
2. State the situation in two sentences and spend the rest on the reasoning.
3. Give the blast radius: what could have broken, and what you measured.
4. Name the disagreement and how you resolved it with evidence.

Follow-up

• What would you do differently if you ran that again?
• How did you know your change caused the improvement?

How do you handle receiving critical feedback on your code during a peer review?

Medium · Behavioral and Culture Fit

Approach

1. Pick a story where you made the decision, not one where you watched it.
2. State the situation in two sentences and spend the rest on the reasoning.
3. Give the blast radius: what could have broken, and what you measured.
4. Name the disagreement and how you resolved it with evidence.

Follow-up

• What would you do differently if you ran that again?
• How did you know your change caused the improvement?