cswork / libraryOpen practice workspace

Interview guides · Workshop Labs

Workshop Labs Software Engineer Interview Guide

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

The 60-second brief

A Software Engineer at Workshop Labs plays a critical role in designing, developing, and scaling the core technology products that drive the company's business. Working within highly collaborative, cross-functional teams, you will build and optimize software solutions that handle high-volume transactions, complex data processing, and seamless user experiences. The engineering team is responsible for maintaining a robust, modern tech stack while continuously pushing the boundaries of performance and system reliability. At Workshop Labs, engineers do not work in silos. You will collaborate closely with Solutions Architects, Product Managers, and Quality Assurance specialists to translate business requirements into clean, maintainable, and highly performant code.

This guide is scoped to a Software Engineer candidate at Workshop Labs.

Focus areas

  • Java
  • Spring Framework (Spring/Spring Boot)
  • Live Coding

The Workshop Labs interview process

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

Initial Conversation

The process begins with an initial contact to discuss the candidate's background and interest in the role.

What to demonstrate

  • The process begins with an initial contact to discuss the candidate's background and interest in the role
  • Depth in Java

How to prepare

  • Answer aloud and timed: Explain the lifecycle of a request in a Spring Boot application.
  • Answer aloud and timed: What are the different thread states in Java, and how do you manage concurrency?

Technical Assessment

Candidates are evaluated on practical engineering skills, problem-solving speed, and technical depth.

What to demonstrate

  • Candidates are evaluated on practical engineering skills, problem-solving speed, and technical depth
  • Depth in Java

How to prepare

  • Answer aloud and timed: How does RabbitMQ handle message queuing, and when would you use it over other message brokers?
  • Answer aloud and timed: Explain the difference between class-based and function-based views in Django.

Cultural Alignment

Assessment of the candidate's ability to collaborate and align with the engineering organization's culture.

What to demonstrate

  • Assessment of the candidate's ability to collaborate and align with the engineering organization's culture
  • Depth in Java

How to prepare

  • Answer aloud and timed: How do you implement dependency injection, and why is it beneficial for testability?
  • Answer aloud and timed: How does the event loop work in JavaScript?

Final Decision

The recruitment team communicates the final hiring decision, typically within 24 to 48 hours after the last round.

What to demonstrate

  • The recruitment team communicates the final hiring decision, typically within 24 to 48 hours after the last round
  • Depth in Java

How to prepare

  • Answer aloud and timed: What is the difference between asynchronous execution and multi-threading?
  • Answer aloud and timed: How would you implement a custom array filtering function in plain vanilla JS without using built-in prototype methods?

Where candidates lose points

Clarify the exact team stack early

Workshop Labs has different product teams using different technologies. Ask your recruiter during the initial call whether the team you are interviewing for focuses on Java, Python, or JavaScript so you can tailor your preparation.

Brush up on your vanilla JavaScript

Even if you are a backend engineer, be prepared for a coding challenge that tests core programming logic using plain JavaScript. Focus on solving the problem cleanly without relying on external libraries.

Prepare your system architecture story

Have a detailed, 10-minute explanation of a complex system you built in the past ready. Be prepared to draw the architecture on a whiteboard, explain the data flow, and defend your choice of databases, protocols, and messaging queues.

Questions & practice

What are the different thread states in Java, and how do you manage concurrency?

Medium · Core Backend & Frameworks

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?

How does the event loop work in JavaScript?

Medium · Frontend & Language Fundamentals

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?

What is the difference between asynchronous execution and multi-threading?

Medium · Frontend & Language Fundamentals

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?

How would you implement a custom array filtering function in plain vanilla JS without using built-in prototype

Medium · Frontend & Language Fundamentals

How would you implement a custom array filtering function in plain vanilla JS without using built-in prototype methods?

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 difference between let, const, and var in modern JavaScript.

Medium · Frontend & Language Fundamentals

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?

Find version gaps and relay lag with window functions

Medium · window functions · event tables · frame semantics

outbox_event holds event_id, aggregate_type, aggregate_id, aggregate_version, event_type, payload, status ('pending','published','dead'), attempts, created_at, published_at. A projection is missing rows and you must decide whether the relay skipped events or the consumer dropped them. Write three queries over the last seven days: one listing every aggregate_id whose published aggregate_version sequence has a hole, one giving per-day counts with a running total, and one returning the newest published event per aggregate. For each, say where the window function is evaluated relative to WHERE and LIMIT. PostgreSQL 16.

Approach

  1. Gaps: compute lead(aggregate_version) OVER (PARTITION BY aggregate_id ORDER BY aggregate_version) in a subquery, then filter next_version <> aggregate_version + 1 in the outer query. Window functions are evaluated after WHERE, GROUP BY and HAVING and before the outer ORDER BY and LIMIT, so the predicate cannot sit in the same WHERE clause and PostgreSQL 16 has no QUALIFY.
  2. Say what the seven-day filter does to the answer: it truncates every partition, so the first row per aggregate has no predecessor inside the window and a hole spanning the boundary is invisible. Widen the window, or join to resource.version as the authority for the true maximum.
  3. Running total: SELECT date_trunc('day', created_at) AS d, count() AS n, sum(count()) OVER (ORDER BY date_trunc('day', created_at) ROWS UNBOUNDED PRECEDING). An aggregate inside a window call is legal because grouping runs before windowing. The grouping key is unique per row here so ROWS and RANGE agree, but write the frame anyway — over ungrouped rows with tied timestamps the default RANGE frame pulls in every peer row and the total jumps.
  4. Newest per aggregate: DISTINCT ON (aggregate_id) ... ORDER BY aggregate_id, aggregate_version DESC is the cheap PostgreSQL-only form when an index matches that order; row_number() OVER (PARTITION BY aggregate_id ORDER BY aggregate_version DESC) = 1 is the portable form and needs a subquery for the same evaluation-order reason as the gap query.

Follow-up

  • Relay failover redelivers events. Does a duplicate break the gap query, and how would you detect one from this table alone?
  • Turn the gap check into a continuous monitor rather than a query someone runs after an incident. What does it watch?

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?

Explain the lifecycle of a request in a Spring Boot application.

Medium · Core Backend & Frameworks

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 does RabbitMQ handle message queuing, and when would you use it over other message brokers?

Medium · Core Backend & Frameworks

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?

Explain the difference between class-based and function-based views in Django.

Medium · Core Backend & Frameworks

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 implement dependency injection, and why is it beneficial for testability?

Medium · Core Backend & Frameworks

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?

Walk me through the architecture of a previous project you worked on. What were the main bottlenecks, and how

Medium · System Design & Architecture

Walk me through the architecture of a previous project you worked on. What were the main bottlenecks, and how did you resolve them?

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 design a system to handle high-throughput, asynchronous events?

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?

What design patterns would you use to decouple a monolithic application into microservices?

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 do you secure REST services against common vulnerabilities like SQL injection and cross-site scripting?

Medium · System Design & Architecture

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?

One customer endpoint stalls deliveries to every other destination

Medium · bulkhead · timeouts · saturation

The egress service delivers about 1.5k webhooks/second across 40,000 destinations, with a per-destination concurrency cap of 4 and a 10-second connect-plus-read timeout. Throughput falls to 300/second, queue depth climbs, and p99 delivery latency for unaffected destinations goes from 200 ms to minutes, while the error rate barely moves. One tenant holds 900 destination rows whose URLs share a hostname that now answers in 9.5 seconds. Explain the mechanism with the arithmetic, then give the containment in the order you would apply it.

Approach

  1. Look at saturation before errors. A flat error rate with collapsing throughput says nothing is failing, things are waiting, so the first signal to pull is in-flight request count or pool wait time rather than the error counter. This is the distinction that decides the whole investigation.
  2. Group in-flight work by resolved host, not by destination id. The cap is keyed per destination row, so 900 rows sharing one hostname buy 3,600 concurrent slots against a single host, each held for 9.5 seconds. The bulkhead was never a bulkhead for that host, and grouping by the wrong dimension is why the dashboard looked healthy.
  3. Do the arithmetic in both directions. Required concurrency is arrival rate times latency, so 1.5k/second at 200 ms needs about 300 in flight, which is entirely consumed by 3,600 slow slots; conversely whatever concurrency is left sustains rate equals concurrency divided by 9.5 seconds, which is the 300/second you are seeing. Matching both numbers is what promotes this from a plausible story to the mechanism.
  4. Explain why the circuit breaker never helped. It opens on consecutive failures, and a 9.5-second response inside a 10-second timeout is a success. Slow is not failing, so an error-rate breaker cannot see this; you need a slow-call ratio, a deadline propagated from the caller's remaining budget, or a concurrency limiter.

Follow-up

  • The host recovers to 80 ms. How long does the queue take to drain, and what does the drain do to the recovered host?
  • Where should the 10-second timeout number actually come from?

Suggested practice checklist

Built from the rounds and topics Workshop Labs candidates report.

Day 1 — Map the Workshop Labs loop

  • Write out the reported sequence: Initial Conversation, Technical Assessment, Cultural Alignment, Final Decision.
  • 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 Java

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

Deliverable: One timed worked example in Java.

Day 3 — Work Spring Framework (Spring/Spring Boot)

  • Spend the session on Spring Framework (Spring/Spring Boot), which Workshop Labs candidates report being tested on.
  • Write one worked example in Spring Framework (Spring/Spring Boot) and time yourself on it.

Deliverable: One timed worked example in Spring Framework (Spring/Spring Boot).

Day 4 — Work Live Coding

  • Spend the session on Live Coding, which Workshop Labs candidates report being tested on.
  • Write one worked example in Live Coding and time yourself on it.

Deliverable: One timed worked example in Live Coding.

Day 5 — Answer out loud: Core Backend & Frameworks

  • Answer aloud, timed: Explain the lifecycle of a request in a Spring Boot application.
  • Answer aloud, timed: What are the different thread states in Java, and how do you manage concurrency?

Deliverable: Spoken answers to 2 reported Core Backend & Frameworks question(s), under time.

Day 6 — Answer out loud: Frontend & Language Fundamentals

  • Answer aloud, timed: How does the event loop work in JavaScript?
  • Answer aloud, timed: What is the difference between asynchronous execution and multi-threading?

Deliverable: Spoken answers to 2 reported Frontend & Language Fundamentals question(s), under time.

Day 7 — Answer out loud: System Design & Architecture

  • Answer aloud, timed: Walk me through the architecture of a previous project you worked on. What were the main bottlenecks, and how did you resolve them?
  • Answer aloud, timed: How do you design a system to handle high-throughput, asynchronous events?

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

Behavioural preparation

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

How do you manage technical debt when working under tight product deadlines?

Medium · Behavioral & Software Development Lifecy

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 your experience with agile methodologies and how the SDLC was structured in your previous company.

Medium · Behavioral & Software Development Lifecy

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 disagree with a Solutions Architect on a technical decision?

Medium · Behavioral & Software Development Lifecy

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 is your approach to code reviews, and how do you ensure code quality across the team?

Medium · Behavioral & Software Development Lifecy

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?