cswork / libraryOpen practice workspace

Interview guides · Quinstreet

Quinstreet Software Engineer Interview Guide

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

The 60-second brief

A Software Engineer at QuinStreet plays a critical role in powering decentralized online marketplaces that match high-intent searchers and consumers with leading brands. Operating within one of the nation's largest media networks, you will build and optimize AI-driven matching technologies, segmentation engines, and real-time bidding systems. Your engineering decisions directly impact how billions of dollars of online media are managed and optimized, making your code vital to the company's core performance marketing business. In this role, you will work on complex, high-scale web applications where performance, reliability, and low latency are paramount.

This guide is scoped to a Software Engineer candidate at Quinstreet.

Focus areas

  • JavaScript
  • HTML
  • CSS

The Quinstreet interview process

Quinstreet 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 discuss your background and fit for the role.

What to demonstrate

  • Initial call to discuss your background and fit for the role
  • Depth in JavaScript

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 Screening

May involve an online coding assessment or a technical phone interview.

What to demonstrate

  • May involve an online coding assessment or a technical phone interview
  • Depth in JavaScript

How to prepare

  • Answer aloud and timed: Describe the lifecycle of a thread in Java and explain how you would handle thread synchronization in a multi-threaded environment.
  • Answer aloud and timed: Explain the lifecycle of a Java Servlet and how it manages concurrent requests.

Core Technical Rounds

Multiple interviews focusing on core programming, system design, and deep dives.

What to demonstrate

  • Multiple interviews focusing on core programming, system design, and deep dives
  • Depth in JavaScript

How to prepare

  • Answer aloud and timed: How would you fetch and parse data from an XML payload within a legacy PHP or Java application?
  • Answer aloud and timed: Write the exact syntax for a CSS media query from memory and explain how media queries execute differently for mobile versus desktop users.

Discussion with Senior Director

Final discussions with a senior director or VP regarding your fit.

What to demonstrate

  • Final discussions with a senior director or VP regarding your fit
  • Depth in JavaScript

How to prepare

  • Answer aloud and timed: Explain the difference between React props and state, and describe how Vue.js handles two-way data binding.
  • Answer aloud and timed: How does cross-site scripting (XSS) occur in modern web applications, and what specific mitigation strategies would you implement on both the frontend and backend?

Behavioral and HR Wrap-up

Final interview focusing on behavioral aspects and HR discussions.

What to demonstrate

  • Final interview focusing on behavioral aspects and HR discussions
  • Depth in JavaScript

How to prepare

  • Prepare three examples from your own work, each with a decision you made and an outcome you can quantify.
  • Re-read the description of the behavioral and hr wrap-up above and write down what you would ask to confirm before it.

Where candidates lose points

Understand the Business Model

QuinStreet operates decentralized marketplaces. Showing that you understand lead generation, pay-per-click bidding, and matching algorithms will instantly make you a more compelling candidate.

Write Syntactically Correct Code

During whiteboard and coding exercises, pay close attention to syntax, variable naming, and error handling. Interviewers expect production-quality code, even when written under time constraints.

Avoid relying too heavily on modern framework abstractions during your coding rounds

Interviewers will often ask you to solve problems using vanilla JavaScript or core Java libraries to test your fundamental understanding of the language.

Questions & practice

Describe the lifecycle of a thread in Java and explain how you would handle thread synchronization in a multi-

Medium · Core Java & Backend Systems

Describe the lifecycle of a thread in Java and explain how you would handle thread synchronization in a multi-threaded environment.

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?

Explain the lifecycle of a Java Servlet and how it manages concurrent requests.

Medium · Core Java & Backend Systems

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?

Write the exact syntax for a CSS media query from memory and explain how media queries execute differently for

Medium · Frontend & Web Technologies

Write the exact syntax for a CSS media query from memory and explain how media queries execute differently for mobile versus desktop users.

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?

A programmer wrote a class MySet that extends List. Another programmer used it thinking it was a set, but

Medium · Object-Oriented Design & Problem Solving

A programmer wrote a class MySet that extends List. Another programmer used it thinking it was a set, but a third programmer used it as a list. How would you refactor this hierarchy to support both list and set features cleanly, and which behavior would you make the default?

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?

Explain how you would implement the Factory pattern to instantiate different payment processing modules, and h

Medium · Object-Oriented Design & Problem Solving

Explain how you would implement the Factory pattern to instantiate different payment processing modules, and how you would transition this to use Spring Dependency Injection.

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?

How would you implement the Observer pattern to handle real-time notifications when a bidding price changes?

Medium · Object-Oriented Design & 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?

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?

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?

What is the difference between a List and a Set in Java, and when would you use one over the other?

Medium · Core Java & Backend Systems

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?

Can an abstract method or an interface be declared as final? Explain why or why not.

Medium · Core Java & Backend Systems

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 fetch and parse data from an XML payload within a legacy PHP or Java application?

Medium · Core Java & Backend Systems

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 difference between React props and state, and describe how Vue.js handles two-way data binding.

Medium · Frontend & Web Technologies

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 does cross-site scripting (XSS) occur in modern web applications, and what specific mitigation strategies

Medium · Frontend & Web Technologies

How does cross-site scripting (XSS) occur in modern web applications, and what specific mitigation strategies would you implement on both the frontend and backend?

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 does client-side tracking, such as Google Analytics, capture and transmit user interaction data back to a

Medium · Frontend & Web Technologies

How does client-side tracking, such as Google Analytics, capture and transmit user interaction data back to a server?

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?

Design an efficient algorithm to compare two massive text files containing names and output all names present

Medium · Object-Oriented Design & Problem Solving

Design an efficient algorithm to compare two massive text files containing names and output all names present in the first file but missing from the second.

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 would you architect the control software for a bank of physical elevators? What state variables, schedulin

Medium · System Design & Architecture

How would you architect the control software for a bank of physical elevators? What state variables, scheduling algorithms, and hardware constraints must you account for?

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?

Design a database schema to support a real-time pay-per-click (PPC) advertising platform where customers bid f

Medium · System Design & Architecture

Design a database schema to support a real-time pay-per-click (PPC) advertising platform where customers bid for ad positions.

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 would you structure a system to handle end-to-end testing for a complex web application containing multipl

Medium · System Design & Architecture

How would you structure a system to handle end-to-end testing for a complex web application containing multiple third-party API integrations?

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?

Exports duplicate a row range about once a week

Hard · leases · clock skew · idempotency

Roughly once a week an export writes a file containing a duplicated range of rows. The affected job_run rows show attempt = 1, status = succeeded, one started_at, and a lease_owner naming a different host from the one whose logs show the job starting. Leases last 30 seconds and are heartbeated every 10 from inside the handler; lease_expires_at is computed on the worker and compared against the database's now(). Find the mechanism, and give a fix that holds even if you cannot fix the clocks.

Approach

  1. Start from the fact that eliminates the obvious answer. attempt = 1 means no retry was recorded, so this is not a re-run after failure; two workers ran the same row concurrently and the takeover path never touched the counter. lease_owner naming a host other than the one that started the job is the same statement from the other side.
  2. Enumerate the mechanisms that cause a premature takeover, then find the signal that separates them. Either the lease genuinely expired because the heartbeat did not fire, which is what happens when the heartbeat runs on the handler's own thread and the handler makes a long blocking call, or it only appeared expired because two clocks disagree, since lease_expires_at is written from the worker's clock and evaluated against the database's. The discriminator is the distribution: incidents clustered on the longest exports indict the heartbeat, incidents clustered on one host indict skew. Measure both, and measure each host's offset against the database directly.
  3. Read the reclaim query precisely. In PostgreSQL now() is transaction start time, not statement time, so a reclaimer holding a long transaction compares against an older timestamp than expected; clock_timestamp() is the statement-time function. This is worth ruling in or out before you redesign anything, because it changes which rows look expired.
  4. Remove the second clock rather than trying to synchronise it. Issue and extend the lease in the database, with lease_expires_at = now() + interval '30 seconds' in both the claim and the heartbeat, so exactly one clock is ever compared and worker skew stops mattering to this predicate.

Follow-up

  • The displaced worker has already streamed half the file to object storage. What makes that side effect safe to repeat?
  • You now count takeovers. What alert fires on that counter, and at what threshold?

Suggested practice checklist

Built from the rounds and topics Quinstreet candidates report.

Day 1 — Map the Quinstreet loop

  • Write out the reported sequence: HR Screening Call, Technical Screening, Core Technical Rounds, Discussion with Senior Director, Behavioral and HR Wrap-up.
  • 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 JavaScript

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

Deliverable: One timed worked example in JavaScript.

Day 3 — Work HTML

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

Deliverable: One timed worked example in HTML.

Day 4 — Work CSS

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

Deliverable: One timed worked example in CSS.

Day 5 — Answer out loud: Core Java & Backend Systems

  • Answer aloud, timed: What is the difference between a List and a Set in Java, and when would you use one over the other?
  • Answer aloud, timed: Can an abstract method or an interface be declared as final? Explain why or why not.

Deliverable: Spoken answers to 2 reported Core Java & Backend Systems question(s), under time.

Day 6 — Answer out loud: Frontend & Web Technologies

  • Answer aloud, timed: Write the exact syntax for a CSS media query from memory and explain how media queries execute differently for mobile versus desktop users.
  • Answer aloud, timed: Explain the difference between React props and state, and describe how Vue.js handles two-way data binding.

Deliverable: Spoken answers to 2 reported Frontend & Web Technologies question(s), under time.

Day 7 — Answer out loud: Object-Oriented Design & Problem Solving

  • Answer aloud, timed: A programmer wrote a class MySet that extends List. Another programmer used it thinking it was a set, but a third programmer used it as a list. How would you refactor this hierarchy to support both list and set features cleanly, and which behavior would you make the default?
  • Answer aloud, timed: Explain how you would implement the Factory pattern to instantiate different payment processing modules, and how you would transition this to use Spring Dependency Injection.

Deliverable: Spoken answers to 2 reported Object-Oriented Design & Problem Solving question(s), under time.

Behavioural preparation

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

Unblock an engineer without taking the keyboard

Easy · mentoring · leases · at-least-once

A teammate has spent two days on a job handler that occasionally writes duplicate rows. They are certain the queue is delivering twice by mistake. You suspect a lease expiring under a slow handler, so the job is running concurrently with itself. Describe how you have unblocked someone in this position: what you asked before offering a hypothesis, what you showed them rather than told them, and what you left them owning. Then say what you would do if their theory turned out to be the right one.

Approach

  1. Ask before diagnosing, and ask for things answerable from data they already have: the attempt count on the job rows that produced duplicates, the handler's observed duration against its lease expiry, and whether the duplicate rows share a natural key that a unique constraint could have caught.
  2. Teach the shape rather than the answer. A lease cannot distinguish a dead worker from a slow one, so a handler that outruns its lease is running twice by design, and deploys deliver the other half by killing handlers mid-run on every rollout. Both of their candidate theories produce identical duplicate rows, which is why the evidence has to come from timings rather than from argument.
  3. Hand over a checklist they execute: a natural key on every write the handler performs so the second copy collides rather than appends, the record of intent written before any external effect, a lease heartbeat while running, and the metric that shows it working.
  4. Keep ownership with them deliberately. Pair on the first write, then step back; if you finish it yourself you have closed one ticket and left the same person stuck on the next redelivery.

Follow-up

  • How would you distinguish a genuine double-delivery from a lease expiry using only the data already stored?
  • Their handler calls an external endpoint before recording that it did. What do you tell them to change first?

Narrate an outage you owned from page to postmortem

Hard · incident response · blast radius · postmortems

Pick an incident you personally drove, ideally one where writes were affected rather than reads. In six to eight minutes: state the symptom as it first appeared on a dashboard, the blast radius you established before you knew the cause, the mitigation you applied and when, the mechanism you eventually proved, and the follow-up that would prevent a repeat. Bring numbers: error rate, tenants affected, minutes to mitigate, minutes to resolve. If you cannot name what you measured, choose a different incident.

Approach

  1. Open on the signal rather than the cause: which metric at which percentile moved, on which service, at what time, so the listener follows the same evidence you had rather than a conclusion you already reached.
  2. Separate mitigation from diagnosis out loud. State what you did to stop the bleeding (flag off, shed traffic, drain a lease, roll back a deploy) and say plainly that you did it before the mechanism was known, because those are two jobs with different deadlines.
  3. Establish blast radius in countable terms: how many tenants, how many writes, and crucially whether the effect was loss or only delay. An append-only revision table or a pending outbox row means the change survived and the projection was merely behind, which is a repair rather than a data-loss incident.
  4. Prove the mechanism instead of asserting it. Name the trace span that grew, the plan that flipped to a sequential scan, the lease that expired, plus one alternative you ruled out and the signal that stayed flat while you ruled it out.

Follow-up

  • What would you do differently in the first five minutes, given the same dashboard and no more information?
  • Which follow-up action did you deliberately not take, and why was dropping it the right call?

Turn a code review disagreement into a decision

Easy · code review · optimistic concurrency · communication

A colleague's change updates a row with UPDATE resource SET version = version + 1 WHERE resource_id = $1 AND version = $2 and treats an affected-row count of zero as a successful no-op. You read that as a silently lost update; they think returning 200 is friendlier to clients than returning a conflict. Describe how you have handled a review disagreement of this shape: what goes in the comment, when you leave the thread, and who decides. Then write the comment you would leave here, in under 80 words.

Approach

  1. Sort the disagreement before writing anything. A silently discarded write is a correctness claim about data; the choice between 409 and 412 is taste. Only the first justifies blocking a merge, and saying which one you are doing is most of the value of the comment.
  2. Make the claim reproducible in the comment itself with an interleaving rather than a principle: A reads version 7, B reads version 7, B commits version 8, A's predicate matches zero rows, A is told it succeeded and A's edit is gone.
  3. Offer the alternative with its cost attached: return 409 carrying the current version and the revision that won, so the client can re-read and re-apply. Note that automatic retry is not the fix, because a retry re-reads the winner's state and reapplies an intent formed against data that no longer exists.
  4. Apply an escalation rule you can state: two round trips on the thread, then a call, and the service's owner decides rather than the reviewer. A reviewer who cannot be overruled is a bottleneck with extra steps.

Follow-up

  • Where would you put the test that fails if someone reintroduces the swallowed zero rowcount?
  • The author says clients cannot handle a 409. How do you check whether that is true?