cswork / libraryOpen practice workspace

Interview guides · Nichols Consulting Engineers

Nichols Consulting Engineers Software Engineer Interview Guide

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

The 60-second brief

At Nichols Consulting Engineers (also known as NCE), the Software Engineer role sits at the critical intersection of advanced software engineering, geospatial analysis, and civil infrastructure. Unlike typical tech companies that build generic consumer applications, Nichols Consulting Engineers builds specialized, data-driven software platforms, asset management systems, and spatial modeling tools. These applications are used by municipalities, government agencies, and internal engineering teams to analyze pavement conditions, manage water resources, and optimize multi-million-dollar infrastructure budgets. As a Software Engineer in this domain, your work directly impacts the physical world. You will design and scale platforms that process massive amounts of geospatial (GIS) data, simulate environmental impacts, and run complex civil engineering algorithms.

This guide is scoped to a Software Engineer candidate at Nichols Consulting Engineers.

Focus areas

  • Pavement and Asset Management
  • Pavement Engineering
  • Water Resources Engineering

The Nichols Consulting Engineers interview process

Nichols Consulting Engineers candidates report 3 rounds over 3-5 weeks. The stages below are what candidates describe, not a published process.

Initial Conversation

Start with a conversation with a recruiter or engineering manager to align on your background and interest in the role.

What to demonstrate

  • Start with a conversation with a recruiter or engineering manager to align on your background and interest in the role
  • Depth in Pavement and Asset Management

How to prepare

  • Answer aloud and timed: How would you optimize a web application that needs to render tens of thousands of interactive road segments on a map?
  • Answer aloud and timed: What is your experience with spatial databases, and how do you write queries using PostGIS or SQL Server Spatial?

Technical Assessment

Participate in a technical assessment, which may include a take-home project or a live coding session focused on full-stack development, database design, or spatial data manipulation.

What to demonstrate

  • Participate in a technical assessment, which may include a take-home project or a live coding session focused on full-stack development, database design, or spatial data manipulation
  • Depth in Pavement and Asset Management

How to prepare

  • Answer aloud and timed: Explain how you would structure a RESTful API to allow external municipal clients to securely upload and process pavement inspection data.
  • Answer aloud and timed: How do you manage state in a complex front-end application when users are toggling multiple GIS layers and filtering large datasets?

Panel Interview

Present your work, discuss system design, and meet with cross-functional team members, including senior engineers and project managers.

What to demonstrate

  • Present your work, discuss system design, and meet with cross-functional team members
  • Including senior engineers and project managers

How to prepare

  • Answer aloud and timed: Describe your process for ensuring cross-browser compatibility and high performance for data-heavy dashboard interfaces.
  • Answer aloud and timed: Describe how you would build a data pipeline to ingest, clean, and store raw sensor data from pavement deflection testing vehicles.

Where candidates lose points

Focus on Practicality over Trendiness

When discussing system design or coding solutions, prioritize reliability, simplicity, and maintainability. NCE builds software that needs to run reliably for years, so over-engineering with the latest unproven framework is discouraged.

Avoid dismissing legacy data formats

In civil engineering consulting, you will frequently deal with older file formats, legacy databases, and Excel spreadsheets. Show that you can handle these gracefully rather than insisting on modern APIs only.

Highlight Your Spatial Experience

If you have worked with maps, GPS coordinates, or spatial databases in the past, make sure to highlight this. Even personal projects using mapping APIs are highly relevant.

Demonstrate Strong Communication

During your interviews, explain your thought process clearly. NCE values engineers who can discuss technical challenges with non-technical team members, as this is a daily occurrence in consulting.

Questions & practice

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?

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?

Find overlapping job attempts and peak concurrency from lease records

Medium · sweep line · intervals · leases

A day of job_run history yields about 50,000,000 attempt records: (job_run_id, job_type, attempt, started_at, finished_at which is NULL when the worker died, lease_expires_at). Leases expire on a clock, so a job that outran its lease ran twice. Produce (a) every job_run_id whose attempts overlapped in wall-clock time and (b) the peak number of simultaneously running attempts per job_type with the minute it occurred. Target O(n log n). State how you treat a NULL finished_at and what clock skew does to your answer.

Approach

  1. Define the interval before sorting anything: an attempt occupies [started_at, COALESCE(finished_at, lease_expires_at)). finished_at is observed and lease_expires_at is only a promise, so every attempt without a finish contributes an estimate and the whole result is a lower bound on overlap rather than an exact count.
  2. For peak concurrency, sweep: emit 2n endpoints, sort by (timestamp, kind) with ends ordered before starts at equal timestamps, then walk the sequence maintaining a counter per job_type and record each type's maximum with its timestamp. O(n log n) dominated by the sort, O(n) space, or O(1) extra if the sort is external and the walk streams.
  3. For overlap detection, do not compare attempts pairwise. A single global sort by (job_run_id, started_at) gives both the grouping and the order; within a group, keep the maximum end seen so far and report an overlap exactly when the next start is less than that running maximum, which is one linear pass after the sort.
  4. Half-open intervals matter and are easy to get wrong: with closed intervals an attempt ending at the same millisecond another begins reads as concurrency two, and across 50,000,000 records that artefact swamps the real signal.

Follow-up

  • A handler is not idempotent and you have found 400 overlapping jobs. Which of them actually caused damage, and what would you query to find out?
  • Peak concurrency for one job_type is 4 against a configured cap of 4. Is the cap working, or is the data hiding attempts that never started?

Replace offset paging on the resource feed with keyset

Easy · keyset pagination · composite index · sort order

resource holds resource_id, tenant_id, owner_user_id, title, body_ref, version, status ('draft','active','archived','deleted'), created_at, updated_at, deleted_at, with an index on (tenant_id, status, updated_at DESC, resource_id DESC). The listing endpoint returns active resources for one tenant, newest update first, 50 per page, today with LIMIT 50 OFFSET n. Tenants reach page 400 and rows are created while they read. Write the keyset query, define what the cursor carries and how it is encoded, and say which part of the index each predicate uses. Assume PostgreSQL 16.

Approach

  1. Name the two failures separately. OFFSET 20000 makes the server produce and discard 20,000 rows, so page cost grows with depth rather than with page size. Independently, any write that changes how many rows sort above the offset moves the window between two fetches, and the direction decides which anomaly you get: an insert lands at the head of updated_at DESC and pushes already-returned rows down past the boundary, so they are returned a second time; a delete above the offset, or a row whose updated_at is bumped above the cursor, pulls rows up and one is never returned at all. Nothing in the response reveals either.
  2. Write the seek: WHERE tenant_id = $1 AND status = 'active' AND (updated_at, resource_id) < ($2, $3) ORDER BY updated_at DESC, resource_id DESC LIMIT 50. The row-value comparison is one index range rather than a disjunction, and both columns are NOT NULL, which is what makes that comparison well defined.
  3. Map each predicate onto the index: tenant_id and status are equality on the leading columns, (updated_at, resource_id) is the range, and the ORDER BY matches the index order so no Sort node appears and the scan stops after 50 rows. The DESC in the definition only matters for mixed directions — a plain ascending btree on the same columns is read backwards for this query.
  4. Put both sort columns in the cursor and nothing the client can tamper with into another tenant: base64 of (updated_at, resource_id), validated server-side, with tenant_id taken from the principal.

Follow-up

  • The client asks for 'jump to page 400'. What do you offer instead, and what does the honest version cost?
  • Sort order becomes user-selectable across four columns. How many indexes is that, and which would you refuse to add?

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 optimize a web application that needs to render tens of thousands of interactive road segments o

Medium · Full-Stack & GIS Development

How would you optimize a web application that needs to render tens of thousands of interactive road segments on a map?

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 how you would structure a RESTful API to allow external municipal clients to securely upload and proce

Medium · Full-Stack & GIS Development

Explain how you would structure a RESTful API to allow external municipal clients to securely upload and process pavement inspection data.

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?

How do you manage state in a complex front-end application when users are toggling multiple GIS layers and fil

Medium · Full-Stack & GIS Development

How do you manage state in a complex front-end application when users are toggling multiple GIS layers and filtering large datasets?

Approach

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

Follow-up

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

Describe your process for ensuring cross-browser compatibility and high performance for data-heavy dashboard i

Medium · Full-Stack & GIS Development

Describe your process for ensuring cross-browser compatibility and high performance for data-heavy dashboard interfaces.

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 how you would build a data pipeline to ingest, clean, and store raw sensor data from pavement deflect

Medium · Data Engineering & Mathematical Modeling

Describe how you would build a data pipeline to ingest, clean, and store raw sensor data from pavement deflection testing vehicles.

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 translate a complex civil engineering formula (e.g., pavement deterioration curves or water runo

Medium · Data Engineering & Mathematical Modeling

How would you translate a complex civil engineering formula (e.g., pavement deterioration curves or water runoff simulations) into highly optimized code?

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 strategies do you use to validate data integrity when importing legacy infrastructure databases from muni

Medium · Data Engineering & Mathematical Modeling

What strategies do you use to validate data integrity when importing legacy infrastructure databases from municipal clients?

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 trade-offs between processing spatial calculations on the database level versus doing it in the ap

Medium · Data Engineering & Mathematical Modeling

Explain the trade-offs between processing spatial calculations on the database level versus doing it in the application code.

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?

Listing latency scales with page size, not with filters

Easy · n+1 · latency · query batching

The tenant listing endpoint reads resource filtered by tenant_id and status, ordered by updated_at DESC, and returns each row plus the owner's display name from app_user and the actor of that resource's latest resource_revision. p99 is 55 ms at 10 rows per page and 1.4 s at 200. Database telemetry shows 401 statements per request, each under 1 ms, and nothing in the slow-query log. Diagnose the cause and give the fix, stating the statement count per request and the p99 you expect afterwards.

Approach

  1. Read the counters before forming a theory. 401 statements for 200 rows is one driver query plus two per row, and sub-millisecond execution with an empty slow-query log rules out a bad plan. The time is round trips, which is why it is invisible in every per-query metric and scales with rows returned rather than with filter selectivity.
  2. Name the two per-row statements from their normalised text: a single-row app_user lookup by user_id, and a resource_revision lookup by resource_id ordered by version DESC LIMIT 1. Confirm by dropping those two response fields and watching the statement count fall to one. That locates the calls in the serialisation layer, not the repository.
  3. Check that the arithmetic accounts for the whole gap. Measure one round trip to the replica in isolation; 400 trips at roughly 3 ms of network plus 0.2 ms of execution is about 1.3 s on top of a 55 ms baseline, which matches. If the multiplication had fallen short, the N+1 would only be part of the story and you would keep looking.
  4. Batch both lookups. Collect owner_user_ids and resource_ids from the driver query, then issue WHERE tenant_id = $1 AND user_id = ANY($2) for the users, and PostgreSQL's SELECT DISTINCT ON (resource_id) ... WHERE resource_id = ANY($2) ORDER BY resource_id, version DESC for the latest revision, which the UNIQUE (resource_id, version) index serves directly. On an engine without DISTINCT ON, use a lateral join or a row_number window. Three statements per request at any page size.

Follow-up

  • The page size is capped at 200 today. What breaks first if it is raised to 2,000, and is it still this bug?
  • How do you stop the next N+1 from reaching production, given that no individual query is slow and the endpoint's tests pass?

Suggested practice checklist

Built from the rounds and topics Nichols Consulting Engineers candidates report.

Day 1 — Map the Nichols Consulting Engineers loop

  • Write out the reported sequence: Initial Conversation, Technical Assessment, Panel Interview.
  • 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 3 reported rounds, with the weakest marked.

Day 2 — Work Pavement and Asset Management

  • Spend the session on Pavement and Asset Management, which Nichols Consulting Engineers candidates report being tested on.
  • Write one worked example in Pavement and Asset Management and time yourself on it.

Deliverable: One timed worked example in Pavement and Asset Management.

Day 3 — Work Pavement Engineering

  • Spend the session on Pavement Engineering, which Nichols Consulting Engineers candidates report being tested on.
  • Write one worked example in Pavement Engineering and time yourself on it.

Deliverable: One timed worked example in Pavement Engineering.

Day 4 — Work Water Resources Engineering

  • Spend the session on Water Resources Engineering, which Nichols Consulting Engineers candidates report being tested on.
  • Write one worked example in Water Resources Engineering and time yourself on it.

Deliverable: One timed worked example in Water Resources Engineering.

Day 5 — Answer out loud: Full-Stack & GIS Development

  • Answer aloud, timed: How would you optimize a web application that needs to render tens of thousands of interactive road segments on a map?
  • Answer aloud, timed: What is your experience with spatial databases, and how do you write queries using PostGIS or SQL Server Spatial?

Deliverable: Spoken answers to 2 reported Full-Stack & GIS Development question(s), under time.

Day 6 — Answer out loud: Data Engineering & Mathematical Modeling

  • Answer aloud, timed: Describe how you would build a data pipeline to ingest, clean, and store raw sensor data from pavement deflection testing vehicles.
  • Answer aloud, timed: How would you translate a complex civil engineering formula (e.g., pavement deterioration curves or water runoff simulations) into highly optimized code?

Deliverable: Spoken answers to 2 reported Data Engineering & Mathematical Modeling question(s), under time.

Day 7 — Answer out loud: Collaborative & Behavioral

  • Answer aloud, timed: How do you approach gathering software requirements from civil engineers or project managers who may not have a technical software background?
  • Answer aloud, timed: Describe a time when you had to balance a client's request for a custom feature with the long-term maintainability of the core software product.

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

Behavioural preparation

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

What is your experience with spatial databases, and how do you write queries using PostGIS or SQL Server Spati

Medium · Full-Stack & GIS Development

What is your experience with spatial databases, and how do you write queries using PostGIS or SQL Server Spatial?

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 concurrency and resource management when running heavy calculation models on the server?

Medium · Data Engineering & Mathematical Modeling

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 approach gathering software requirements from civil engineers or project managers who may not have

Medium · Collaborative & Behavioral

How do you approach gathering software requirements from civil engineers or project managers who may not have a technical software background?

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 time when you had to balance a client's request for a custom feature with the long-term maintainabi

Medium · Collaborative & Behavioral

Describe a time when you had to balance a client's request for a custom feature with the long-term maintainability of the core software product.

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 situations where a calculation model produces unexpected results, and you must debug the iss

Medium · Collaborative & Behavioral

How do you handle situations where a calculation model produces unexpected results, and you must debug the issue alongside domain experts?

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 project where you had to learn a new domain or industry-specific concept quickly to write effe

Medium · Collaborative & Behavioral

Tell me about a project where you had to learn a new domain or industry-specific concept quickly to write effective software.

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 prioritize your tasks when working on multiple client-facing projects with tight deadlines?

Medium · Collaborative & Behavioral

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?