cswork / libraryOpen practice workspace

Interview guides · University Of Miami

University Of Miami Software Engineer Interview Guide

University Of Miami Software Engineer interview guide: reported rounds, questions and how candidates describe the process.

The 60-second brief

A Software Engineer at the University of Miami plays a critical role in bridging the gap between cutting-edge academic research, healthcare delivery, and enterprise-level educational technology. Unlike typical corporate roles, software engineering at this institution spans a highly diverse technical landscape. You could be embedded within the Center for Computational Science (CCS)—now known as the Institute for Data Science and Computing (IDSC)—working on advanced semantic-enabled search systems, or you might support central IT, building and maintaining critical database interfaces that connect multiple legacy vendor systems. Because the University of Miami is both a premier research institution and a major healthcare provider (UHealth), the applications you build and maintain have a direct impact on student success, breakthrough scientific discoveries, and clinical operations.

This guide is scoped to a Software Engineer candidate at University Of Miami.

Focus areas

  • Software Engineering (General)
  • Semantic Search
  • Search Systems

The University Of Miami interview process

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

Initial Screening

Conducted by HR or a non-technical coordinator to verify background, discuss salary, and assess communication skills.

What to demonstrate

  • Conducted by HR or a non-technical coordinator to verify background, discuss salary, and assess communication skills
  • 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 Conversations

Phone or video interview with senior developers focusing on past projects and specific technical skills.

What to demonstrate

  • Phone or video interview with senior developers focusing on past projects and specific technical skills
  • Depth in Software Engineering (General)

How to prepare

  • Answer aloud and timed: Explain your familiarity with web services, APIs, and the specific technologies mentioned in our department's job description.
  • Answer aloud and timed: How would you approach designing a semantic-enabled search system or working with unstructured research data?

Team Meeting

Panel interview with multiple team members, senior managers, or academic leaders to evaluate fit.

What to demonstrate

  • Panel interview with multiple team members, senior managers, or academic leaders to evaluate fit
  • Depth in Software Engineering (General)

How to prepare

  • Answer aloud and timed: What is your process for debugging a slow database query in a production environment?
  • Answer aloud and timed: Why do you want to work as a Software Engineer at the University of Miami?

Practical Test (Optional)

Some departments may include a coding exercise or practical test alongside technical discussions.

What to demonstrate

  • Some departments may include a coding exercise or practical test alongside technical discussions
  • Depth in Software Engineering (General)

How to prepare

  • Answer aloud and timed: Tell me about a time you had to learn a new technology or framework quickly to complete a project. What was your approach?
  • Answer aloud and timed: Describe a situation where you had to explain a complex technical concept to a non-technical stakeholder, such as a faculty member or administrative director.

Where candidates lose points

Align with the Job Description

Ensure you can speak confidently about every technology mentioned in the specific job posting. Interviewers frequently structure their questions directly around the listed requirements.

Emphasize Your Initiative

If you lack experience with a specific tool or framework, explain how you plan to learn it. Showing that you have already researched the technology before the interview demonstrates valuable proactivity.

Prepare for Non-Technical Interviewers

You may be interviewed by a department chair, a Dean, or an administrative manager. Practice explaining your technical achievements in simple, high-impact terms that highlight business or academic value.

Be Ready for Personality Questions

Do not neglect behavioral preparation. Be ready to discuss how you handle stress, resolve team conflicts, and stay motivated when working on long-term projects.

Questions & practice

How would you approach designing a semantic-enabled search system or working with unstructured research data?

Medium · Technical & System Integration

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?

Archive a resource graph without breaking live references or recursing

Medium · graph traversal · topological order · tenant isolation

Resources reference other resources within a tenant; for the largest tenant the reference table holds up to 2,000,000 nodes and 8,000,000 edges. Archiving a resource must archive everything reachable from it that nothing outside the set still references, refuse when a live external referrer exists, and terminate when references form cycles, which they legitimately do. Produce the archive order and the refusal list, targeting O(V+E). Say what stops the traversal crossing a tenant boundary, and why recursion is the wrong control structure at this size.

Approach

  1. Load the subgraph with the tenant predicate on both endpoints of the edge, not only on the side you started from. Scoping the left table alone is the classic cross-tenant leak: one mis-entered edge then pulls another tenant's resources into the traversal and, worse, into the archive.
  2. Traverse iteratively with an explicit stack. A 2,000,000-node graph can hold a chain deep enough to exhaust a native stack in the low tens of thousands of frames, and that failure is a process crash rather than an error you can return.
  3. Treat cycles as data rather than corruption: compute strongly connected components with Tarjan in O(V+E) using its own explicit stack, then condense. The condensation is a DAG, so a topological order over it gives the archive order, and every member of a component archives in one transaction because no order within a cycle is valid.
  4. Decide refusals with reverse edges. A candidate is archivable only if every in-edge originates inside the candidate set, so build the transpose or count in-degrees restricted to the visited set, and emit each blocked resource with the id of the external referrer, which is the only part of the answer an operator can act on.

Follow-up

  • The graph is read in one query and the archive writes a minute later. What can change in between, and how do you make the write safe?
  • The candidate set is 400,000 resources. Is that one transaction, and if not, what does a half-finished archive look like to a reader?

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?

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?

Find version gaps and relay lag with window functions

Medium · window functions · event tables · frame semantics

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

Approach

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

Follow-up

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

Explain your familiarity with web services, APIs, and the specific technologies mentioned in our department's

Medium · Technical & System Integration

Explain your familiarity with web services, APIs, and the specific technologies mentioned in our department's job description.

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 recent project you completed. What was your individual contribution, and how did you choose

Medium · Problem-Solving & Project Discussion

Walk us through a recent project you completed. What was your individual contribution, and how did you choose the technology stack?

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?

If we gave you a project idea with high-level requirements, how would you structure the development lifecycle

Medium · Problem-Solving & Project Discussion

If we gave you a project idea with high-level requirements, how would you structure the development lifecycle from scratch?

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 process for debugging a slow database query in a production environment?

Medium · Technical & System Integration

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 University Of Miami candidates report.

Day 1 — Map the University Of Miami loop

  • Write out the reported sequence: Initial Screening, Technical Conversations, Team Meeting, Practical Test (Optional).
  • 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 (General)

  • Spend the session on Software Engineering (General), which University Of Miami 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 Semantic Search

  • Spend the session on Semantic Search, which University Of Miami candidates report being tested on.
  • Write one worked example in Semantic Search and time yourself on it.

Deliverable: One timed worked example in Semantic Search.

Day 4 — Work Search Systems

  • Spend the session on Search Systems, which University Of Miami candidates report being tested on.
  • Write one worked example in Search Systems and time yourself on it.

Deliverable: One timed worked example in Search Systems.

Day 5 — Answer out loud: Technical & System Integration

  • Answer aloud, timed: Describe your experience working with multiple databases and integrating heterogeneous systems.
  • Answer aloud, timed: How do you handle data synchronization when working with different programming languages and configured vendor products?

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

Day 6 — Answer out loud: Behavioral & Mission Alignment

  • Answer aloud, timed: Why do you want to work as a Software Engineer at the University of Miami?
  • Answer aloud, timed: Tell me about a time you had to learn a new technology or framework quickly to complete a project. What was your approach?

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

Day 7 — Answer out loud: Problem-Solving & Project Discussion

  • Answer aloud, timed: Walk us through a recent project you completed. What was your individual contribution, and how did you choose the technology stack?
  • Answer aloud, timed: If we gave you a project idea with high-level requirements, how would you structure the development lifecycle from scratch?

Deliverable: Spoken answers to 2 reported Problem-Solving & Project Discussion question(s), under time.

Behavioural preparation

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

Describe your experience working with multiple databases and integrating heterogeneous systems.

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

How do you handle data synchronization when working with different programming languages and configured vendor

Medium · Technical & System Integration

How do you handle data synchronization when working with different programming languages and configured vendor products?

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 do you want to work as a Software Engineer at the University of Miami?

Medium · Behavioral & Mission Alignment

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 learn a new technology or framework quickly to complete a project. What was yo

Medium · Behavioral & Mission Alignment

Tell me about a time you had to learn a new technology or framework quickly to complete a project. What was your approach?

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 explain a complex technical concept to a non-technical stakeholder, such

Medium · Behavioral & Mission Alignment

Describe a situation where you had to explain a complex technical concept to a non-technical stakeholder, such as a faculty member or administrative director.

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 supporting multiple departments with competing demands?

Medium · Behavioral & Mission Alignment

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?

Share an experience where you identified a gap in your technical knowledge and took the initiative to master i

Medium · Behavioral & Mission Alignment

Share an experience where you identified a gap in your technical knowledge and took the initiative to master it before starting a task.

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

How do you handle a situation where a configured vendor product does not natively support a feature that our u

Medium · Problem-Solving & Project Discussion

How do you handle a situation where a configured vendor product does not natively support a feature that our users desperately need?

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?