As a Software Engineer at Evernorth, you are a pivotal part of a dynamic team dedicated to enhancing healthcare solutions through innovative technology. This role is crucial as it directly influences the development and maintenance of applications that improve patient experiences and operational efficiencies. By leveraging your expertise, you will contribute to projects that range from building robust backend systems to implementing seamless user interfaces, all while ensuring compliance with industry regulations. In this role, you will work on various products that tackle significant challenges in the healthcare sector, collaborating closely with cross-functional teams to develop solutions that are not only scalable but also user-centric. The complexity of the projects you engage with will require a deep understanding of modern software development practices and a commitment to continuous improvement. Expect to be challenged and inspired as you play a key role in shaping the future of healthcare technology.
Application Submission
reportedCandidates submit their application for the Software Engineer position.
What to demonstrate
- Candidates submit their application for the Software Engineer position
- Depth in Java
How to prepare
- Answer aloud and timed: What are the differences between Java 8 and Java 11?
- Answer aloud and timed: Can you explain the Spring Boot lifecycle?
Initial Screening Call
reportedCandidates undergo an initial screening call with a recruiter.
What to demonstrate
- Candidates undergo an initial screening call with a recruiter
- Depth in Java
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 Interviews
reportedSuccessful candidates participate in one or more technical interviews, which may include coding challenges and design discussions.
What to demonstrate
- Successful candidates participate in one or more technical interviews, which may include coding challenges and design discussions
- Depth in Java
How to prepare
- Answer aloud and timed: What is the role of MongoDB in your projects?
- Answer aloud and timed: How would you design a microservices architecture for a healthcare application?
Managerial/HR Round
reportedFinal stage includes discussions around salary, benefits, and logistics with a manager or HR representative.
What to demonstrate
- Final stage includes discussions around salary, benefits, and logistics with a manager or HR representative
- Depth in Java
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 managerial/hr round above and write down what you would ask to confirm before it.
PracHub editorial advice for the preparation topics above.
Clarify Technical Concepts
When discussing technical topics, ensure you explain your thought process and reasoning. This helps interviewers gauge your understanding.
Practice Coding Under Pressure
Given the technical nature of the interviews, practice coding challenges in a timed environment to simulate real interview conditions.
Show Enthusiasm
Express your interest in the role and the mission of Evernorth. Enthusiasm can leave a positive impression on interviewers.
Prepare for Behavioral Questions
Reflect on past experiences that highlight your teamwork, problem-solving, and leadership skills.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
How would you optimize a function that processes large datasets?
How would you optimize a function that processes large datasets?
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- 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?
Can you explain the difference between a HashMap and a TreeMap?
Can you explain the difference between a HashMap and a TreeMap?
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- 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 a function to reverse a linked list.
Write a function to reverse a linked list.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- 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?
Implement a binary search algorithm.
Implement a binary search algorithm.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- 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?
Create a function that checks if a string is a palindrome.
Create a function that checks if a string is a palindrome.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- 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?
Keep soft-deleted accounts from blocking re-registration
app_user holds user_id, tenant_id, email CITEXT, password_hash (NULL for SSO principals), email_verified_at, auth_version, status ('invited','active','suspended','deactivated'), created_at, updated_at, deleted_at. Two live accounts for one address inside a tenant must be impossible, but an address freed by a soft delete must be reusable, and the same tenant may delete and re-register it repeatedly. Write the uniqueness DDL for PostgreSQL 16, then the equivalent for MySQL 8 where partial indexes do not exist, and say what each permits once three deleted rows already hold that address.
Approach
- Start from what is actually unique: not (tenant_id, email), but (tenant_id, email) among live rows. PostgreSQL says that directly — CREATE UNIQUE INDEX app_user_live_email ON app_user (tenant_id, email) WHERE deleted_at IS NULL. A full constraint over the same two columns burns the address permanently the first time someone deletes an account.
- Keep case-insensitivity in the type or the index, never in the application: CITEXT as given, or UNIQUE (tenant_id, lower(email)) as an expression index where the extension is unavailable. A case-sensitive unique column is exactly how two accounts for one human appear.
- For MySQL 8 the predicate has to move inside the key: add a discriminator column that is a constant 0 while the row is live and is set to user_id on delete, with UNIQUE (tenant_id, email, deleted_marker). Live rows share the constant and still collide; deleted rows differ from each other and stop colliding.
- State the NULL variant and its dependency: leaving the marker NULL for deleted rows also works, because a unique index treats NULLs as distinct — true in MySQL, and true in PostgreSQL only under the default NULLS DISTINCT, which PostgreSQL 15 lets you reverse. Check the polarity against the three existing deleted rows: constant-on-live is what preserves the collision you want, and reversing it silently admits duplicate live accounts.
Follow-up
- A deleted account re-registers with the same address the next day. Do the old resource rows follow the new user_id, and how does the API keep the two principals apart?
- How do you honour an erasure request while resource_revision.actor_user_id still references this table?
Explain why the owner filter ignores the listing index
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?
What are the differences between Java 8 and Java 11?
What are the differences between Java 8 and Java 11?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- 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 the Spring Boot lifecycle?
Can you explain the Spring Boot lifecycle?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- 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 the use of annotations in Spring Boot.
Describe the use of annotations in Spring Boot.
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
What is the role of MongoDB in your projects?
What is the role of MongoDB in your projects?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- 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 microservices architecture for a healthcare application?
How would you design a microservices architecture for a healthcare application?
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 how you would implement load balancing in your system.
Explain how you would implement load balancing in your system.
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?
What design patterns have you utilized in your projects, and why?
What design patterns have you utilized in your projects, and why?
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 how you would approach debugging a complex issue in production.
Describe how you would approach debugging a complex issue in production.
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?
Built from the rounds and topics Evernorth candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Evernorth loop
- Write out the reported sequence: Application Submission, Initial Screening Call, Technical Interviews, Managerial/HR Round.
- 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 Java
- Spend the session on Java, which Evernorth candidates report being tested on.
- Write one worked example in Java and time yourself on it.
Deliverable: One timed worked example in Java.
03Work Spring Boot
- Spend the session on Spring Boot, which Evernorth 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.
04Work JVM Garbage Collection
- Spend the session on JVM Garbage Collection, which Evernorth candidates report being tested on.
- Write one worked example in JVM Garbage Collection and time yourself on it.
Deliverable: One timed worked example in JVM Garbage Collection.
05Answer out loud: Technical Knowledge
- Answer aloud, timed: What are the differences between Java 8 and Java 11?
- Answer aloud, timed: Can you explain the Spring Boot lifecycle?
Deliverable: Spoken answers to 2 reported Technical Knowledge question(s), under time.
06Answer out loud: System Design
- Answer aloud, timed: How would you design a microservices architecture for a healthcare application?
- Answer aloud, timed: Explain how you would implement load balancing in your system.
Deliverable: Spoken answers to 2 reported System Design question(s), under time.
07Answer out loud: Behavioral Questions
- Answer aloud, timed: Tell me about a challenging project you worked on and how you overcame obstacles.
- Answer aloud, timed: How do you prioritize tasks when managing multiple responsibilities?
Deliverable: Spoken answers to 2 reported Behavioral Questions question(s), under time.
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.
How do you handle exception management in your applications?
How do you handle exception management in your applications?
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?
Can you describe a time when you had to refactor an application for better performance?
Can you describe a time when you had to refactor an application for better performance?
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 challenging project you worked on and how you overcame obstacles.
Tell me about a challenging project you worked on and how you overcame obstacles.
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 prioritize tasks when managing multiple responsibilities?
How do you prioritize tasks when managing multiple responsibilities?
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 had to work with a difficult team member.
Describe a situation where you had to work with a difficult team member.
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?
What motivates you to excel in your role as a software engineer?
What motivates you to excel in your role as a software engineer?
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?
- 01
How do you handle exception management in your applications?
- 02
Can you describe a time when you had to refactor an application for better performance?
- 03
Tell me about a challenging project you worked on and how you overcame obstacles.
- 04
How do you prioritize tasks when managing multiple responsibilities?
How difficult are the interviews at Evernorth?
The interviews can be challenging, especially in technical rounds, requiring a solid understanding of programming concepts and problem-solving abilities. Preparation is key, and candidates often benefit from practicing coding problems and reviewing system design principles.
Evernorth Software Engineer candidate reports ↗What differentiates successful candidates?
Successful candidates tend to demonstrate not only technical proficiency but also strong communication skills and a cultural fit with Evernorth's values. Showing enthusiasm for healthcare technology and a collaborative mindset can help you stand out.
Evernorth Software Engineer candidate reports ↗What is the typical timeline from initial screen to offer?
The timeline can vary, but candidates often experience a few weeks between initial screenings and final offers. It's crucial to follow up after interviews to express your continued interest.
Evernorth Software Engineer candidate reports ↗What topics does Evernorth test in interviews?
Evernorth interviews most often cover Python, Java, Spring Boot, Technical Interviewing, and Data Structures & Algorithms (DSA). The exact emphasis depends on the specific role you apply for.
Evernorth 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.
- 01Evernorth Software Engineer candidate reports ↗
Company-reported rounds, questions and FAQ.
Candidate reports · Accessed 2026-09-22 - 02PracHub Software Engineer practice ↗
PracHub practice material, not company-reported.
PracHub page · Accessed 2026-09-22 - 03PracHub preparation framework ↗
PracHub preparation guidance.
PracHub page · Accessed 2026-09-22
Explore related engineering environments and compare the preparation focus.
Confluent Software Engineer Interview Guide
Concurrency exercises for Confluent candidates: check-then-act races, deadlock from inconsistent lock ordering, and why two individually atomic operations do not compose into an atomic update.
GitHub Software Engineer Interview Questions & Guide 2026
Testing exercises for GitHub software engineer prep: choosing boundary cases over repetition, isolating tests from shared clock and ordering, and treating an intermittent failure as a defect rather than noise.
Zulily Software Engineer Interview Guide
What Zulily asks Software Engineer candidates, from reported rounds and questions.
Zoom Communications Software Engineer Interview Guide
What Zoom Communications asks Software Engineer candidates, from reported rounds and questions.