Hays Solutions · Software Engineer
Updated · 2026-10-02

Hays Solutions Software Engineer
Interview Guide

THE 60-SECOND BRIEF

As a Software Engineer at Hays Solutions, you serve as a critical bridge between complex technical requirements and high-impact business outcomes. You are not merely writing code; you are architecting solutions that drive efficiency, support internal stakeholders, and contribute to the robust infrastructure that defines the Hays Solutions ecosystem. Your work directly influences the speed and reliability with which the organization meets its operational goals. This role requires a balance of technical proficiency and a deep understanding of the business landscape. Whether you are working on internal tools or client-facing systems, you will be expected to demonstrate a high degree of accountability and problem-solving capability.

This guide is scoped to a Software Engineer candidate at Hays Solutions.

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

ASP.NETObject-Oriented Programming (OOP)IT Support (VIP/Client Support)

20 min read

Browse Software Engineer questions

See the practice prompts

16Practice promptsAcross five skill areas

As a Software Engineer at Hays Solutions, you serve as a critical bridge between complex technical requirements and high-impact business outcomes. You are not merely writing code; you are architecting solutions that drive efficiency, support internal stakeholders, and contribute to the robust infrastructure that defines the Hays Solutions ecosystem. Your work directly influences the speed and reliability with which the organization meets its operational goals. This role requires a balance of technical proficiency and a deep understanding of the business landscape. Whether you are working on internal tools or client-facing systems, you will be expected to demonstrate a high degree of accountability and problem-solving capability. Success in this position is measured by your ability to translate ambiguous requirements into clean, scalable, and maintainable software while effectively collaborating across multidisciplinary teams. ##### Tip The Software Engineer role at Hays Solutions often involves a mix of legacy system maintenance and modern development, requiring you to be adaptable and comfortable working with diverse tech stacks.

01

Initial Screening

reported

Begins with a video call to establish your background and motivation.

What to demonstrate

  • Begins with a video call to establish your background and motivation
  • Depth in ASP.NET

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.
Hays Solutions Software Engineer candidate reports ↗
02

Technical Assessments

reported

Progress into formal technical evaluations, including written tests and deep-dive sessions.

What to demonstrate

  • Progress into formal technical evaluations
  • Including written tests and deep-dive sessions

How to prepare

  • Answer aloud and timed: What are your key strengths and weaknesses?
  • Answer aloud and timed: Why are you looking for a new opportunity?
Hays Solutions Software Engineer candidate reports ↗
03

Personal Interviews

reported

Engage in interviews focused on personal fit and technical capabilities.

What to demonstrate

  • Engage in interviews focused on personal fit and technical capabilities
  • Depth in ASP.NET

How to prepare

  • Answer aloud and timed: How do you manage your workload and prioritize tasks?
  • Answer aloud and timed: What do you know about our company and products?
Hays Solutions Software Engineer candidate reports ↗
04

Management Discussions

reported

Participate in discussions with management to assess alignment with team goals.

What to demonstrate

  • Participate in discussions with management to assess alignment with team goals
  • Depth in ASP.NET

How to prepare

  • Answer aloud and timed: Can you explain basic OOPS (Object-Oriented Programming) concepts?
  • Answer aloud and timed: What is your experience with ASP.NET or similar frameworks?
Hays Solutions Software Engineer candidate reports ↗

PracHub editorial advice for the preparation topics above.

01

Prepare for the "Why

Beyond technical skills, be ready to explain why you want to work for this specific company. Researching their business model will give you a significant advantage.

02

Focus on Clarity

When answering behavioral questions, use the STAR method (Situation, Task, Action, Result) to ensure your answers are structured and easy to follow.

03

Stay Calm under Pressure

If you encounter a technical question you don't know, explain your thought process out loud. Interviewers often value your approach to finding a solution over an immediate, perfect answer.

04

Review your Resume

Be prepared to talk about every project listed on your resume in detail. Know the "what," "why," and "how" of your past contributions.

Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.

10 technical prompts0 include a worked solution

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

easy
hashingat-least-onceaggregation

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?

Find overlapping job attempts and peak concurrency from lease records

medium
sweep lineintervalsleases

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

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

Canonicalise a request body into a stable idempotency fingerprint

medium
parsingcanonicalisationhashing

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?

Built from the rounds and topics Hays Solutions candidates report.

Small steps. Visible outcomes.0 / 7 completed
ONE WEEK · YOUR PACE

Prepare, practise & reflect

One practical outcome each day. Spend longer where you need it.

0 / 7 done
01Map the Hays Solutions loop
  • Write out the reported sequence: Initial Screening, Technical Assessments, Personal Interviews, Management Discussions.
  • 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.

02Work ASP.NET
  • Spend the session on ASP.NET, which Hays Solutions candidates report being tested on.
  • Write one worked example in ASP.NET and time yourself on it.

Deliverable: One timed worked example in ASP.NET.

03Work Object-Oriented Programming (OOP)
  • Spend the session on Object-Oriented Programming (OOP), which Hays Solutions candidates report being tested on.
  • Write one worked example in Object-Oriented Programming (OOP) and time yourself on it.

Deliverable: One timed worked example in Object-Oriented Programming (OOP).

04Work IT Support (VIP/Client Support)
  • Spend the session on IT Support (VIP/Client Support), which Hays Solutions candidates report being tested on.
  • Write one worked example in IT Support (VIP/Client Support) and time yourself on it.

Deliverable: One timed worked example in IT Support (VIP/Client Support).

05Answer out loud: Behavioral and Role Motivation
  • Answer aloud, timed: Tell me about yourself.
  • Answer aloud, timed: Walk us through your resume and experience.

Deliverable: Spoken answers to 2 reported Behavioral and Role Motivation question(s), under time.

06Answer out loud: Technical and Problem-Solving
  • Answer aloud, timed: What do you know about our company and products?
  • Answer aloud, timed: Can you explain basic OOPS (Object-Oriented Programming) concepts?

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

07Dry run for Hays Solutions
  • Run one full mock under time, then write down the two questions you most want to ask your interviewers.

Deliverable: A completed timed mock and two questions to ask.

Expand any day for tasks and deliverables. Your progress is saved on this device.

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

Tell me about yourself.

medium
Behavioral and Role Motivation

Tell me about yourself.

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?

Walk us through your resume and experience.

medium
Behavioral and Role Motivation

Walk us through your resume and experience.

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?

What are your key strengths and weaknesses?

medium
Behavioral and Role Motivation

What are your key strengths and weaknesses?

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 are you looking for a new opportunity?

medium
Behavioral and Role Motivation

Why are you looking for a new opportunity?

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 workload and prioritize tasks?

medium
Behavioral and Role Motivation

How do you manage your workload and prioritize tasks?

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?

What is your experience with ASP.NET or similar frameworks?

medium
Technical and Problem-Solving

What is your experience with ASP.NET or similar frameworks?

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?
  • 01

    Tell me about yourself.

  • 02

    Walk us through your resume and experience.

  • 03

    What are your key strengths and weaknesses?

  • 04

    Why are you looking for a new opportunity?

PracHub preparation framework ↗
How difficult are the technical assessments?

The assessments are generally considered manageable if you have a strong grasp of fundamentals. They focus more on your ability to apply basic principles correctly than on solving highly obscure algorithm puzzles.

Hays Solutions Software Engineer candidate reports ↗
What is the most important factor in getting an offer?

A combination of technical reliability and professional communication. The interviewers are looking for someone who can be trusted to handle tasks independently while remaining a team player.

Hays Solutions Software Engineer candidate reports ↗
How long does the process take?

The process can move relatively quickly once you pass the initial screening. Expect a few weeks of active engagement, including the time taken for technical evaluations and management interviews. ##### Tip Prepare for the "Why Hays Solutions?" question by researching the company's recent initiatives and their core business model.

Hays Solutions Software Engineer candidate reports ↗
What topics does Hays Solutions test in interviews?

Hays Solutions interviews most often cover Requirements Gathering, Cross-Functional Collaboration, Project Management, ASP.NET, and Stakeholder Management. The exact emphasis depends on the specific role you apply for.

Hays Solutions Software Engineer candidate reports ↗
Sources & methodology 3 sources ↗

No official company page is cited. Rounds and questions come from candidate reports and PracHub editorial material; each source shows the date it was read.