cswork / libraryOpen practice workspace

Interview guides · Redapt

Redapt Software Engineer Interview Guide

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

The 60-second brief

As a Software Engineer at Redapt, you are at the intersection of complex infrastructure, cloud-native services, and high-performance computing. Redapt is a leader in data center infrastructure and cloud solutions, meaning your work directly influences how enterprise-grade systems are architected, deployed, and managed. You are not just writing code; you are building the connective tissue that allows large-scale environments to remain resilient and efficient. This role requires a blend of deep technical curiosity and practical problem-solving. Whether you are focusing on Hyper-V virtualization or Network System Engineering, you will be expected to tackle challenges that impact the core performance of client environments.

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

Focus areas

  • Hyper-V
  • Network System Engineering
  • Software Engineering

The Redapt interview process

Redapt candidates report 2 rounds over 2-4 weeks. The stages below are what candidates describe, not a published process.

Recruiter Screen

Initial discussion to align on goals and expectations.

What to demonstrate

  • Initial discussion to align on goals and expectations
  • Depth in Hyper-V

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 Deep Dives

Series of interviews with team leads and the broader engineering team focusing on technical skills.

What to demonstrate

  • Series of interviews with team leads and the broader engineering team focusing on technical skills
  • Depth in Hyper-V

How to prepare

  • Answer aloud and timed: If you were tasked with automating a manual infrastructure deployment, what tools and strategies would you choose?
  • Answer aloud and timed: How do you balance the need for quick feature delivery with the requirement for long-term system stability?

Where candidates lose points

Structure your answers

Use the STAR method (Situation, Task, Action, Result) for behavioral questions to ensure your responses are concise and impactful.

Be ready to dive deep

If you mention a specific technology or project on your resume, be prepared to answer follow-up questions about its architecture, challenges, and your specific contribution.

Ask thoughtful questions

Use the time at the end of your interviews to ask about the team’s current technical hurdles or how they approach project planning.

Questions & practice

Write a function to parse and validate a specific configuration file format.

Medium · Coding and Algorithms

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?

Given a set of network logs, how would you programmatically extract and count unique error occurrences?

Medium · Coding and Algorithms

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?

Solve a standard algorithmic challenge (e.g., array manipulation or string processing) to demonstrate your gra

Medium · Coding and Algorithms

Solve a standard algorithmic challenge (e.g., array manipulation or string processing) to demonstrate your grasp of data structures.

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?

Keep soft-deleted accounts from blocking re-registration

Easy · soft delete · unique constraints · engine differences

app_user holds user_id, tenant_id, email CITEXT, password_hash (NULL for SSO principals), email_verified_at, auth_version, status ('invited','active','suspended','deactivated'), created_at, updated_at, deleted_at. Two live accounts for one address inside a tenant must be impossible, but an address freed by a soft delete must be reusable, and the same tenant may delete and re-register it repeatedly. Write the uniqueness DDL for PostgreSQL 16, then the equivalent for MySQL 8 where partial indexes do not exist, and say what each permits once three deleted rows already hold that address.

Approach

  1. Start from what is actually unique: not (tenant_id, email), but (tenant_id, email) among live rows. PostgreSQL says that directly — CREATE UNIQUE INDEX app_user_live_email ON app_user (tenant_id, email) WHERE deleted_at IS NULL. A full constraint over the same two columns burns the address permanently the first time someone deletes an account.
  2. Keep case-insensitivity in the type or the index, never in the application: CITEXT as given, or UNIQUE (tenant_id, lower(email)) as an expression index where the extension is unavailable. A case-sensitive unique column is exactly how two accounts for one human appear.
  3. For MySQL 8 the predicate has to move inside the key: add a discriminator column that is a constant 0 while the row is live and is set to user_id on delete, with UNIQUE (tenant_id, email, deleted_marker). Live rows share the constant and still collide; deleted rows differ from each other and stop colliding.
  4. State the NULL variant and its dependency: leaving the marker NULL for deleted rows also works, because a unique index treats NULLs as distinct — true in MySQL, and true in PostgreSQL only under the default NULLS DISTINCT, which PostgreSQL 15 lets you reverse. Check the polarity against the three existing deleted rows: constant-on-live is what preserves the collision you want, and reversing it silently admits duplicate live accounts.

Follow-up

  • A deleted account re-registers with the same address the next day. Do the old resource rows follow the new user_id, and how does the API keep the two principals apart?
  • How do you honour an erasure request while resource_revision.actor_user_id still references this table?

Denormalise tenant onto revisions and backfill it live

Hard · denormalisation · online migration · backfill

resource_revision (revision_id, resource_id, version, actor_user_id, change_kind, patch, request_id, created_at) has 400M rows and no tenant column; tenant_id lives only on resource. Two reads need it: a tenant-scoped audit feed ordered by created_at DESC, and an offboarding purge. Both join back to resource today. Justify adding tenant_id to resource_revision against those two reads, name the anomaly the copy introduces and the constraint that prevents it, then give the ordered migration for a live table taking 1.2k writes/second — the lock each step takes, how the backfill is batched, and where each step stops being reversible. PostgreSQL 16.

Approach

  1. Justify from the access path rather than from taste. Without the column, the audit feed either scans resource_revision by created_at and discards other tenants' rows, or resolves the tenant's resource_ids first and probes with them — both proportional to the tenant's whole history rather than to one page. With (tenant_id, created_at DESC, revision_id DESC) it is a seek that stops at 50 rows, and the purge becomes a ranged delete instead of a join.
  2. Name the cost exactly: a second copy of a fact can disagree with the first. Make the disagreement unwritable rather than documented — add UNIQUE (resource_id, tenant_id) on resource so it can serve as a foreign-key target, then FOREIGN KEY (resource_id, tenant_id) REFERENCES resource (resource_id, tenant_id) on the revision table. A revision can then only ever carry its parent's tenant.
  3. Step one, expand: ALTER TABLE resource_revision ADD COLUMN tenant_id BIGINT NULL, with no default, so it is a catalogue change and no rewrite. It still needs ACCESS EXCLUSIVE for an instant, and that instant queues behind the longest open transaction on the table while every later query queues behind it — set lock_timeout to 2s and retry rather than wait.
  4. Step two, dual-write: deploy the writer that populates tenant_id on every new revision while reads still use the join. Reversible by redeploying the previous build, because nothing reads the column yet.

Follow-up

  • The backfill is half finished and a rollback is required. What state is the table in, and what does the previous build do with a half-populated column?
  • How do you verify the backfill actually finished, given rows are still being inserted while it runs?

If you were tasked with automating a manual infrastructure deployment, what tools and strategies would you cho

Medium · Problem-Solving and Technical Logic

If you were tasked with automating a manual infrastructure deployment, what tools and strategies would you choose?

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

How do you balance the need for quick feature delivery with the requirement for long-term system stability?

Medium · Problem-Solving and Technical Logic

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

Describe your process for documentation when working on a complex system architecture.

Medium · Behavioral and Team Dynamics

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 troubleshooting a significant performance degradation in a virtualized environment?

Medium · Problem-Solving and Technical Logic

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

Day 1 — Map the Redapt loop

  • Write out the reported sequence: Recruiter Screen, Technical Deep Dives.
  • 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 2 reported rounds, with the weakest marked.

Day 2 — Work Hyper-V

  • Spend the session on Hyper-V, which Redapt candidates report being tested on.
  • Write one worked example in Hyper-V and time yourself on it.

Deliverable: One timed worked example in Hyper-V.

Day 3 — Work Network System Engineering

  • Spend the session on Network System Engineering, which Redapt candidates report being tested on.
  • Write one worked example in Network System Engineering and time yourself on it.

Deliverable: One timed worked example in Network System Engineering.

Day 4 — Work Software Engineering

  • Spend the session on Software Engineering, which Redapt 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 5 — Answer out loud: Problem-Solving and Technical Logic

  • Answer aloud, timed: How would you approach troubleshooting a significant performance degradation in a virtualized environment?
  • Answer aloud, timed: Describe a time you had to optimize a piece of code to improve latency or resource consumption.

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

Day 6 — Answer out loud: Coding and Algorithms

  • Answer aloud, timed: Write a function to parse and validate a specific configuration file format.
  • Answer aloud, timed: Given a set of network logs, how would you programmatically extract and count unique error occurrences?

Deliverable: Spoken answers to 2 reported Coding and Algorithms question(s), under time.

Day 7 — Answer out loud: Behavioral and Team Dynamics

  • Answer aloud, timed: Tell me about a time you had a technical disagreement with a teammate; how did you resolve it?
  • Answer aloud, timed: How do you handle ambiguity when project requirements are not fully defined?

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

Behavioural preparation

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

Describe a time you had to optimize a piece of code to improve latency or resource consumption.

Medium · Problem-Solving and Technical Logic

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 technical disagreement with a teammate; how did you resolve it?

Medium · Behavioral and Team Dynamics

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 ambiguity when project requirements are not fully defined?

Medium · Behavioral and Team Dynamics

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?