cswork / libraryOpen practice workspace

Interview guides · St Engineering

St Engineering Software Engineer Interview Guide

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

The 60-second brief

St Engineering hires Software Engineers; this guide collects what candidates report about the process.

This guide is scoped to a Software Engineer candidate at St Engineering.

Focus areas

  • Programming language familiarity (self-rated)
  • System/Software lifecycle awareness (maintenance vs developm
  • Live coding / on-the-spot coding

The St Engineering interview process

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

HR Screening Call

Initial call to assess background, salary expectations, and general fit.

What to demonstrate

  • Initial call to assess background, salary expectations, and general fit
  • Depth in Programming language familiarity (self-rated)

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 Interviews

One or two rounds of interviews focusing on technical and managerial skills.

What to demonstrate

  • One or two rounds of interviews focusing on technical and managerial skills
  • Depth in Programming language familiarity (self-rated)

How to prepare

  • Answer aloud and timed: How does memory allocation work in C++, and how do you prevent memory leaks in a long-running system?
  • Answer aloud and timed: Describe the core principles of Object-Oriented Programming (OOP) and how you have applied them in a recent project.

Technical Assessment

May include an online HackerRank test, a take-home coding assignment, or a written technical paper.

What to demonstrate

  • May include an online HackerRank test, a take-home coding assignment, or a written technical paper
  • Depth in Programming language familiarity (self-rated)

How to prepare

  • Answer aloud and timed: Explain how a database index works and how you would optimize a slow-running SQL query.
  • Answer aloud and timed: How would you design a scalable backend API using FastAPI or gRPC to handle real-time data streaming?

Department Head Review

Final review by the department head, typically after technical interviews.

What to demonstrate

  • Final review by the department head, typically after technical interviews
  • Depth in Programming language familiarity (self-rated)

How to prepare

  • Answer aloud and timed: Describe your experience with containerization tools like Docker and orchestration platforms like Kubernetes.
  • Answer aloud and timed: How do you handle API integration when connecting different platforms and video management systems?

Offer Discussion

Discussion regarding the job offer and terms.

What to demonstrate

  • Discussion regarding the job offer and terms
  • Depth in Programming language familiarity (self-rated)

How to prepare

  • Answer aloud and timed: Walk us through how you would design a secure, fault-tolerant system architecture for a high-security environment.
  • Answer aloud and timed: What is your approach to setting up CI/CD pipelines, and how do you ensure zero-downtime deployments?

Where candidates lose points

Highlight Your Projects

Be ready to talk in-depth about your past projects, internships, or school work. Bring architecture diagrams or code snippets if permitted, and be prepared to explain your design choices and the trade-offs you made.

Brush Up on the Basics

Do not spend all your time memorizing complex dynamic programming algorithms. Instead, ensure you have a flawless grasp of basic data structures, OOP principles, memory management, and SQL queries.

Emphasize Security Awareness

Showing that you understand the importance of secure coding practices, data privacy, and compliance will make you stand out as a candidate who is ready for St Engineering's regulated environment.

Questions & practice

Explain the difference between multi-threading and multi-processing, and when you would use each in Python or

Medium · Technical & Programming Fundamentals

Explain the difference between multi-threading and multi-processing, and when you would use each in Python or C++.

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 memory allocation work in C++, and how do you prevent memory leaks in a long-running system?

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

Diff a projection against the primary without per-row point reads

Hard · reconciliation · range hashing · throttling

The listing projection has drifted and some rows show a stale version. The primary holds 40,000,000 resource rows across 12,000 tenants while serving 1,200 writes and 14,000 reads per second. The obvious repair, reading each resource row and comparing its version against the projection, is correct and would eventually finish. Explain precisely why it is unacceptable here, then give a diff that finds the differing rows, state its complexity, and make it safe to run against a live primary. Replication lag is usually under 100 ms and is not bounded.

Approach

  1. Quantify the naive cost rather than calling it slow: 40,000,000 point reads at even 0.5 ms each is over five hours serialised, and the only lever is concurrency, which is exactly what you cannot spend. The primary's pool is sized for the write path, and 40,000,000 random reads evict the buffer cache that sustains the 85 percent cache hit rate, so the audit degrades the system it is auditing.
  2. Replace random access with one ordered pass per side. Both sides can be read in (tenant_id, resource_id) order, which is a sequential scan on each and a merge join in O(n) time and O(1) memory. For a dense diff that is the whole answer, and it reads the primary once instead of 40,000,000 times.
  3. For the expected sparse case, compare range hashes instead of rows: partition the key space, compute per range an order-independent aggregate over hash(resource_id, version), compare aggregates, and descend only into ranges that differ. With d differing rows and branching factor B, at most d ranges mismatch per level, so the drill-down examines O(d log_B(n/d)) ranges and reads full rows only in mismatching leaves.
  4. Aggregate with a sum modulo 2^64 or a multiset hash, never XOR. XOR is order-independent but self-cancelling, so two rows wrong in the same way, or a row duplicated on one side, leave the range aggregate matching and the range is declared clean.

Follow-up

  • The diff reports 900 stale rows. How do you decide between patching those rows and rebuilding the projection from resource_revision?
  • Same job, but the projection lives in a search index that cannot be scanned in key order. What changes?

Explain how a database index works and how you would optimize a slow-running SQL query.

Medium · Technical & Programming Fundamentals

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?

Stop tag and share joins from fanning out a page

Medium · join fan-out · semi-joins · many-to-many

resource_tag is (resource_id, tag_id) with PK (resource_id, tag_id); resource_share is (resource_id, shared_with_user_id, permission). The tagged-and-shared listing inner-joins resource to both, filters tenant_id, tag_id = ANY($2) and shared_with_user_id = $3, orders by updated_at DESC and takes 50. Pages come back with fewer than 50 distinct resources and the total in the header is far too high. Explain the row multiplication, rewrite both the page query and the count query so each is correct, and name the index each one needs. PostgreSQL 16.

Approach

  1. Do the arithmetic against the predicates that are actually there. An inner join emits one row per matching child row, and both joins are filtered: tag_id = ANY($2) admits only the requested tags, shared_with_user_id = $3 admits one user's share rows. So a resource holding three of the requested tags and shared with $3 once yields three rows, not one — the multiplier is its count of matching tags times its share rows for that single user, and that second factor is 1 unless the table admits duplicate (resource_id, shared_with_user_id) pairs. LIMIT 50 then limits rows rather than resources, and COUNT(*) counts pairs — the header is the product, not the population.
  2. Reject DISTINCT as the fix. It deduplicates after the product has been built, so the planner must materialise and sort the fanned-out set before the LIMIT can apply, and it leaves any SUM or AVG in the same select list wrong.
  3. Rewrite both filters as semi-joins, keeping resource as the only row source: AND EXISTS (SELECT 1 FROM resource_tag rt WHERE rt.resource_id = r.resource_id AND rt.tag_id = ANY($2)) and the same shape against resource_share. A semi-join stops at the first match per resource and preserves the driving index order, so ORDER BY updated_at DESC, resource_id DESC LIMIT 50 still stops after 50 rows.
  4. Count with the same predicates and no join at all: SELECT count(*) FROM resource r WHERE r.tenant_id = $1 AND r.status = 'active' AND EXISTS (...) AND EXISTS (...). Nothing multiplies a resource, so the number is the population.

Follow-up

  • The filter changes from 'any of these tags' to 'all of these tags'. Rewrite it and state what it costs relative to the ANY form.
  • A resource can be shared with the same user twice under different permissions. Does your count change, and should it?

What are the primary differences between development and maintenance in the software development lifecycle?

Medium · Technical & Programming Fundamentals

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 the core principles of Object-Oriented Programming (OOP) and how you have applied them in a recent pr

Medium · Technical & Programming Fundamentals

Describe the core principles of Object-Oriented Programming (OOP) and how you have applied them in a recent project.

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 would you design a scalable backend API using FastAPI or gRPC to handle real-time data streaming?

Medium · System Architecture & Integration

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 handle API integration when connecting different platforms and video management systems?

Medium · System Architecture & Integration

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 us through how you would design a secure, fault-tolerant system architecture for a high-security environm

Medium · System Architecture & Integration

Walk us through how you would design a secure, fault-tolerant system architecture for a high-security environment.

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 is your approach to setting up CI/CD pipelines, and how do you ensure zero-downtime deployments?

Medium · System Architecture & Integration

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 us through a major software project from your resume. What was your specific role, and what tech stack di

Medium · Project & Academic Experience

Walk us through a major software project from your resume. What was your specific role, and what tech stack did you write the code in?

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 the architecture of a school or internship project you worked on. How did you handle database linkage

Medium · Project & Academic Experience

Describe the architecture of a school or internship project you worked on. How did you handle database linkages and data processing?

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 did you learn from your most recent internship, and how do you plan to apply those skills to this role?

Medium · Project & Academic Experience

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?

Are you comfortable working independently without constant supervision from a senior engineer? Provide an exam

Medium · Project & Academic Experience

Are you comfortable working independently without constant supervision from a senior engineer? Provide an example of when you did so.

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?

One log partition stops advancing while the others drain

Easy · poison message · head-of-line blocking · consumer lag

Search results for a subset of tenants are hours stale; the rest are current. The projection consumer reports lag of zero on 15 of 16 partitions and 400,000 on one. Its error rate is flat and its CPU is idle. outbox_event has no pending rows older than a second, so the relay has published everything it holds. Identify the mechanism, give the ordered checks, and state what you do in the first ten minutes versus what you change permanently.

Approach

  1. Read the lag distribution first. A slow consumer lags everywhere; zero on fifteen partitions and 400,000 on one is not throughput. Idle CPU on the stuck partition means the consumer is not advancing its offset at all, which points at one message it cannot get past rather than at a rate problem.
  2. Exonerate the producer before touching the consumer. No pending outbox rows older than a second means the relay published, so the event exists in the log. This separates never sent from sent and never applied, which are different code paths and usually different owners.
  3. Read the message at the stuck offset and the handler's log lines for its event_id. A flat error rate with no progress has two explanations and you must distinguish them: the handler is throwing and the retry loop is swallowing it, or the handler is blocking on something and never returning. Idle CPU with no error lines favours the second.
  4. Mitigate before diagnosing further. Move the offending event to a dead-letter store and commit the offset past it. Adding consumers does nothing here, because a partition is consumed by exactly one member of the group, and the blast radius is every aggregate hashed to that partition, not only the aggregate that produced the bad event.

Follow-up

  • The dead-lettered event carried aggregate_version 7 and the projection had applied 6. What must the replay do differently if 8 and 9 landed in the meantime?
  • How do you show staleness to the user while the partition is behind, given the API already returns the projection's watermark?

Suggested practice checklist

Built from the rounds and topics St Engineering candidates report.

Day 1 — Map the St Engineering loop

  • Write out the reported sequence: HR Screening Call, Technical Interviews, Technical Assessment, Department Head Review, 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 5 reported rounds, with the weakest marked.

Day 2 — Work Programming language familiarity (self-rated)

  • Spend the session on Programming language familiarity (self-rated), which St Engineering candidates report being tested on.
  • Write one worked example in Programming language familiarity (self-rated) and time yourself on it.

Deliverable: One timed worked example in Programming language familiarity (self-rated).

Day 3 — Work System/Software lifecycle awareness (maintenance vs development)

  • Spend the session on System/Software lifecycle awareness (maintenance vs development), which St Engineering candidates report being tested on.
  • Write one worked example in System/Software lifecycle awareness (maintenance vs development) and time yourself on it.

Deliverable: One timed worked example in System/Software lifecycle awareness (maintenance vs development).

Day 4 — Work Live coding / on-the-spot coding

  • Spend the session on Live coding / on-the-spot coding, which St Engineering candidates report being tested on.
  • Write one worked example in Live coding / on-the-spot coding and time yourself on it.

Deliverable: One timed worked example in Live coding / on-the-spot coding.

Day 5 — Answer out loud: Technical & Programming Fundamentals

  • Answer aloud, timed: What are the primary differences between development and maintenance in the software development lifecycle?
  • Answer aloud, timed: Explain the difference between multi-threading and multi-processing, and when you would use each in Python or C++.

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

Day 6 — Answer out loud: System Architecture & Integration

  • Answer aloud, timed: How would you design a scalable backend API using FastAPI or gRPC to handle real-time data streaming?
  • Answer aloud, timed: Describe your experience with containerization tools like Docker and orchestration platforms like Kubernetes.

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

Day 7 — Answer out loud: Behavioral & Scenario-Based

  • Answer aloud, timed: Describe a situation where you had to solve a difficult engineering problem under a tight deadline. How did you manage your time and pressure?
  • Answer aloud, timed: How do you handle conflict within a development team, especially when there is a disagreement on technical architecture?

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

Behavioural preparation

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

Describe your experience with containerization tools like Docker and orchestration platforms like Kubernetes.

Medium · System Architecture & Integration

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 solve a difficult engineering problem under a tight deadline. How did yo

Medium · Behavioral & Scenario-Based

Describe a situation where you had to solve a difficult engineering problem under a tight deadline. How did you manage your time and pressure?

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 conflict within a development team, especially when there is a disagreement on technical arc

Medium · Behavioral & Scenario-Based

How do you handle conflict within a development team, especially when there is a disagreement on technical architecture?

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?

Why are you interested in working with St Engineering, and how do you feel about working in highly secure, air

Medium · Behavioral & Scenario-Based

Why are you interested in working with St Engineering, and how do you feel about working in highly secure, air-gapped environments?

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 us about a time you had to learn a new technology or programming language quickly to deliver a project.

Medium · Behavioral & Scenario-Based

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 balance the need for rapid feature delivery with the necessity of maintaining clean, well-documente

Medium · Behavioral & Scenario-Based

How do you balance the need for rapid feature delivery with the necessity of maintaining clean, well-documented 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?