cswork / libraryOpen practice workspace

Interview guides · Select Minds

Select Minds Software Engineer Interview Guide

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

The 60-second brief

A Software Engineer at Select Minds plays a pivotal role in designing, developing, and modernizing robust applications across a diverse set of client environments. Because Select Minds delivers high-impact technology solutions to various industries, engineers here work on everything from enterprise full-stack applications and cloud-native automation pipelines to critical legacy database systems. Your work directly influences system reliability, operational efficiency, and the digital transformation journeys of the organizations we support. What makes this position both challenging and rewarding is the sheer breadth of technologies and environments you will interact with. On any given project, you might be automating cloud infrastructure using Terraform on AWS or Azure, building scalable APIs with Java or.NET, or optimizing legacy enterprise workflows.

This guide is scoped to a Software Engineer candidate at Select Minds.

Focus areas

  • Software Engineering
  • Terraform
  • COBOL

The Select Minds interview process

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

Background Assessment

Initial evaluation of your background to determine fit for the role.

What to demonstrate

  • Initial evaluation of your background to determine fit for the role
  • Depth in Software Engineering

How to prepare

  • Answer aloud and timed: How would you design a secure, automated pipeline to deploy virtual machine images across both AWS and Azure?
  • Answer aloud and timed: Describe a scenario where you had to troubleshoot a critical performance bottleneck in a production environment. What was your methodology?

Technical Evaluations

Deep technical and scenario-based evaluations to assess coding abilities.

What to demonstrate

  • Deep technical and scenario-based evaluations to assess coding abilities
  • Depth in Software Engineering

How to prepare

  • Answer aloud and timed: How do you design an API gateway to handle high-traffic spikes while ensuring low latency and high availability?
  • Answer aloud and timed: Walk me through how you would architect a multi-tenant full-stack application using.NET or Java.

Architectural Review

High-level architectural evaluation to gauge design and system thinking.

What to demonstrate

  • High-level architectural evaluation to gauge design and system thinking
  • Depth in Software Engineering

How to prepare

  • Answer aloud and timed: What strategies do you use to ensure data consistency across distributed microservices?
  • Answer aloud and timed: What are the key differences between managing state in Terraform for AWS versus Azure?

Behavioral Review

Assessment of cultural alignment and soft skills through behavioral questions.

What to demonstrate

  • Assessment of cultural alignment and soft skills through behavioral questions
  • Depth in Software Engineering

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 review above and write down what you would ask to confirm before it.

Where candidates lose points

Structure your scenario answers

When facing scenario-based questions, use the STAR method (Situation, Task, Action, Result) to keep your answers structured and impactful. Focus on your specific contributions and the technical decisions you made.

Talk through your whiteboarding

Do not solve problems in silence. Talk your interviewer through your thought process, explain the trade-offs of your approach, and invite feedback as you sketch out your designs.

Be prepared to walk through your architectural decisions step-by-step

Interviewers value clear communication and structured thinking over a perfect initial design.

Questions & practice

How do you optimize database queries and handle connection pooling in high-concurrency environments?

Medium · Technical & Domain-Specific

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?

Canonicalise a request body into a stable idempotency fingerprint

Medium · parsing · canonicalisation · hashing

idempotency_key.request_fingerprint is a SHA-256 over the method, path and canonicalised body, and a retry whose fingerprint differs must be rejected with 422 rather than served the stored response. Write the canonicaliser. Bodies are JSON up to 256 KB nested at most 32 levels; clients vary key order, whitespace and unicode escaping, and some send 64-bit ids as JSON numbers. Produce a deterministic byte string such that semantically identical bodies match and any semantic difference does not. State your complexity and name two normalisations you refuse to perform.

Approach

  1. Parse once into a tree, then re-serialise under fixed rules: object keys sorted, array order preserved, one escaping convention, no insignificant whitespace. Parsing is O(n) and sorting keys is O(k log k) per object, so O(n log n) overall with O(depth) stack, and the 32-level cap is enforced during parsing because hostile nesting is how a canonicaliser becomes a stack overflow.
  2. Sort keys by their UTF-8 bytes and say why the obvious implementation is wrong in some runtimes: a default string comparison that orders by UTF-16 code units places surrogate pairs, meaning code points from U+10000 up, below U+E000 to U+FFFF, which is not UTF-8 byte order, so two services written in different languages disagree on the same document.
  3. Do not re-encode numbers through a double. IEEE-754 binary64 represents integers exactly only up to 2^53, so normalising a 19-digit id through a float changes it, and 1 against 1.0 cannot be reconciled without deciding whether they are the same value. Preserve the literal token, and require ids as strings at the API boundary if you want them comparable.
  4. Reject duplicate keys rather than picking one. JSON permits them and parsers disagree, most keeping the last, so any choice you make ties the fingerprint to a parser detail that the code handling the request does not necessarily share.

Follow-up

  • A client sends the same logical request with an extra field your API ignores. Same key, different fingerprint, so you return 422. Is that the right answer?
  • Where does the fingerprint get computed relative to request decompression and the body-size limit?

Collapse a redelivered event batch into per-aggregate high-water marks

Easy · hashing · at-least-once · aggregation

You drain a batch of up to 5,000,000 events, each (aggregate_id BIGINT, aggregate_version INT, event_type, payload). The log guarantees order within one aggregate only; the batch merges 64 partitions, and a relay failover has redelivered a range, so an older version for an aggregate can appear after a newer one. Given a map of last_applied_version per aggregate, produce the events worth applying, at most one per (aggregate_id, version), plus the count discarded. Target O(n) time. State the memory for 2,000,000 distinct aggregates and what you do when it does not fit.

Approach

  1. One pass, one hash map from aggregate_id to the highest version kept, and a discard counter. An event whose version is at or below last_applied_version for its aggregate is dropped without further work, which is the whole reason the event carries its version rather than a delta. O(n) expected time, O(d) space in distinct aggregates.
  2. Keep the maximum, never the last occurrence. The redelivered range means the final appearance of an aggregate in the batch can be an older version than one seen earlier in the same batch, so last-wins applies stale state over newer state and the projection regresses with no error anywhere.
  3. Cost the memory instead of calling it large: an 8-byte key plus a 4-byte version is 12 bytes of payload, and an open-addressed table held at a 0.7 load factor costs roughly 17 bytes per entry before per-slot metadata, so 2,000,000 aggregates is tens of megabytes in a native layout and several times that in a runtime that boxes both key and value.
  4. If the distinct set exceeds memory, partition on hash(aggregate_id) mod P and reduce each partition independently. Every event for one aggregate hashes to the same partition, so the per-partition result is exact and the merge is concatenation rather than a second reduction.

Follow-up

  • The payload is a patch rather than a snapshot, so applying only the highest version loses the intermediate changes. What changes in your reduction?
  • How do you detect that version 7 arrived while version 6 was never delivered, and what should the consumer do about the gap?

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?

Write the update path that detects a concurrent edit

Medium · optimistic concurrency · transactional outbox · audit history

resource carries version INT NOT NULL DEFAULT 1. resource_revision holds revision_id, resource_id, version, actor_user_id, change_kind, patch JSONB, request_id, created_at with UNIQUE (resource_id, version). outbox_event holds aggregate_type, aggregate_id, aggregate_version, event_type, payload, status. A PUT carries the version the client read. Write the exact statements for the single transaction that applies the edit, records the revision and enqueues 'resource.updated', and give the handler's branch on zero affected rows. Then say what PostgreSQL 16 does under READ COMMITTED when two of these updates hit one row at once.

Approach

  1. One transaction, three writes, no network call inside it: UPDATE resource SET title = $3, version = version + 1, updated_at = now() WHERE resource_id = $1 AND tenant_id = $4 AND version = $2; then INSERT the resource_revision row at version $2 + 1; then INSERT the outbox_event row at the same aggregate_version. The event goes to a table rather than a broker because no transaction spans both.
  2. Branch on the affected-row count before doing anything else. Zero has three causes — stale version, wrong tenant, row gone — so re-read once and map to 409 carrying the current version, or 404 for an id outside the caller's tenant, which also stops the endpoint confirming that another tenant's id exists.
  3. State the engine behaviour instead of assuming it. Under READ COMMITTED the second UPDATE blocks on the row lock, and when the first commits PostgreSQL re-evaluates the WHERE clause against the newly committed row, so the version predicate now fails and the statement reports zero rows. Under REPEATABLE READ the identical collision raises SQLSTATE 40001 instead, so the handler must fold both shapes into one conflict response.
  4. Keep UNIQUE (resource_id, version) even though the predicate already serialises writers. It is what makes a lost update unwritable if any other path ever reaches the revision table, and it converts a logic bug into 23505 rather than into a silently missing history row.

Follow-up

  • A client sends the version it read ten minutes ago and the resource has moved three versions. What is in your 409 so it can resolve the conflict without a full re-fetch?
  • Two editors, two disjoint fields, no overlap. Does your answer still refuse the second write, and should it?

How would you design a secure, automated pipeline to deploy virtual machine images across both AWS and Azure?

Medium · Scenario-Based & 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 design an API gateway to handle high-traffic spikes while ensuring low latency and high availabilit

Medium · Scenario-Based & System Design

How do you design an API gateway to handle high-traffic spikes while ensuring low latency and high availability?

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?

Walk me through how you would architect a multi-tenant full-stack application using.NET or Java.

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

What strategies do you use to ensure data consistency across distributed microservices?

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

What are the key differences between managing state in Terraform for AWS versus Azure?

Medium · Technical & Domain-Specific

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 life cycle of an HTTP request in a.NET Core or Spring Boot application.

Medium · Technical & Domain-Specific

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?

What is your approach to writing unit and integration tests for legacy systems, such as COBOL or older enterpr

Medium · Technical & Domain-Specific

What is your approach to writing unit and integration tests for legacy systems, such as COBOL or older enterprise applications?

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?

Describe how you manage secrets and configuration parameters securely in a cloud-native environment.

Medium · Technical & Domain-Specific

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 a scenario where you had to troubleshoot a critical performance bottleneck in a production environmen

Medium · Scenario-Based & System Design

Describe a scenario where you had to troubleshoot a critical performance bottleneck in a production environment. What was your methodology?

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 Select Minds candidates report.

Day 1 — Map the Select Minds loop

  • Write out the reported sequence: Background Assessment, Technical Evaluations, Architectural Review, Behavioral Review.
  • 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 Software Engineering

  • Spend the session on Software Engineering, which Select Minds 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 Terraform

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

Deliverable: One timed worked example in Terraform.

Day 4 — Work COBOL

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

Deliverable: One timed worked example in COBOL.

Day 5 — Answer out loud: Scenario-Based & System Design

  • Answer aloud, timed: How would you design a secure, automated pipeline to deploy virtual machine images across both AWS and Azure?
  • Answer aloud, timed: Describe a scenario where you had to troubleshoot a critical performance bottleneck in a production environment. What was your methodology?

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

Day 6 — Answer out loud: Technical & Domain-Specific

  • Answer aloud, timed: What are the key differences between managing state in Terraform for AWS versus Azure?
  • Answer aloud, timed: Explain the life cycle of an HTTP request in a.NET Core or Spring Boot application.

Deliverable: Spoken answers to 2 reported Technical & Domain-Specific question(s), under time.

Day 7 — Answer out loud: Behavioral & Adaptability

  • Answer aloud, timed: Tell me about a time you had to quickly learn a new technology or framework to deliver a project. How did you approach the learning curve?
  • Answer aloud, timed: How do you handle disagreements with a technical lead or architect regarding system design choices?

Deliverable: Spoken answers to 2 reported Behavioral & Adaptability 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 quickly learn a new technology or framework to deliver a project. How did you

Medium · Behavioral & Adaptability

Tell me about a time you had to quickly learn a new technology or framework to deliver a project. How did you approach the learning curve?

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 a technical lead or architect regarding system design choices?

Medium · Behavioral & Adaptability

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 situation where you had to balance delivering a feature quickly versus writing perfect, technical-d

Medium · Behavioral & Adaptability

Describe a situation where you had to balance delivering a feature quickly versus writing perfect, technical-debt-free 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 maintain clear communication and alignment when working with remote or hybrid cross-functional team

Medium · Behavioral & Adaptability

How do you maintain clear communication and alignment when working with remote or hybrid cross-functional teams?

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?