Roofstock Software Engineer Interview Guide

The 60-second brief

As a Software Engineer at Roofstock, you are at the intersection of high-growth fintech and the complex, trillion-dollar real estate market. Your work directly impacts how investors discover, analyze, and purchase single-family rental properties. You are building the digital infrastructure that makes real estate investing as accessible as trading stocks, requiring a balance of robust backend architecture and intuitive frontend experiences. The role demands more than just coding proficiency; it requires a product-minded approach to engineering. Whether you are optimizing data processing pipelines, building scalable analytical engines, or refining the user-facing marketplace, you are solving real-world problems that bring transparency and efficiency to a traditionally opaque industry.

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

Focus areas

• Systems Design (Whiteboard/Virtual)
• Technical Interview Rounds
• Communication Skills (Technical)

The Roofstock interview process

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

Recruiter Screen

Initial discussion with a recruiter to review your background and interest in Roofstock.

What to demonstrate

• Initial discussion with a recruiter to review your background and interest in Roofstock
• Depth in Systems Design (Whiteboard/Virtual)

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.

Technical Conversations

Series of discussions with hiring managers and engineering leads to assess technical foundation.

What to demonstrate

• Series of discussions with hiring managers and engineering leads to assess technical foundation
• Depth in Systems Design (Whiteboard/Virtual)

How to prepare

• Answer aloud and timed: How do you ensure the reliability and scalability of the services you build?
• Answer aloud and timed: Describe your process for handling edge cases when designing a new API endpoint.

System Design Exercises

Engagements focused on evaluating your ability to design systems in a real-world context.

What to demonstrate

• Engagements focused on evaluating your ability to design systems in a real-world context
• Depth in Systems Design (Whiteboard/Virtual)

How to prepare

• Answer aloud and timed: How do you evaluate the trade-offs between different data storage solutions for a specific use case?
• Answer aloud and timed: Walk me through the design of a system that processes large volumes of real estate data.

Behavioral Interviews

Interviews that explore how you navigate teamwork and handle ambiguity.

What to demonstrate

• Interviews that explore how you navigate teamwork and handle ambiguity
• Depth in Systems Design (Whiteboard/Virtual)

How to prepare

• Prepare three examples from your own work, each with a decision you made and an outcome you can quantify.
• Re-read the description of the behavioral interviews above and write down what you would ask to confirm before it.

Final Rounds

Conversations with team leadership to finalize assessment and fit.

What to demonstrate

• Conversations with team leadership to finalize assessment and fit
• Depth in Systems Design (Whiteboard/Virtual)

How to prepare

• Answer aloud and timed: How do you approach database schema design for a complex, relational data model?
• Answer aloud and timed: Tell me about a time you had to pivot your technical approach due to changing requirements.

Where candidates lose points

Prepare your "Why

Be ready to clearly articulate why you want to work at Roofstock specifically, rather than just any fintech company.

Embrace the "Conversational" Style

Our interviewers are humans, not robots. Engage with them, ask questions about their own experiences, and treat the interview as a two-way discovery.

Focus on Impact

When describing your past work, use the STAR method (Situation, Task, Action, Result) to highlight the specific impact you had on your team or product.

Review your own code

If you have open-source projects or public repositories, be prepared to walk through them. Being able to explain your own design decisions is a strong signal.

Questions & practice

Explain a time you had to weigh technical debt against the need for rapid feature delivery.

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

How do you evaluate the trade-offs between different data storage solutions for a specific use case?

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

Archive a resource graph without breaking live references or recursing

Medium · graph traversal · topological order · tenant isolation

Resources reference other resources within a tenant; for the largest tenant the reference table holds up to 2,000,000 nodes and 8,000,000 edges. Archiving a resource must archive everything reachable from it that nothing outside the set still references, refuse when a live external referrer exists, and terminate when references form cycles, which they legitimately do. Produce the archive order and the refusal list, targeting O(V+E). Say what stops the traversal crossing a tenant boundary, and why recursion is the wrong control structure at this size.

Approach

1. Load the subgraph with the tenant predicate on both endpoints of the edge, not only on the side you started from. Scoping the left table alone is the classic cross-tenant leak: one mis-entered edge then pulls another tenant's resources into the traversal and, worse, into the archive.
2. Traverse iteratively with an explicit stack. A 2,000,000-node graph can hold a chain deep enough to exhaust a native stack in the low tens of thousands of frames, and that failure is a process crash rather than an error you can return.
3. Treat cycles as data rather than corruption: compute strongly connected components with Tarjan in O(V+E) using its own explicit stack, then condense. The condensation is a DAG, so a topological order over it gives the archive order, and every member of a component archives in one transaction because no order within a cycle is valid.
4. Decide refusals with reverse edges. A candidate is archivable only if every in-edge originates inside the candidate set, so build the transpose or count in-degrees restricted to the visited set, and emit each blocked resource with the id of the external referrer, which is the only part of the answer an operator can act on.

Follow-up

• The graph is read in one query and the archive writes a minute later. What can change in between, and how do you make the write safe?
• The candidate set is 400,000 resources. Is that one transaction, and if not, what does a half-finished archive look like to a reader?

How do you approach database schema design for a complex, relational data model?

Medium · System Design & Architecture

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?

Explain why the owner filter ignores the listing index

Medium · composite index · query plans · sort elimination

The only index on resource is (tenant_id, status, updated_at DESC, resource_id DESC). A new endpoint returns one user's resources across all statuses, newest created first: WHERE tenant_id = $1 AND owner_user_id = $2 ORDER BY created_at DESC LIMIT 20. On a tenant with 2M rows it takes 900 ms and EXPLAIN shows a sort above a large scan. Explain precisely why the existing index cannot serve it, give the index that can, and state which of these the new index still will not help: owner_user_id alone across tenants; the same query ordered by updated_at. PostgreSQL 16.

Approach

1. Separate the two jobs an index does. For filtering, a composite btree is seekable only on a left prefix, so with no predicate on status the scan can at best range over tenant_id and test owner_user_id per row; PostgreSQL 16 has no btree skip scan to jump the unconstrained column.
2. For ordering, the index is sorted by (status, updated_at) within a tenant and not by created_at, so the LIMIT cannot stop early: every matching row is read and then sorted. That is the 'Sort Method: top-N heapsort' line, and it is why the plan reads 2M rows to answer with 20.
3. Derive the replacement from the access path — equality, equality, then the ordering column: CREATE INDEX CONCURRENTLY ON resource (tenant_id, owner_user_id, created_at DESC). The scan seeks to the (tenant, owner) range and walks 20 entries in order, so the Sort node disappears along with the row-read.
4. Treat INCLUDE (title, status) as conditional, not free. An index-only scan still visits the heap for any row whose page is not marked all-visible, so on a table taking 1.2k writes/second the win depends on autovacuum keeping the visibility map current, and the wider index costs more on every insert.

Follow-up

• 90% of rows are status='active'. Would a partial index WHERE status = 'active' change your answer, and for which of the three queries?
• A dashboard runs this for 40 owners in one page load. What changes about the design?

How do you ensure the reliability and scalability of the services you build?

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

Describe your process for handling edge cases when designing a new API endpoint.

Medium · Technical & Problem Solving

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?

Walk me through the design of a system that processes large volumes of real estate data.

Medium · System Design & Architecture

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 would you architect a service that requires high availability and low latency?

Medium · System Design & Architecture

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?

Discuss the pros and cons of microservices versus monolithic architectures in our context.

Medium · System Design & Architecture

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 would you approach debugging a complex performance bottleneck in a distributed system?

Medium · Technical & Problem Solving

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 Roofstock candidates report.

Day 1 — Map the Roofstock loop

• Write out the reported sequence: Recruiter Screen, Technical Conversations, System Design Exercises, Behavioral Interviews, Final Rounds.
• 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 5 reported rounds, with the weakest marked.

Day 2 — Work Systems Design (Whiteboard/Virtual)

• Spend the session on Systems Design (Whiteboard/Virtual), which Roofstock candidates report being tested on.
• Write one worked example in Systems Design (Whiteboard/Virtual) and time yourself on it.

Deliverable: One timed worked example in Systems Design (Whiteboard/Virtual).

Day 3 — Work Technical Interview Rounds

• Spend the session on Technical Interview Rounds, which Roofstock candidates report being tested on.
• Write one worked example in Technical Interview Rounds and time yourself on it.

Deliverable: One timed worked example in Technical Interview Rounds.

Day 4 — Work Communication Skills (Technical)

• Spend the session on Communication Skills (Technical), which Roofstock candidates report being tested on.
• Write one worked example in Communication Skills (Technical) and time yourself on it.

Deliverable: One timed worked example in Communication Skills (Technical).

Day 5 — Answer out loud: Technical & Problem Solving

• Answer aloud, timed: How would you approach debugging a complex performance bottleneck in a distributed system?
• Answer aloud, timed: Explain a time you had to weigh technical debt against the need for rapid feature delivery.

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

Day 6 — Answer out loud: System Design & Architecture

• Answer aloud, timed: Walk me through the design of a system that processes large volumes of real estate data.
• Answer aloud, timed: How would you architect a service that requires high availability and low latency?

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

Day 7 — Answer out loud: Behavioral & Cultural Alignment

• Answer aloud, timed: Tell me about a time you had to pivot your technical approach due to changing requirements.
• Answer aloud, timed: How do you handle disagreements with stakeholders regarding technical implementation?

Deliverable: Spoken answers to 2 reported Behavioral & Cultural Alignment 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 pivot your technical approach due to changing requirements.

Medium · Behavioral & Cultural Alignment

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 disagreements with stakeholders regarding technical implementation?

Medium · Behavioral & Cultural Alignment

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 project where you had to lead or mentor others through a difficult technical challenge.

Medium · Behavioral & Cultural Alignment

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?

What draws you to the intersection of real estate and technology?

Medium · Behavioral & Cultural Alignment

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?