cswork / libraryOpen practice workspace

Interview guides · Cult.fit

Cult.fit Software Engineer Interview Guide

Cult.fit Software Engineer interview guide: reported rounds, questions and how candidates describe the process.

The 60-second brief

As a Software Engineer at Cult.fit, you are at the intersection of consumer technology, health, and high-performance engineering. You will be responsible for building and scaling the digital infrastructure that powers India’s leading fitness and wellness ecosystem. Your work directly impacts millions of users, ranging from seamless class bookings and live workout streams to complex backend systems that manage personalized health data. This role is critical because Cult.fit operates at a massive scale, requiring engineers to solve complex problems related to concurrency, real-time data processing, and user experience optimization. You will work within cross-functional teams to translate ambitious business goals into robust, maintainable, and high-performing technical solutions.

This guide is scoped to a Software Engineer candidate at Cult.fit.

Focus areas

  • Software Engineering
  • SDE Leveling (SDE 3)
  • Interview Process Design

The Cult.fit interview process

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

Initial Technical Screen

Candidates undergo an initial technical screening to assess their foundational skills.

What to demonstrate

  • Candidates undergo an initial technical screening to assess their foundational skills
  • Depth in Software Engineering

How to prepare

  • Answer aloud and timed: How would you design a highly scalable booking system for fitness classes to handle high concurrency?
  • Answer aloud and timed: Explain the trade-offs between SQL and NoSQL databases in the context of user health profiles.

Role-Specific Assessment

More intensive evaluations focused on the specific requirements of the Software Engineer role.

What to demonstrate

  • More intensive evaluations focused on the specific requirements of the Software Engineer role
  • Depth in Software Engineering

How to prepare

  • Answer aloud and timed: How do you ensure high availability for live-streamed workout sessions?
  • Answer aloud and timed: Describe a situation where you had to refactor a legacy system to improve performance.

Final Offer Discussion

Discussion regarding the final offer after completing the interview rounds.

What to demonstrate

  • Discussion regarding the final offer after completing the interview rounds
  • Depth in Software Engineering

How to prepare

  • Answer aloud and timed: How do you approach API design for a mobile-first application to ensure minimal latency?
  • Answer aloud and timed: Given a set of user activity logs, how would you identify the most active users in real-time?

Where candidates lose points

Own your narrative

If you sense the interview is unstructured, take control by summarizing your experience and highlighting how it aligns with Cult.fit's goals.

Focus on trade-offs

Never give a "best" solution without mentioning the trade-offs (e.g., latency vs. consistency).

Be ready for ambiguity

Many interviewers will provide vague requirements. Ask clarifying questions early to show that you think like an engineer who solves real problems.

Stay calm under pressure

If you get stuck on a coding problem, communicate your thought process out loud. Interviewers care more about your problem-solving process than your ability to arrive at the perfect answer immediately.

Questions & practice

Given a set of user activity logs, how would you identify the most active users in real-time?

Medium · Problem-Solving & Coding

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 thread-safe caching mechanism for frequently accessed user data.

Medium · Problem-Solving & Coding

Approach

  1. Say what the runtime actually does before reasoning about the code.
  2. Name what is shared across threads and what owns each piece of state.
  3. Identify the window where an invariant is briefly untrue.
  4. Distinguish a value from a reference to it, and say which one you handed out.

Follow-up

  • What happens if two callers reach this at the same time?
  • Where could this allocate more than you expect?

Optimize a function that processes large batches of user subscription data.

Medium · Problem-Solving & Coding

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?

What do you do when you are faced with an ambiguous problem and limited documentation?

Medium · Behavioral & Leadership

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?

Explain the trade-offs between SQL and NoSQL databases in the context of user health profiles.

Medium · Technical & 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?

Hold a per-tenant active cap against concurrent creates

Hard · write skew · isolation levels · constraints

A tenant on the standard plan may hold at most 50 resources with status='active'. The create handler runs SELECT count(*) FROM resource WHERE tenant_id = $1 AND status = 'active', compares to 50, then inserts. Two creates arrive 3 ms apart on different instances and the tenant lands at 51. Name the anomaly, say whether PostgreSQL 16 READ COMMITTED or REPEATABLE READ prevents it and why, then give an implementation that holds the cap at READ COMMITTED with the exact statements. Finally, say what changes when the cap is 'at most one running export per tenant' on job_run.

Approach

  1. Name it: write skew. The two transactions read an overlapping set and write disjoint rows, so there is no row-level conflict for the engine to detect and each commit is individually legal.
  2. Rule out the levels precisely. READ COMMITTED takes a fresh snapshot per statement and takes no lock on the counted rows, so both see 49. PostgreSQL's REPEATABLE READ is snapshot isolation: it removes non-repeatable reads and phantoms within the snapshot but still admits write skew, because the anomaly is not a re-read of a changed row, it is a read of a set that a concurrent transaction invalidates. Only SERIALIZABLE closes it, by tracking the read dependency and aborting one transaction with SQLSTATE 40001 — a guarantee that exists only if the application re-runs the whole transaction from the read.
  3. Convert the set predicate into a single-row conflict: keep tenant.active_resource_count and run UPDATE tenant SET active_resource_count = active_resource_count + 1 WHERE tenant_id = $1 AND active_resource_count < 50 in the same transaction as the INSERT. Zero affected rows is the cap, returned as 409. The row lock serialises the decision at any isolation level, and contention is bounded to one tenant's row — which is also the fair-scheduling unit, unlike a global counter that would convoy every tenant behind one row.
  4. State the cost you just took on: a counter is a second source of truth that can drift, so every path that changes status must adjust it inside the same transaction, and a periodic reconciliation has to exist, with resource_revision as the authority for what the count should have been.

Follow-up

  • A resource moves from archived back to active. Which statements change, and what breaks if the counter update and the status change land in different transactions?
  • The cap becomes plan-dependent and a plan can change mid-month. Where does the number 50 live, and who reads it?

How would you design a highly scalable booking system for fitness classes to handle high concurrency?

Medium · Technical & System Design

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?

How do you ensure high availability for live-streamed workout sessions?

Medium · Technical & System Design

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 a situation where you had to refactor a legacy system to improve performance.

Medium · Technical & System Design

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?

How do you approach API design for a mobile-first application to ensure minimal latency?

Medium · Technical & System Design

Approach

  1. Say who the caller is and what they do when the call fails halfway.
  2. Define the identity of a request so a retry cannot double-apply it.
  3. Separate accepted, pending, failed and confirmed; they are different facts.
  4. Design the error taxonomy before the success shape; callers branch on it.

Follow-up

  • What happens if the caller retries after a timeout?
  • How does a client discover it is on an old version of this contract?

How would you handle race conditions in a distributed booking environment?

Medium · Problem-Solving & Coding

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 your approach to debugging a production issue that only occurs intermittently.

Medium · Problem-Solving & Coding

Approach

  1. Establish what changed and when, before forming any theory.
  2. Pick a bisection that eliminates candidates whichever way it turns out.
  3. Check the instrumentation before believing the symptom.
  4. Separate the trigger from the cause; the deploy is rarely the bug.

Follow-up

  • What would you look at first, and what would it rule out?
  • How would you tell a cause from a coincidence here?

Suggested practice checklist

Built from the rounds and topics Cult.fit candidates report.

Day 1 — Map the Cult.fit loop

  • Write out the reported sequence: Initial Technical Screen, Role-Specific Assessment, Final Offer Discussion.
  • 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 3 reported rounds, with the weakest marked.

Day 2 — Work Software Engineering

  • Spend the session on Software Engineering, which Cult.fit candidates report being tested on.
  • Write one worked example in Software Engineering and time yourself on it.

Deliverable: One timed worked example in Software Engineering.

Day 3 — Work SDE Leveling (SDE 3)

  • Spend the session on SDE Leveling (SDE 3), which Cult.fit candidates report being tested on.
  • Write one worked example in SDE Leveling (SDE 3) and time yourself on it.

Deliverable: One timed worked example in SDE Leveling (SDE 3).

Day 4 — Work Interview Process Design

  • Spend the session on Interview Process Design, which Cult.fit candidates report being tested on.
  • Write one worked example in Interview Process Design and time yourself on it.

Deliverable: One timed worked example in Interview Process Design.

Day 5 — Answer out loud: Technical & System Design

  • Answer aloud, timed: How would you design a highly scalable booking system for fitness classes to handle high concurrency?
  • Answer aloud, timed: Explain the trade-offs between SQL and NoSQL databases in the context of user health profiles.

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

Day 6 — Answer out loud: Problem-Solving & Coding

  • Answer aloud, timed: Given a set of user activity logs, how would you identify the most active users in real-time?
  • Answer aloud, timed: Implement a thread-safe caching mechanism for frequently accessed user data.

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

Day 7 — Answer out loud: Behavioral & Leadership

  • Answer aloud, timed: Tell me about a time you had to disagree with a product manager on a feature requirement.
  • Answer aloud, timed: How do you handle a situation where you have conflicting technical priorities?

Deliverable: Spoken answers to 2 reported Behavioral & Leadership question(s), under time.

Behavioural preparation

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

Tell me about a time you had to disagree with a product manager on a feature requirement.

Medium · Behavioral & Leadership

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 a situation where you have conflicting technical priorities?

Medium · Behavioral & Leadership

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?

Describe a time you mentored a junior engineer or improved team processes.

Medium · Behavioral & Leadership

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?