Doran Jones Software Engineer Interview Guide

The 60-second brief

As a Software Engineer at Doran Jones, you will play a critical role in designing, developing, and delivering high-quality software solutions for some of the world’s leading financial institutions, hedge funds, and enterprise clients. Because Doran Jones operates as a specialized technology consulting and services firm, our engineers do not work in a vacuum. Instead, you will build and optimize systems that directly impact our clients' core business operations, ranging from high-frequency trading infrastructure to complex enterprise customer relationship management (CRM) platforms. This role is highly dynamic and requires a unique blend of deep technical expertise and strong professional consulting skills.

This guide is scoped to a Software Engineer candidate at Doran Jones.

Focus areas

• Multithreading
• Microsoft Dynamics CRM Development
• Python

The Doran Jones interview process

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

Recruiter Screening

Initial discussion about your background, career goals, and salary expectations.

What to demonstrate

• Initial discussion about your background, career goals, and salary expectations
• Depth in Multithreading

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 Assessment

May include a take-home coding challenge or a live technical screening.

What to demonstrate

• May include a take-home coding challenge or a live technical screening
• Depth in Multithreading

How to prepare

• Answer aloud and timed: Describe how you would implement a thread-safe queue from scratch.
• Answer aloud and timed: What is the difference between optimistic and pessimistic locking?

Technical Interviews

Comprehensive interviews focusing on core engineering fundamentals like multithreading and system design.

What to demonstrate

• Comprehensive interviews focusing on core engineering fundamentals like multithreading and system design
• Depth in Multithreading

How to prepare

• Answer aloud and timed: How does the Global Interpreter Lock (GIL) impact multi-threading in Python?
• Answer aloud and timed: Given an array of integers, write a function to find the contiguous subarray with the largest sum.

Behavioral Fit Assessment

Final round assessing your behavioral fit and readiness for client engagement.

What to demonstrate

• Final round assessing your behavioral fit and readiness for client engagement
• Depth in Multithreading

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 fit assessment above and write down what you would ask to confirm before it.

Where candidates lose points

Over-communicate your thought process

During live coding sessions, do not code in silence. Explain what you are doing, why you are choosing a specific data structure, and what trade-offs you are making.

Brush up on concurrency basics

Be prepared to discuss multithreading concepts in detail, as this is a frequent focus area for our engineering teams.

Align on salary expectations early

Ensure your compensation requirements are clearly discussed during the initial recruiter screening to avoid any alignment issues late in the process.

Questions & practice

Explain the difference between a process and a thread.

Medium · Multithreading & Concurrency

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?

Describe how you would implement a thread-safe queue from scratch.

Medium · Multithreading & Concurrency

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?

What is the difference between optimistic and pessimistic locking?

Medium · Multithreading & Concurrency

Approach

1. Say what the runtime actually does before reasoning about the code.
2. Name what is shared across threads and what owns each piece of state.
3. Identify the window where an invariant is briefly untrue.
4. Distinguish a value from a reference to it, and say which one you handed out.

Follow-up

• What happens if two callers reach this at the same time?
• Where could this allocate more than you expect?

How does the Global Interpreter Lock (GIL) impact multi-threading in Python?

Medium · Multithreading & Concurrency

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?

Given an array of integers, write a function to find the contiguous subarray with the largest sum.

Medium · Algorithmic 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?

How would you reverse a linked list iteratively and recursively?

Medium · Algorithmic 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?

Walk me through how you would optimize a search algorithm operating on a massive, unsorted dataset.

Medium · Algorithmic 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?

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?

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?

Explain how you would design an algorithm to detect cycles in a directed graph.

Medium · Algorithmic Problem Solving

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?

Describe your approach to building custom plugins and workflow activities in a CRM environment.

Medium · Domain & Platform Integration

Approach

1. Say who the caller is and what they do when the call fails halfway.
2. Define the identity of a request so a retry cannot double-apply it.
3. Separate accepted, pending, failed and confirmed; they are different facts.
4. Design the error taxonomy before the success shape; callers branch on it.

Follow-up

• What happens if the caller retries after a timeout?
• How does a client discover it is on an old version of this contract?

How do you design and secure RESTful APIs that need to handle sensitive financial data?

Medium · Domain & Platform Integration

Approach

1. Fix the scope first: who calls this, how often, and what they do when it fails.
2. Name the read and write paths separately; they rarely have the same bottleneck.
3. Choose a partition key and say what query it makes expensive.
4. State the consistency you need, and where you are willing to be stale.

Follow-up

• What breaks first when traffic grows ten times?
• How does this behave when that dependency is down for an hour?

Explain how dependency injection works and how you have utilized it in your previous projects.

Medium · Domain & Platform Integration

Approach

1. Say who the caller is and what they do when the call fails halfway.
2. Define the identity of a request so a retry cannot double-apply it.
3. Separate accepted, pending, failed and confirmed; they are different facts.
4. Design the error taxonomy before the success shape; callers branch on it.

Follow-up

• What happens if the caller retries after a timeout?
• How does a client discover it is on an old version of this contract?

How do you prevent deadlocks in a multi-threaded environment?

Medium · Multithreading & Concurrency

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?

Tell me about a time you had to debug a critical production issue under tight time constraints.

Medium · Behavioral & Client Management

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 Doran Jones candidates report.

Day 1 — Map the Doran Jones loop

• Write out the reported sequence: Recruiter Screening, Technical Assessment, Technical Interviews, Behavioral Fit Assessment.
• 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 Multithreading

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

Deliverable: One timed worked example in Multithreading.

Day 3 — Work Microsoft Dynamics CRM Development

• Spend the session on Microsoft Dynamics CRM Development, which Doran Jones candidates report being tested on.
• Write one worked example in Microsoft Dynamics CRM Development and time yourself on it.

Deliverable: One timed worked example in Microsoft Dynamics CRM Development.

Day 4 — Work Python

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

Deliverable: One timed worked example in Python.

Day 5 — Answer out loud: Multithreading & Concurrency

• Answer aloud, timed: Explain the difference between a process and a thread.
• Answer aloud, timed: How do you prevent deadlocks in a multi-threaded environment?

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

Day 6 — Answer out loud: Algorithmic Problem Solving

• Answer aloud, timed: Given an array of integers, write a function to find the contiguous subarray with the largest sum.
• Answer aloud, timed: How would you reverse a linked list iteratively and recursively?

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

Day 7 — Answer out loud: Domain & Platform Integration

• Answer aloud, timed: How do you handle high-volume data synchronization between Microsoft Dynamics CRM and external SQL databases?
• Answer aloud, timed: Describe your approach to building custom plugins and workflow activities in a CRM environment.

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

Behavioural preparation

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

How do you handle high-volume data synchronization between Microsoft Dynamics CRM and external SQL databases?

Medium · Domain & Platform Integration

Approach

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

Follow-up

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

Describe a time when you had to deal with a sudden change in project requirements from a client. How did you a

Medium · Behavioral & Client Management

Describe a time when you had to deal with a sudden change in project requirements from a client. How did you adapt?

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 client's internal technical team disagrees with your architectural recom

Medium · Behavioral & Client Management

How do you handle a situation where a client's internal technical team disagrees with your architectural recommendations?

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 manage your time and deliverables when working across multiple client initiatives?

Medium · Behavioral & Client Management

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?