cswork / libraryOpen practice workspace

Interview guides · Evernorth Health Services India

Evernorth Health Services India Software Engineer Interview Guide

Evernorth Health Services India Software Engineer interview guide: reported rounds, questions and how candidates describe the process.

The 60-second brief

As a Software Engineer at Evernorth Health Services India, you are at the intersection of complex healthcare data and scalable technology. This role is pivotal in building and maintaining the platforms that power health service delivery, requiring you to bridge the gap between high-level architectural requirements and precise, efficient code. You will contribute to mission-critical systems that affect millions of lives, necessitating a high degree of responsibility, technical rigor, and a commitment to stability. The work environment is fast-paced and demands an ability to thrive in a large, distributed organizational structure. You will be expected to solve problems that range from optimizing database performance to architecting robust microservices.

This guide is scoped to a Software Engineer candidate at Evernorth Health Services India.

Focus areas

  • Algorithms
  • Spring Boot
  • Problem Solving (Core Reasoning)

The Evernorth Health Services India interview process

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

Initial Recruiter Engagement

The process begins with a recruiter reaching out to discuss your background and the role.

What to demonstrate

  • The process begins with a recruiter reaching out to discuss your background and the role
  • Depth in Algorithms

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 Assessments

Deep-dive technical assessments to evaluate your technical depth.

What to demonstrate

  • Deep-dive technical assessments to evaluate your technical depth
  • Depth in Algorithms

How to prepare

  • Answer aloud and timed: Can you explain the principles of Object-Oriented Programming (OOP) and how you apply them in your daily work?
  • Answer aloud and timed: Describe your experience with Spring Boot and managing dependencies in a microservices environment.

Panel-Based Behavioral Interviews

Behavioral interviews conducted by a panel to assess your fit within the engineering culture.

What to demonstrate

  • Behavioral interviews conducted by a panel to assess your fit within the engineering culture
  • Depth in Algorithms

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 panel-based behavioral interviews above and write down what you would ask to confirm before it.

Final Panel Evaluations

Final evaluations by a panel to make a decision on your candidacy.

What to demonstrate

  • Final evaluations by a panel to make a decision on your candidacy
  • Depth in Algorithms

How to prepare

  • Answer aloud and timed: How would you design a highly available service that handles millions of requests daily?
  • Answer aloud and timed: Explain how you would implement a caching strategy to improve application performance.

Where candidates lose points

Structure your answers

Use the STAR method (Situation, Task, Action, Result) for all behavioral questions to keep your responses concise and impactful.

Be honest about your skills

If asked about a technology you haven't used, explain your familiarity with related concepts rather than pretending to have expertise.

Prepare questions for the interviewer

Always have 3-5 thoughtful questions about the team’s current challenges or the company’s engineering culture to demonstrate your genuine interest.

Always clarify the requirements of a coding problem before you start writing

Interviewers value the process of understanding the problem more than just the final syntax.

Questions & practice

What are your preferred strategies for handling concurrency and multi-threading in your applications?

Medium · Technical Fundamentals and Domain Knowle

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?

Canonicalise a request body into a stable idempotency fingerprint

Medium · parsing · canonicalisation · hashing

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?

Archive a resource graph without breaking live references or recursing

Medium · graph traversal · topological order · tenant isolation

Resources reference other resources within a tenant; for the largest tenant the reference table holds up to 2,000,000 nodes and 8,000,000 edges. Archiving a resource must archive everything reachable from it that nothing outside the set still references, refuse when a live external referrer exists, and terminate when references form cycles, which they legitimately do. Produce the archive order and the refusal list, targeting O(V+E). Say what stops the traversal crossing a tenant boundary, and why recursion is the wrong control structure at this size.

Approach

  1. Load the subgraph with the tenant predicate on both endpoints of the edge, not only on the side you started from. Scoping the left table alone is the classic cross-tenant leak: one mis-entered edge then pulls another tenant's resources into the traversal and, worse, into the archive.
  2. Traverse iteratively with an explicit stack. A 2,000,000-node graph can hold a chain deep enough to exhaust a native stack in the low tens of thousands of frames, and that failure is a process crash rather than an error you can return.
  3. Treat cycles as data rather than corruption: compute strongly connected components with Tarjan in O(V+E) using its own explicit stack, then condense. The condensation is a DAG, so a topological order over it gives the archive order, and every member of a component archives in one transaction because no order within a cycle is valid.
  4. Decide refusals with reverse edges. A candidate is archivable only if every in-edge originates inside the candidate set, so build the transpose or count in-degrees restricted to the visited set, and emit each blocked resource with the id of the external referrer, which is the only part of the answer an operator can act on.

Follow-up

  • The graph is read in one query and the archive writes a minute later. What can change in between, and how do you make the write safe?
  • The candidate set is 400,000 resources. Is that one transaction, and if not, what does a half-finished archive look like to a reader?

How do you optimize SQL queries for large, complex datasets?

Medium · Technical Fundamentals and Domain Knowle

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?

Find version gaps and relay lag with window functions

Medium · window functions · event tables · frame semantics

outbox_event holds event_id, aggregate_type, aggregate_id, aggregate_version, event_type, payload, status ('pending','published','dead'), attempts, created_at, published_at. A projection is missing rows and you must decide whether the relay skipped events or the consumer dropped them. Write three queries over the last seven days: one listing every aggregate_id whose published aggregate_version sequence has a hole, one giving per-day counts with a running total, and one returning the newest published event per aggregate. For each, say where the window function is evaluated relative to WHERE and LIMIT. PostgreSQL 16.

Approach

  1. Gaps: compute lead(aggregate_version) OVER (PARTITION BY aggregate_id ORDER BY aggregate_version) in a subquery, then filter next_version <> aggregate_version + 1 in the outer query. Window functions are evaluated after WHERE, GROUP BY and HAVING and before the outer ORDER BY and LIMIT, so the predicate cannot sit in the same WHERE clause and PostgreSQL 16 has no QUALIFY.
  2. Say what the seven-day filter does to the answer: it truncates every partition, so the first row per aggregate has no predecessor inside the window and a hole spanning the boundary is invisible. Widen the window, or join to resource.version as the authority for the true maximum.
  3. Running total: SELECT date_trunc('day', created_at) AS d, count() AS n, sum(count()) OVER (ORDER BY date_trunc('day', created_at) ROWS UNBOUNDED PRECEDING). An aggregate inside a window call is legal because grouping runs before windowing. The grouping key is unique per row here so ROWS and RANGE agree, but write the frame anyway — over ungrouped rows with tied timestamps the default RANGE frame pulls in every peer row and the total jumps.
  4. Newest per aggregate: DISTINCT ON (aggregate_id) ... ORDER BY aggregate_id, aggregate_version DESC is the cheap PostgreSQL-only form when an index matches that order; row_number() OVER (PARTITION BY aggregate_id ORDER BY aggregate_version DESC) = 1 is the portable form and needs a subquery for the same evaluation-order reason as the gap query.

Follow-up

  • Relay failover redelivers events. Does a duplicate break the gap query, and how would you detect one from this table alone?
  • Turn the gap check into a continuous monitor rather than a query someone runs after an incident. What does it watch?

Explain the difference between REST and SOAP and when to use each.

Medium · Technical Fundamentals and Domain Knowle

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?

Can you explain the principles of Object-Oriented Programming (OOP) and how you apply them in your daily work?

Medium · Technical Fundamentals and Domain Knowle

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 design a highly available service that handles millions of requests daily?

Medium · System Design and 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?

Explain how you would implement a caching strategy to improve application performance.

Medium · System Design and 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?

How do you approach debugging a production issue in a distributed system?

Medium · System Design and Problem Solving

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 Evernorth Health Services India candidates report.

Day 1 — Map the Evernorth Health Services India loop

  • Write out the reported sequence: Initial Recruiter Engagement, Technical Assessments, Panel-Based Behavioral Interviews, Final Panel Evaluations.
  • 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 Algorithms

  • Spend the session on Algorithms, which Evernorth Health Services India candidates report being tested on.
  • Write one worked example in Algorithms and time yourself on it.

Deliverable: One timed worked example in Algorithms.

Day 3 — Work Spring Boot

  • Spend the session on Spring Boot, which Evernorth Health Services India candidates report being tested on.
  • Write one worked example in Spring Boot and time yourself on it.

Deliverable: One timed worked example in Spring Boot.

Day 4 — Work Problem Solving (Core Reasoning)

  • Spend the session on Problem Solving (Core Reasoning), which Evernorth Health Services India candidates report being tested on.
  • Write one worked example in Problem Solving (Core Reasoning) and time yourself on it.

Deliverable: One timed worked example in Problem Solving (Core Reasoning).

Day 5 — Answer out loud: Technical Fundamentals and Domain Knowledge

  • Answer aloud, timed: Explain the difference between REST and SOAP and when to use each.
  • Answer aloud, timed: How do you optimize SQL queries for large, complex datasets?

Deliverable: Spoken answers to 2 reported Technical Fundamentals and Domain Knowledge question(s), under time.

Day 6 — Answer out loud: System Design and Problem Solving

  • Answer aloud, timed: Describe a time you had to design a system from scratch. What were your primary considerations?
  • Answer aloud, timed: How would you design a highly available service that handles millions of requests daily?

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

Day 7 — Answer out loud: Behavioral and Cultural Fit

  • Answer aloud, timed: Tell me about a time you had a conflict with a teammate. How did you resolve it?
  • Answer aloud, timed: Describe a situation where you had to explain a complex technical concept to a non-technical stakeholder.

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

Behavioural preparation

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

Describe your experience with Spring Boot and managing dependencies in a microservices environment.

Medium · Technical Fundamentals and Domain Knowle

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 you had to design a system from scratch. What were your primary considerations?

Medium · System Design and Problem Solving

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 you had a conflict with a teammate. How did you resolve it?

Medium · Behavioral and Cultural Fit

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 explain a complex technical concept to a non-technical stakeholder.

Medium · Behavioral and Cultural Fit

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 tight deadlines and shifting priorities?

Medium · Behavioral and Cultural Fit

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?

Give an example of a project where you took initiative to improve a process or system.

Medium · Behavioral and Cultural Fit

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?