cswork / libraryOpen practice workspace

Interview guides · Robert Half

Robert Half Software Engineer Interview Guide

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

The 60-second brief

As a Software Engineer working with or through Robert Half, you occupy a vital position at the intersection of enterprise technology, modern application development, and strategic client placements. This role directly impacts how organizations scale their technical capabilities, whether you are building cross-platform mobile solutions with.NET MAUI, architecting AI-driven workflows and agent-based automation using Python and LLMs, or leading enterprise development teams as a technical lead. Your code and system designs directly drive operational efficiency, user experience, and long-term business growth for diverse corporate partners. The scope of this role ranges from hands-on full-stack development—utilizing stacks such as Java, C#,.NET, React, and MySQL—to specialized engineering in cloud environments and enterprise platforms like Salesforce.

This guide is scoped to a Software Engineer candidate at Robert Half.

Focus areas

  • Database Concepts (SQL vs NoSQL)
  • Behavioral Interviewing
  • RAG (Retrieval-Augmented Generation)

The Robert Half interview process

Robert Half candidates report 2 rounds over 2-4 weeks. The stages below are what candidates describe, not a published process.

Recruiter Screening Call

Initial call to review your background, career objectives, and compensation expectations.

What to demonstrate

  • Initial call to review your background, career objectives, and compensation expectations
  • Depth in Database Concepts (SQL vs NoSQL)

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 Panel Interview

Interview with engineering leads, solutions architects, or client stakeholders involving resume deep dives and technical questions.

What to demonstrate

  • Interview with engineering leads, solutions architects, or client stakeholders involving resume deep dives and technical questions
  • Depth in Database Concepts (SQL vs NoSQL)

How to prepare

  • Answer aloud and timed: Can you explain your hands-on experience with.NET MAUI and cross-platform mobile application deployment for iOS and Android?
  • Answer aloud and timed: How do you optimize database query performance and manage indexes in MySQL?

Where candidates lose points

Know your resume inside and out

Interviewers frequently ask detailed follow-up questions about specific projects, libraries, and architectural choices listed on your CV. Be ready to defend every line you wrote.

Communicate your thought process

During technical and scenario-based questions, talk through your reasoning aloud. Interviewers value how you approach ambiguity and structure solutions just as much as the final answer.

Align with business outcomes

Connect your technical solutions to business value, demonstrating that you understand how code impacts efficiency, user experience, and organizational revenue.

Prepare thoughtful questions

Ask interviewers about team structure, deployment pipelines, technical debt management, and what success looks like in the first ninety days of the role.

Maintain professional flexibility

Approach every conversation with adaptability, recognizing that requirements in fast-paced tech environments can shift quickly.

Questions & practice

How do you handle asynchronous programming and threading in C# and the broader.NET ecosystem?

Medium · Resume Deep-Dive & Theoretical Questions

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?

Track a rolling failure rate per destination for circuit decisions

Easy · sliding window · ring buffer · circuit breaker

The egress service delivers about 1,500 webhooks per second across roughly 40,000 destinations, each call bounded by a 10 second timeout. Maintain, per destination, the failure rate over the trailing 60 seconds so a caller can ask before dispatch whether the circuit should open. Attempts arrive as (destination_id, finished_at_ms, outcome). Requirement: amortised O(1) per attempt, with total memory bounded by the destination count rather than by traffic. Give the structure, its exact memory, and the rule that stops a destination with three attempts from opening a circuit.

Approach

  1. Name the exact-deque version and then reject it as the default. Holding timestamps and advancing a tail pointer past anything older than now minus 60 seconds is a correct two-pointer window at amortised O(1) per attempt, but its memory tracks in-window traffic, so one destination in a retry storm holds hundreds of thousands of entries while thousands of quiet destinations hold none.
  2. Use a ring of 60 one-second buckets per destination, each bucket a pair of counters for attempts and failures. On an attempt, advance the ring by the elapsed whole seconds, zeroing at most min(elapsed, 60) buckets, then increment the head. That is amortised O(1) with a fixed footprint per destination.
  3. State the footprint: 60 buckets times two 4-byte counters is 480 bytes of payload per destination, so 40,000 destinations is roughly 20 to 25 MB with per-entry overhead, bounded by the catalogue rather than by the rate. The cost is granularity, since the oldest bucket ages out in whole seconds, which is far tighter than the decision needs.
  4. Require a minimum sample before the circuit may open. A destination with three attempts and three failures reads as 100 percent and is not evidence; a floor of roughly 20 attempts in the window makes the ratio meaningful, and below that floor use a run of consecutive failures as the trigger instead.

Follow-up

  • The fleet is 30 instances and each sees roughly a thirtieth of a destination's traffic. Where does the rate actually live, and what does a per-instance answer get wrong?
  • A destination answers in 9.5 seconds and succeeds. It is not failing but it is consuming your per-destination concurrency. What signal should open the circuit here?

Collapse a redelivered event batch into per-aggregate high-water marks

Easy · hashing · at-least-once · aggregation

You drain a batch of up to 5,000,000 events, each (aggregate_id BIGINT, aggregate_version INT, event_type, payload). The log guarantees order within one aggregate only; the batch merges 64 partitions, and a relay failover has redelivered a range, so an older version for an aggregate can appear after a newer one. Given a map of last_applied_version per aggregate, produce the events worth applying, at most one per (aggregate_id, version), plus the count discarded. Target O(n) time. State the memory for 2,000,000 distinct aggregates and what you do when it does not fit.

Approach

  1. One pass, one hash map from aggregate_id to the highest version kept, and a discard counter. An event whose version is at or below last_applied_version for its aggregate is dropped without further work, which is the whole reason the event carries its version rather than a delta. O(n) expected time, O(d) space in distinct aggregates.
  2. Keep the maximum, never the last occurrence. The redelivered range means the final appearance of an aggregate in the batch can be an older version than one seen earlier in the same batch, so last-wins applies stale state over newer state and the projection regresses with no error anywhere.
  3. Cost the memory instead of calling it large: an 8-byte key plus a 4-byte version is 12 bytes of payload, and an open-addressed table held at a 0.7 load factor costs roughly 17 bytes per entry before per-slot metadata, so 2,000,000 aggregates is tens of megabytes in a native layout and several times that in a runtime that boxes both key and value.
  4. If the distinct set exceeds memory, partition on hash(aggregate_id) mod P and reduce each partition independently. Every event for one aggregate hashes to the same partition, so the per-partition result is exact and the merge is concatenation rather than a second reduction.

Follow-up

  • The payload is a patch rather than a snapshot, so applying only the highest version loses the intermediate changes. What changes in your reduction?
  • How do you detect that version 7 arrived while version 6 was never delivered, and what should the consumer do about the gap?

What is the difference between NoSQL and SQL databases, and when would you choose one over the other for a new

Medium · Technical & Core Domain Questions

What is the difference between NoSQL and SQL databases, and when would you choose one over the other for a new project?

Approach

  1. Name the grain you start from and join outward from it.
  2. Check whether any join is one-to-many before aggregating, or the sums inflate.
  3. Say which index the query would use, and what makes it unusable.
  4. Handle the rows that do not match: that is usually the actual question.

Follow-up

  • How does the query change if that join becomes one-to-many?
  • What happens to this when the table is ten times larger?

How do you optimize database query performance and manage indexes in MySQL?

Medium · Technical & Core Domain Questions

Approach

  1. Name the grain you start from and join outward from it.
  2. Check whether any join is one-to-many before aggregating, or the sums inflate.
  3. Say which index the query would use, and what makes it unusable.
  4. Handle the rows that do not match: that is usually the actual question.

Follow-up

  • How does the query change if that join becomes one-to-many?
  • What happens to this when the table is ten times larger?

How do you manage component lifecycle and state management in React?

Medium · Technical & Core Domain Questions

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 you explain your hands-on experience with.NET MAUI and cross-platform mobile application deployment for iO

Medium · Technical & Core Domain Questions

Can you explain your hands-on experience with.NET MAUI and cross-platform mobile application deployment for iOS and Android?

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?

Walk me through every architectural decision and technology choice on this specific project listed on your res

Medium · Resume Deep-Dive & Theoretical Questions

Walk me through every architectural decision and technology choice on this specific project listed on your resume.

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?

What challenges have you faced while deploying applications in a Linux and Java Tomcat environment, and how di

Medium · Resume Deep-Dive & Theoretical Questions

What challenges have you faced while deploying applications in a Linux and Java Tomcat environment, and how did you resolve them?

Approach

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

Follow-up

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

How do you ensure data integrity and security compliance within enterprise CRM or ERP platforms?

Medium · Resume Deep-Dive & Theoretical Questions

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 a project where you collaborated with distributed or offshore team members.

Medium · Behavioral & Leadership Questions

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?

Walk me through your step-by-step process for performing root-cause analysis on a recurring system crash.

Medium · Problem-Solving & Scenario-Based Questio

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 a client requested an enterprise automation workflow with tight cloud integration, how would you design the

Medium · Problem-Solving & Scenario-Based Questio

If a client requested an enterprise automation workflow with tight cloud integration, how would you design the initial prototype?

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?

Imagine a critical database migration fails halfway through execution; what immediate containment and recovery

Medium · Problem-Solving & Scenario-Based Questio

Imagine a critical database migration fails halfway through execution; what immediate containment and recovery steps do you take?

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 approach troubleshooting a production incident where mobile API response times have suddenly deg

Medium · Problem-Solving & Scenario-Based Questio

How would you approach troubleshooting a production incident where mobile API response times have suddenly degraded across Android devices?

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 Robert Half candidates report.

Day 1 — Map the Robert Half loop

  • Write out the reported sequence: Recruiter Screening Call, Technical 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 2 reported rounds, with the weakest marked.

Day 2 — Work Database Concepts (SQL vs NoSQL)

  • Spend the session on Database Concepts (SQL vs NoSQL), which Robert Half candidates report being tested on.
  • Write one worked example in Database Concepts (SQL vs NoSQL) and time yourself on it.

Deliverable: One timed worked example in Database Concepts (SQL vs NoSQL).

Day 3 — Work Behavioral Interviewing

  • Spend the session on Behavioral Interviewing, which Robert Half candidates report being tested on.
  • Write one worked example in Behavioral Interviewing and time yourself on it.

Deliverable: One timed worked example in Behavioral Interviewing.

Day 4 — Work RAG (Retrieval-Augmented Generation)

  • Spend the session on RAG (Retrieval-Augmented Generation), which Robert Half candidates report being tested on.
  • Write one worked example in RAG (Retrieval-Augmented Generation) and time yourself on it.

Deliverable: One timed worked example in RAG (Retrieval-Augmented Generation).

Day 5 — Answer out loud: Technical & Core Domain Questions

  • Answer aloud, timed: What is the difference between NoSQL and SQL databases, and when would you choose one over the other for a new project?
  • Answer aloud, timed: How do you manage component lifecycle and state management in React?

Deliverable: Spoken answers to 2 reported Technical & Core Domain Questions question(s), under time.

Day 6 — Answer out loud: Resume Deep-Dive & Theoretical Questions

  • Answer aloud, timed: Walk me through every architectural decision and technology choice on this specific project listed on your resume.
  • Answer aloud, timed: How do you handle asynchronous programming and threading in C# and the broader.NET ecosystem?

Deliverable: Spoken answers to 2 reported Resume Deep-Dive & Theoretical Questions question(s), under time.

Day 7 — Answer out loud: Behavioral & Leadership Questions

  • Answer aloud, timed: Describe a situation where you had to lead a technical team through a tight deadline or shifting project requirements.
  • Answer aloud, timed: How do you handle disagreements with product managers or stakeholders regarding technical debt versus new feature development?

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

Behavioural preparation

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

What is your experience integrating LLMs or building agent-based AI workflows using Python?

Medium · Technical & Core Domain Questions

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?

Can you explain a time when you had to refactor legacy code to improve system maintainability and performance?

Medium · Resume Deep-Dive & Theoretical Questions

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 lead a technical team through a tight deadline or shifting project requi

Medium · Behavioral & Leadership Questions

Describe a situation where you had to lead a technical team through a tight deadline or shifting project requirements.

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 disagreements with product managers or stakeholders regarding technical debt versus new feat

Medium · Behavioral & Leadership Questions

How do you handle disagreements with product managers or stakeholders regarding technical debt versus new feature development?

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 when you mentored a junior developer or helped upskill a team member.

Medium · Behavioral & Leadership Questions

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 tasks when managing multiple competing deliverables across backend and frontend layers?

Medium · Behavioral & Leadership Questions

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 code reviews, and what specific code smells do you look for before approving a pull reques

Medium · Problem-Solving & Scenario-Based Questio

How do you approach code reviews, and what specific code smells do you look for before approving a pull request?

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?