cswork / libraryOpen practice workspace

Interview guides · Exc@v8

Exc@v8 Software Engineer Interview Guide

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

The 60-second brief

At Exc@v8, the Software Engineer role—often aligned with our specialized fleet and heavy plant technical operations—is the backbone of our commitment to operational excellence. You are not just writing code or managing systems; you are ensuring that the complex machinery and heavy equipment powering our clients' industries remain operational, efficient, and safe. This position is critical because it bridges the gap between high-level engineering logic and physical, real-world utility. Whether you are working on agricultural, heavy plant, or HGV fleet systems, your contributions directly impact the uptime of essential infrastructure. You will be expected to diagnose complex mechanical and software-integrated systems, solve unique technical problems in the field or the workshop, and maintain the high standards that Exc@v8 is known for. 02 · Compensation

This guide is scoped to a Software Engineer candidate at Exc@v8.

Focus areas

  • Software Engineering (General)
  • Diagnostics and Troubleshooting
  • Fleet Management (Technical)

The Exc@v8 interview process

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

Initial Screening

Gauge your technical background and interest in specific service areas.

What to demonstrate

  • Gauge your technical background and interest in specific service areas
  • Depth in Software Engineering (General)

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 Discussions

Engage in in-depth technical discussions to assess your knowledge.

What to demonstrate

  • Engage in in-depth technical discussions to assess your knowledge
  • Depth in Software Engineering (General)

How to prepare

  • Answer aloud and timed: Explain your process for prioritizing repairs when faced with multiple critical equipment failures.
  • Answer aloud and timed: What specific experience do you have with the diagnostic software tools used in modern HGV or heavy plant environments?

Situational Assessments

Simulate challenges you would face in the workshop or field.

What to demonstrate

  • Simulate challenges you would face in the workshop or field
  • Depth in Software Engineering (General)

How to prepare

  • Answer aloud and timed: Describe a situation where you identified a safety risk in a workshop environment. What actions did you take?
  • Answer aloud and timed: How do you ensure that your technical documentation is accurate and useful for other engineers?

Team Interaction

Collaborate with team members to showcase your problem-solving approach.

What to demonstrate

  • Collaborate with team members to showcase your problem-solving approach
  • Depth in Software Engineering (General)

How to prepare

  • Answer aloud and timed: What steps do you take to stay updated with the latest technological advancements in heavy vehicle or plant machinery?
  • Answer aloud and timed: Tell me about a time you had to explain a complex technical issue to a non-technical client or colleague.

Final Evaluation

Undergo a final assessment to evaluate your overall fit for the role.

What to demonstrate

  • Undergo a final assessment to evaluate your overall fit for the role
  • Depth in Software Engineering (General)

How to prepare

  • Answer aloud and timed: How do you handle high-pressure situations where a client’s equipment is down and needs immediate attention?
  • Answer aloud and timed: Give an example of how you have collaborated with other team members to resolve a particularly difficult technical bottleneck.

Where candidates lose points

Practice your "why

Be ready to clearly articulate why you want to work for Exc@v8 and why you are passionate about heavy engineering.

Use the STAR method

When answering behavioral questions, use the Situation, Task, Action, and Result format to keep your answers structured and impactful.

Ask meaningful questions

Use the end of your interview to ask about the team's current technical challenges or the company's approach to new technology.

Do not attempt to guess an answer if you are unsure of a technical detail

It is much better to explain your process for finding the answer than to provide incorrect information.

Questions & practice

Explain your process for prioritizing repairs when faced with multiple critical equipment failures.

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

What specific experience do you have with the diagnostic software tools used in modern HGV or heavy plant envi

Medium · Technical Diagnostic & Problem Solving

What specific experience do you have with the diagnostic software tools used in modern HGV or heavy plant environments?

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?

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?

Hold a per-tenant active cap against concurrent creates

Hard · write skew · isolation levels · constraints

A tenant on the standard plan may hold at most 50 resources with status='active'. The create handler runs SELECT count(*) FROM resource WHERE tenant_id = $1 AND status = 'active', compares to 50, then inserts. Two creates arrive 3 ms apart on different instances and the tenant lands at 51. Name the anomaly, say whether PostgreSQL 16 READ COMMITTED or REPEATABLE READ prevents it and why, then give an implementation that holds the cap at READ COMMITTED with the exact statements. Finally, say what changes when the cap is 'at most one running export per tenant' on job_run.

Approach

  1. Name it: write skew. The two transactions read an overlapping set and write disjoint rows, so there is no row-level conflict for the engine to detect and each commit is individually legal.
  2. Rule out the levels precisely. READ COMMITTED takes a fresh snapshot per statement and takes no lock on the counted rows, so both see 49. PostgreSQL's REPEATABLE READ is snapshot isolation: it removes non-repeatable reads and phantoms within the snapshot but still admits write skew, because the anomaly is not a re-read of a changed row, it is a read of a set that a concurrent transaction invalidates. Only SERIALIZABLE closes it, by tracking the read dependency and aborting one transaction with SQLSTATE 40001 — a guarantee that exists only if the application re-runs the whole transaction from the read.
  3. Convert the set predicate into a single-row conflict: keep tenant.active_resource_count and run UPDATE tenant SET active_resource_count = active_resource_count + 1 WHERE tenant_id = $1 AND active_resource_count < 50 in the same transaction as the INSERT. Zero affected rows is the cap, returned as 409. The row lock serialises the decision at any isolation level, and contention is bounded to one tenant's row — which is also the fair-scheduling unit, unlike a global counter that would convoy every tenant behind one row.
  4. State the cost you just took on: a counter is a second source of truth that can drift, so every path that changes status must adjust it inside the same transaction, and a periodic reconciliation has to exist, with resource_revision as the authority for what the count should have been.

Follow-up

  • A resource moves from archived back to active. Which statements change, and what breaks if the counter update and the status change land in different transactions?
  • The cap becomes plan-dependent and a plan can change mid-month. Where does the number 50 live, and who reads it?

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?

How do you approach reading and interpreting complex technical schematics or software-integrated diagrams?

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

Describe a situation where you identified a safety risk in a workshop environment. What actions did you take?

Medium · Operational & Procedural Knowledge

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 ensure that your technical documentation is accurate and useful for other engineers?

Medium · Operational & Procedural Knowledge

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 steps do you take to stay updated with the latest technological advancements in heavy vehicle or plant ma

Medium · Operational & Procedural Knowledge

What steps do you take to stay updated with the latest technological advancements in heavy vehicle or plant machinery?

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?

p99 jumped on one listing filter while p50 stayed flat

Medium · query planning · composite index · percentiles

After a release that added an owner_user_id filter to the resource listing, p99 rose from 90 ms to 1.9 s while p50 stayed at 40 ms. Traffic and row counts are unchanged. resource carries the index (tenant_id, status, updated_at DESC, resource_id DESC). The new query filters tenant_id and owner_user_id, orders by updated_at DESC, resource_id DESC, and takes 20 rows. On PostgreSQL, explain the shape of the regression, prove it from a query plan, and give the index you would add.

Approach

  1. Start from the shape. A flat p50 with a moved p99 means a subset of requests changed cost, not all of them, so the first job is naming the subset. Bucket the endpoint's latency by the tenant's row count; the natural hypothesis is that large tenants are a small share of requests and all of the tail.
  2. Get the plan for the new query on a large tenant with EXPLAIN (ANALYZE, BUFFERS). Expect an index scan over the tenant's range, a filter discarding most of it, then a Sort feeding the Limit, possibly reporting Sort Method: external merge Disk. Read actual rows on the scan node, not estimated.
  3. Explain why the existing index cannot serve it. A composite B-tree is seekable only as a left prefix, and with no equality predicate on status the scan cannot treat updated_at as an ordering, because rows in the tenant's range are ordered by status first. Everything matching must be read and sorted before LIMIT 20 can apply, so a tenant with 400,000 rows pays 400,000 rows to return 20.
  4. Add (tenant_id, owner_user_id, updated_at DESC, resource_id DESC). Equality on the first two columns leaves the index ordered by updated_at within that pair, so the plan becomes an index scan that stops after 20 rows with no Sort node. PostgreSQL can scan a B-tree backwards, so the DESC markers matter only if the two sort columns ever disagree in direction; keeping them explicit documents the order the keyset cursor depends on.

Follow-up

  • The endpoint paginates with OFFSET. What does page 500 cost with your index, and what does the keyset version cost?
  • How would you have caught this before release, given that a 10,000-row seed database produces the same plan shape at an unnoticeable cost?

Suggested practice checklist

Built from the rounds and topics Exc@v8 candidates report.

Day 1 — Map the Exc@v8 loop

  • Write out the reported sequence: Initial Screening, Technical Discussions, Situational Assessments, Team Interaction, Final Evaluation.
  • 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 Software Engineering (General)

  • Spend the session on Software Engineering (General), which Exc@v8 candidates report being tested on.
  • Write one worked example in Software Engineering (General) and time yourself on it.

Deliverable: One timed worked example in Software Engineering (General).

Day 3 — Work Diagnostics and Troubleshooting

  • Spend the session on Diagnostics and Troubleshooting, which Exc@v8 candidates report being tested on.
  • Write one worked example in Diagnostics and Troubleshooting and time yourself on it.

Deliverable: One timed worked example in Diagnostics and Troubleshooting.

Day 4 — Work Fleet Management (Technical)

  • Spend the session on Fleet Management (Technical), which Exc@v8 candidates report being tested on.
  • Write one worked example in Fleet Management (Technical) and time yourself on it.

Deliverable: One timed worked example in Fleet Management (Technical).

Day 5 — Answer out loud: Technical Diagnostic & Problem Solving

  • Answer aloud, timed: Describe a time you diagnosed a fault in a system that had multiple potential failure points. How did you isolate the root cause?
  • Answer aloud, timed: How do you approach reading and interpreting complex technical schematics or software-integrated diagrams?

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

Day 6 — Answer out loud: Operational & Procedural Knowledge

  • Answer aloud, timed: Describe a situation where you identified a safety risk in a workshop environment. What actions did you take?
  • Answer aloud, timed: How do you ensure that your technical documentation is accurate and useful for other engineers?

Deliverable: Spoken answers to 2 reported Operational & Procedural Knowledge question(s), under time.

Day 7 — Answer out loud: Behavioral & Team Collaboration

  • Answer aloud, timed: Tell me about a time you had to explain a complex technical issue to a non-technical client or colleague.
  • Answer aloud, timed: How do you handle high-pressure situations where a client’s equipment is down and needs immediate attention?

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

Behavioural preparation

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

Describe a time you diagnosed a fault in a system that had multiple potential failure points. How did you isol

Medium · Technical Diagnostic & Problem Solving

Describe a time you diagnosed a fault in a system that had multiple potential failure points. How did you isolate the root cause?

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 to explain a complex technical issue to a non-technical client or colleague.

Medium · Behavioral & Team Collaboration

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 high-pressure situations where a client’s equipment is down and needs immediate attention?

Medium · Behavioral & Team Collaboration

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?

Give an example of how you have collaborated with other team members to resolve a particularly difficult techn

Medium · Behavioral & Team Collaboration

Give an example of how you have collaborated with other team members to resolve a particularly difficult technical bottleneck.

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?