Interview guides · Humana

Humana Software Engineer Interview Guide

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

The 60-second brief

As a Software Engineer at Humana, you play a vital role in building and modernizing the digital health infrastructure that serves millions of healthcare members across the country. Humana relies heavily on technology to power automated decisioning engines, real-time clinical workflows, cloud infrastructure, and enterprise data processing. Engineers here build stateful microservices, optimize cloud utilization, maintain low-latency APIs, and deploy sophisticated algorithms that directly impact patient outcomes and administrative efficiency. The work at Humana combines high-concurrency systems development with strict healthcare compliance and data protection standards.

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

Focus areas

Behavioral Interviewing
Cloud Computing (General)
Technical Coding Assessments

The Humana interview process

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

Automated Pre-screening

Initial assessment using a video platform or online skills assessment to verify programming background and behavioral responses.

What to demonstrate

Initial assessment using a video platform or online skills assessment to verify programming background and behavioral responses
Depth in Behavioral Interviewing

How to prepare

Answer aloud and timed: Why do you want to work for Humana, and why are you interested in the healthcare sector?
Answer aloud and timed: Describe a time when you had a conflict with a teammate or stakeholder. How did you handle it and what was the outcome?

Recruiter Interaction

Discussion with a recruiter or hiring coordinator to align on logistics, team specifics, and candidate expectations.

What to demonstrate

Discussion with a recruiter or hiring coordinator to align on logistics, team specifics, and candidate expectations
Depth in Behavioral Interviewing

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 Evaluation

Mix of live technical panel interviews and pair-programming or architecture discussions focusing on practical problem-solving and code readability.

What to demonstrate

Mix of live technical panel interviews and pair-programming or architecture discussions focusing on practical problem-solving and code readability
Depth in Behavioral Interviewing

How to prepare

Answer aloud and timed: Describe a situation where you noticed a process or workflow inefficiency. What steps did you take to resolve it?
Answer aloud and timed: Walk me through how you would debug a real-world API integration issue between a front-end interface and a back-end microservice.

Final Panel Interview

Broader panel interview with hiring managers, software architects, and engineering team members to evaluate team fit and project history.

What to demonstrate

Broader panel interview with hiring managers, software architects, and engineering team members to evaluate team fit and project history
Depth in Behavioral Interviewing

How to prepare

Answer aloud and timed: Explain the key differences between synchronous REST APIs and asynchronous event-driven communications.
Answer aloud and timed: How do you handle security concerns, authentication, and authorization when designing APIs in an enterprise setting?

Where candidates lose points

Structure Every Behavioral Answer

Frame every behavioral story around the STAR method. State the Situation concisely, outline your specific Task, detail your individual Actions, and highlight the measurable Result.

Focus on Practical Code Quality

During coding or pair-programming sessions, prioritize clean naming conventions, explicit error handling, and testability over overly complex optimization tricks.

Highlight System Resilience

When discussing architecture or backend design, actively talk about idempotency, retry mechanisms, failure modes, and observability. Interviewers value engineers who plan for partial system failures.

Questions & practice

How do you manage optimistic versus pessimistic locking in high-concurrency database updates?

Medium · System Design, Architecture & Cloud

Approach

Say what the runtime actually does before reasoning about the code.
Name what is shared across threads and what owns each piece of state.
Identify the window where an invariant is briefly untrue.
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?

Merge partitioned event streams into one ordered feed with bounded lateness

Hard · k-way merge · watermarks · out-of-order streams

The read-model service consumes 64 log partitions carrying about 4,000 events per second in total. Each partition is ordered within itself, but partitions drift by up to 30 seconds, and the activity feed must present a tenant's events in occurred_at order. Produce the merge. State its complexity, the buffer it requires in events and in bytes, what happens when one partition is idle, and what you do with an event that arrives after you have already emitted its position. Payloads average 1 KB.

Approach

Merge with a min-heap over the 64 partition heads keyed on (occurred_at, event_id): O(log P) per event and O(n log P) overall. The tie-break on event_id is what makes the output deterministic when two partitions carry the same millisecond, which matters because the feed is paginated and a non-deterministic order reorders pages under the reader.
Emitting the heap head is only correct once every partition has produced everything up to that timestamp, so the emit condition is a watermark: the minimum across partitions of the highest occurred_at seen, less the allowed lateness. Events are held until the watermark passes them, which is what turns individually ordered streams into a jointly ordered one.
Size the buffer from the lateness rather than guessing: 4,000 events per second times 30 seconds is 120,000 buffered events, and at 1 KB each about 120 MB of heap. That number is the real price of the ordering guarantee and belongs in front of whoever asked for it.
Handle the idle partition explicitly, because it fails the feed rather than corrupting it: a partition with no traffic never advances its own maximum, so the watermark freezes and output stops entirely. Either every partition emits a periodic idle marker carrying the broker's current time, or the watermark falls back to wall clock for a partition silent beyond a threshold.

Follow-up

The lateness budget is raised to five minutes. What is the new buffer, and what besides memory changes?
The consumer restarts. Where does it resume from, and what does the feed look like for the first 30 seconds?

Identify the heaviest tenants in a five-minute window under memory pressure

Medium · top-k · heavy hitters · streaming

The edge service handles about 3,000 requests per second across roughly 50,000 tenants, peaking near 9,000. Expose the 50 heaviest tenants by request count over the trailing five minutes so limits can be tightened before one tenant's backfill starves the fleet. You may not retain five minutes of raw records. Give the exact solution and its memory, then the bounded-memory approximation with its error stated as a formula, and say which you would ship and at what tenant cardinality that choice changes.

Approach

Do the exact version first, because it is affordable at this cardinality: a ring of 300 one-second counters per tenant, advanced lazily, is 1,200 bytes of counters per tenant and roughly 60 to 90 MB for 50,000 tenants with overhead. Carry a running total and subtract the bucket you overwrite so a window read is O(1) rather than 300 adds.
Extract the top 50 with a size-k min-heap over the tenant sums: O(d log k) for d tenants, against O(d log d) to sort them all. Maintaining the heap continuously instead of on query requires a tenant-to-heap-index map, because incrementing a count already inside the heap means sifting from a known position, and without that map you rebuild the heap on every request.
State the approximation precisely rather than gesturing at sketches. Misra-Gries with m counters retains every item whose true count exceeds N/(m+1), and each retained count underestimates the truth by at most N/(m+1). With m = 1,000 and N = 900,000 requests in the window the error is roughly 900 requests, which is fine for spotting a tenant sending 50,000 and useless for ranking two tenants 200 apart.
Say what breaks when the window slides: Misra-Gries and Space-Saving are insert-only and cannot be decremented as records age out. The workable construction is one summary per sub-window, say ten seconds, with 30 summaries merged at query time, and the merged error is the sum of the per-summary errors, so the bound degrades linearly in the number of sub-windows.

Follow-up

The heaviest tenant is heavy because of one export job rather than user traffic. Should the limiter treat those as the same tenant?
Two tenants sit tied at the boundary of the top 50. Does your answer flap, and does the flapping matter?

Explain why the owner filter ignores the listing index

Medium · composite index · query plans · sort elimination

The only index on resource is (tenant_id, status, updated_at DESC, resource_id DESC). A new endpoint returns one user's resources across all statuses, newest created first: WHERE tenant_id = $1 AND owner_user_id = $2 ORDER BY created_at DESC LIMIT 20. On a tenant with 2M rows it takes 900 ms and EXPLAIN shows a sort above a large scan. Explain precisely why the existing index cannot serve it, give the index that can, and state which of these the new index still will not help: owner_user_id alone across tenants; the same query ordered by updated_at. PostgreSQL 16.

Approach

Separate the two jobs an index does. For filtering, a composite btree is seekable only on a left prefix, so with no predicate on status the scan can at best range over tenant_id and test owner_user_id per row; PostgreSQL 16 has no btree skip scan to jump the unconstrained column.
For ordering, the index is sorted by (status, updated_at) within a tenant and not by created_at, so the LIMIT cannot stop early: every matching row is read and then sorted. That is the 'Sort Method: top-N heapsort' line, and it is why the plan reads 2M rows to answer with 20.
Derive the replacement from the access path — equality, equality, then the ordering column: CREATE INDEX CONCURRENTLY ON resource (tenant_id, owner_user_id, created_at DESC). The scan seeks to the (tenant, owner) range and walks 20 entries in order, so the Sort node disappears along with the row-read.
Treat INCLUDE (title, status) as conditional, not free. An index-only scan still visits the heap for any row whose page is not marked all-visible, so on a table taking 1.2k writes/second the win depends on autovacuum keeping the visibility map current, and the wider index costs more on every insert.

Follow-up

90% of rows are status='active'. Would a partial index WHERE status = 'active' change your answer, and for which of the three queries?
A dashboard runs this for 40 owners in one page load. What changes about the design?

Denormalise tenant onto revisions and backfill it live

Hard · denormalisation · online migration · backfill

resource_revision (revision_id, resource_id, version, actor_user_id, change_kind, patch, request_id, created_at) has 400M rows and no tenant column; tenant_id lives only on resource. Two reads need it: a tenant-scoped audit feed ordered by created_at DESC, and an offboarding purge. Both join back to resource today. Justify adding tenant_id to resource_revision against those two reads, name the anomaly the copy introduces and the constraint that prevents it, then give the ordered migration for a live table taking 1.2k writes/second — the lock each step takes, how the backfill is batched, and where each step stops being reversible. PostgreSQL 16.

Approach

Justify from the access path rather than from taste. Without the column, the audit feed either scans resource_revision by created_at and discards other tenants' rows, or resolves the tenant's resource_ids first and probes with them — both proportional to the tenant's whole history rather than to one page. With (tenant_id, created_at DESC, revision_id DESC) it is a seek that stops at 50 rows, and the purge becomes a ranged delete instead of a join.
Name the cost exactly: a second copy of a fact can disagree with the first. Make the disagreement unwritable rather than documented — add UNIQUE (resource_id, tenant_id) on resource so it can serve as a foreign-key target, then FOREIGN KEY (resource_id, tenant_id) REFERENCES resource (resource_id, tenant_id) on the revision table. A revision can then only ever carry its parent's tenant.
Step one, expand: ALTER TABLE resource_revision ADD COLUMN tenant_id BIGINT NULL, with no default, so it is a catalogue change and no rewrite. It still needs ACCESS EXCLUSIVE for an instant, and that instant queues behind the longest open transaction on the table while every later query queues behind it — set lock_timeout to 2s and retry rather than wait.
Step two, dual-write: deploy the writer that populates tenant_id on every new revision while reads still use the join. Reversible by redeploying the previous build, because nothing reads the column yet.

Follow-up

The backfill is half finished and a rollback is required. What state is the table in, and what does the previous build do with a half-populated column?
How do you verify the backfill actually finished, given rows are still being inserted while it runs?

Walk me through how you would debug a real-world API integration issue between a front-end interface and a bac

Medium · Technical Fundamentals & Practical Troub

Walk me through how you would debug a real-world API integration issue between a front-end interface and a back-end microservice.

Approach

Say who the caller is and what they do when the call fails halfway.
Define the identity of a request so a retry cannot double-apply it.
Separate accepted, pending, failed and confirmed; they are different facts.
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?

Explain the key differences between synchronous REST APIs and asynchronous event-driven communications.

Medium · Technical Fundamentals & Practical Troub

Approach

Say who the caller is and what they do when the call fails halfway.
Define the identity of a request so a retry cannot double-apply it.
Separate accepted, pending, failed and confirmed; they are different facts.
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 would you design a resilient, stateful system that guarantees idempotent execution across retries and part

Medium · System Design, Architecture & Cloud

How would you design a resilient, stateful system that guarantees idempotent execution across retries and partial network failures?

Approach

Fix the scope first: who calls this, how often, and what they do when it fails.
Name the read and write paths separately; they rarely have the same bottleneck.
Choose a partition key and say what query it makes expensive.
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 the Outbox Pattern and how it ensures atomicity between local database state updates and event publish

Medium · System Design, Architecture & Cloud

Explain the Outbox Pattern and how it ensures atomicity between local database state updates and event publishing to downstream systems.

Approach

Fix the scope first: who calls this, how often, and what they do when it fails.
Name the read and write paths separately; they rarely have the same bottleneck.
Choose a partition key and say what query it makes expensive.
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 experience with cloud platforms, specifically regarding microservices deployment, messaging queu

Medium · System Design, Architecture & Cloud

Describe your experience with cloud platforms, specifically regarding microservices deployment, messaging queues, and serverless architecture.

Approach

Fix the scope first: who calls this, how often, and what they do when it fails.
Name the read and write paths separately; they rarely have the same bottleneck.
Choose a partition key and say what query it makes expensive.
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 a complex technical bug you encountered in a recent project. How did you diagnose it, and what was th

Medium · Technical Fundamentals & Practical Troub

Describe a complex technical bug you encountered in a recent project. How did you diagnose it, and what was the fix?

Approach

Establish what changed and when, before forming any theory.
Pick a bisection that eliminates candidates whichever way it turns out.
Check the instrumentation before believing the symptom.
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?

What considerations do you take into account when optimizing cloud resource usage and cloud cost efficiency?

Medium · Technical Fundamentals & Practical Troub

Approach

Establish what changed and when, before forming any theory.
Pick a bisection that eliminates candidates whichever way it turns out.
Check the instrumentation before believing the symptom.
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?

Walk through a troubleshooting scenario involving network routing, distributed cloud services, or infrastructu

Medium · System Design, Architecture & Cloud

Walk through a troubleshooting scenario involving network routing, distributed cloud services, or infrastructure failures.

Approach

Establish what changed and when, before forming any theory.
Pick a bisection that eliminates candidates whichever way it turns out.
Check the instrumentation before believing the symptom.
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 Humana candidates report.

Day 1 — Map the Humana loop

Write out the reported sequence: Automated Pre-screening, Recruiter Interaction, Technical Evaluation, Final 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 4 reported rounds, with the weakest marked.

Day 2 — Work Behavioral Interviewing

Spend the session on Behavioral Interviewing, which Humana 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 3 — Work Cloud Computing (General)

Spend the session on Cloud Computing (General), which Humana candidates report being tested on.
Write one worked example in Cloud Computing (General) and time yourself on it.

Deliverable: One timed worked example in Cloud Computing (General).

Day 4 — Work Technical Coding Assessments

Spend the session on Technical Coding Assessments, which Humana candidates report being tested on.
Write one worked example in Technical Coding Assessments and time yourself on it.

Deliverable: One timed worked example in Technical Coding Assessments.

Day 5 — Answer out loud: Behavioral & Behavioral Scenarios

Answer aloud, timed: Why do you want to work for Humana, and why are you interested in the healthcare sector?
Answer aloud, timed: Describe a time when you had a conflict with a teammate or stakeholder. How did you handle it and what was the outcome?

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

Day 6 — Answer out loud: Technical Fundamentals & Practical Troubleshooting

Answer aloud, timed: Walk me through how you would debug a real-world API integration issue between a front-end interface and a back-end microservice.
Answer aloud, timed: Explain the key differences between synchronous REST APIs and asynchronous event-driven communications.

Deliverable: Spoken answers to 2 reported Technical Fundamentals & Practical Troubleshooting question(s), under time.

Day 7 — Answer out loud: System Design, Architecture & Cloud

Answer aloud, timed: How would you design a resilient, stateful system that guarantees idempotent execution across retries and partial network failures?
Answer aloud, timed: Explain the Outbox Pattern and how it ensures atomicity between local database state updates and event publishing to downstream systems.

Deliverable: Spoken answers to 2 reported System Design, Architecture & Cloud question(s), under time.

Behavioural preparation

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

Why do you want to work for Humana, and why are you interested in the healthcare sector?

Medium · Behavioral & Behavioral Scenarios

Approach

Pick a story where you made the decision, not one where you watched it.
State the situation in two sentences and spend the rest on the reasoning.
Give the blast radius: what could have broken, and what you measured.
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 a conflict with a teammate or stakeholder. How did you handle it and what was the

Medium · Behavioral & Behavioral Scenarios

Describe a time when you had a conflict with a teammate or stakeholder. How did you handle it and what was the outcome?

Approach

Pick a story where you made the decision, not one where you watched it.
State the situation in two sentences and spend the rest on the reasoning.
Give the blast radius: what could have broken, and what you measured.
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 had to convince your team or leadership to adopt a specific technical approach o

Medium · Behavioral & Behavioral Scenarios

Tell me about a time when you had to convince your team or leadership to adopt a specific technical approach or solution.

Approach

Pick a story where you made the decision, not one where you watched it.
State the situation in two sentences and spend the rest on the reasoning.
Give the blast radius: what could have broken, and what you measured.
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?

Give an example of a situation where you had to work under highly stressful conditions or tight deadlines. How

Medium · Behavioral & Behavioral Scenarios

Give an example of a situation where you had to work under highly stressful conditions or tight deadlines. How did you prioritize?

Approach

Pick a story where you made the decision, not one where you watched it.
State the situation in two sentences and spend the rest on the reasoning.
Give the blast radius: what could have broken, and what you measured.
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 noticed a process or workflow inefficiency. What steps did you take to resolve

Medium · Behavioral & Behavioral Scenarios

Describe a situation where you noticed a process or workflow inefficiency. What steps did you take to resolve it?

Approach

Pick a story where you made the decision, not one where you watched it.
State the situation in two sentences and spend the rest on the reasoning.
Give the blast radius: what could have broken, and what you measured.
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 security concerns, authentication, and authorization when designing APIs in an enterprise se

Medium · Technical Fundamentals & Practical Troub

How do you handle security concerns, authentication, and authorization when designing APIs in an enterprise setting?

Approach

Pick a story where you made the decision, not one where you watched it.
State the situation in two sentences and spend the rest on the reasoning.
Give the blast radius: what could have broken, and what you measured.
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?