Eversana Software Engineer Interview Guide

The 60-second brief

At Eversana, a Software Engineer plays a pivotal role in transforming the life sciences industry. Eversana is a leading provider of global commercial services to the pharmaceutical and biotechnology sectors. As a software engineer, you will design, build, and maintain the complex digital platforms that power patient support services, channel management, specialty consulting, and real-time analytics. Your work directly impacts how life-saving treatments are commercialized and delivered to patients globally. This role requires a unique blend of technical expertise, problem-solving agility, and domain awareness. Unlike generic tech companies, Eversana operates in a highly regulated healthcare environment. This means the systems you develop must be exceptionally secure, scalable, and compliant with industry standards.

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

Focus areas

• Java (Core)
• Sorting Algorithms (Arrays)
• Problem Solving

The Eversana interview process

Eversana candidates report 6 rounds over 4-6 weeks. The stages below are what candidates describe, not a published process.

HR Screening

Initial call providing information about Eversana, the team, and the interview roadmap.

What to demonstrate

• Initial call providing information about Eversana, the team, and the interview roadmap
• Depth in Java (Core)

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 Screening

Focus on core programming concepts, basic algorithms, and database queries.

What to demonstrate

• Focus on core programming concepts, basic algorithms, and database queries
• Depth in Java (Core)

How to prepare

• Answer aloud and timed: How does exception handling work in Java? Describe the difference between checked and unchecked exceptions.
• Answer aloud and timed: Explain the concept of method overloading versus method overriding with real-world examples.

Project Discussions

Deep dive into project requirements and real-time scenarios based on past experiences.

What to demonstrate

• Deep dive into project requirements and real-time scenarios based on past experiences
• Depth in Java (Core)

How to prepare

• Answer aloud and timed: What is the Java Collections Framework? How does a HashMap work internally?
• Answer aloud and timed: Write a SQL query using different types of joins (inner, left, right, full) to combine patient and prescription records.

Online Assessment (Campus)

For campus placements, an online exam may be included before technical interviews.

What to demonstrate

• For campus placements, an online exam may be included before technical interviews
• Depth in Java (Core)

How to prepare

• Answer aloud and timed: What is database normalization, and why is it important in enterprise applications?
• Answer aloud and timed: How do you optimize a slow-performing SQL query? Explain the role of indexes.

Group Discussion (Campus)

For campus placements, a group discussion may occur prior to technical and HR interviews.

What to demonstrate

• For campus placements, a group discussion may occur prior to technical and HR interviews
• Depth in Java (Core)

How to prepare

• Answer aloud and timed: What is the difference between the GROUP BY and HAVING clauses in SQL?
• Answer aloud and timed: Walk me through the architecture of a project you previously worked on. What were the main technical challenges, and how did you resolve them?

Technical and HR Interviews

Final interviews focusing on technical skills and cultural fit within the company.

What to demonstrate

• Final interviews focusing on technical skills and cultural fit within the company
• Depth in Java (Core)

How to prepare

• Answer aloud and timed: How would you design a system to handle real-time data feeds from multiple pharmaceutical distributors?
• Answer aloud and timed: Describe a scenario where a project requirement was ambiguous. How did you gather the necessary information to proceed with development?

Where candidates lose points

Clarify ambiguous requirements immediately

If a question or scenario presented by your interviewer seems unclear, do not hesitate to ask clarifying questions. This demonstrates strong communication and a methodical approach to problem-solving.

Brush up on your SQL Joins

Database queries are a staple of the technical evaluation. Practice writing queries that involve multiple joins, aggregations, and subqueries.

Prepare your project walk-throughs

Be ready to talk in detail about your past projects. Focus on the architectural decisions you made, the challenges you faced, and how your contributions impacted the business.

Align with Eversana's mission

Show that you understand the company's role in the life sciences sector. Expressing an interest in building software that improves patient care and commercial efficiency will resonate strongly with your interviewers.

Questions & practice

Write a program to sort an array of integers without using built-in library sorting methods.

Medium · Core Java & Object-Oriented Programming

Approach

1. Restate the input: its shape, its size, and what is guaranteed about it.
2. Name the brute-force solution and its complexity before improving on it.
3. Choose the data structure from the access pattern, not from familiarity.
4. 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?

Describe a scenario where a project requirement was ambiguous. How did you gather the necessary information to

Medium · Real-Time Scenarios & Project Requiremen

Describe a scenario where a project requirement was ambiguous. How did you gather the necessary information to proceed with development?

Approach

1. Restate the input: its shape, its size, and what is guaranteed about it.
2. Name the brute-force solution and its complexity before improving on it.
3. Choose the data structure from the access pattern, not from familiarity.
4. 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?

Find overlapping job attempts and peak concurrency from lease records

Medium · sweep line · intervals · leases

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?

Write a SQL query using different types of joins (inner, left, right, full) to combine patient and prescriptio

Medium · Relational Databases & SQL

Write a SQL query using different types of joins (inner, left, right, full) to combine patient and prescription records.

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?

What is database normalization, and why is it important in enterprise applications?

Medium · Relational Databases & SQL

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 a slow-performing SQL query? Explain the role of indexes.

Medium · Relational Databases & SQL

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?

What is the difference between the GROUP BY and HAVING clauses in SQL?

Medium · Relational Databases & SQL

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?

Explain the difference between String, StringBuilder, and StringBuffer in Java. When would you use each?

Medium · Core Java & Object-Oriented Programming

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 does exception handling work in Java? Describe the difference between checked and unchecked exceptions.

Medium · Core Java & Object-Oriented Programming

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?

Explain the concept of method overloading versus method overriding with real-world examples.

Medium · Core Java & Object-Oriented Programming

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?

What is the Java Collections Framework? How does a HashMap work internally?

Medium · Core Java & Object-Oriented Programming

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 the architecture of a project you previously worked on. What were the main technical challenge

Medium · Real-Time Scenarios & Project Requiremen

Walk me through the architecture of a project you previously worked on. What were the main technical challenges, and how did you resolve them?

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 would you design a system to handle real-time data feeds from multiple pharmaceutical distributors?

Medium · Real-Time Scenarios & Project Requiremen

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 ensure code quality and data security when integrating third-party healthcare APIs?

Medium · Real-Time Scenarios & Project Requiremen

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?

One log partition stops advancing while the others drain

Easy · poison message · head-of-line blocking · consumer lag

Search results for a subset of tenants are hours stale; the rest are current. The projection consumer reports lag of zero on 15 of 16 partitions and 400,000 on one. Its error rate is flat and its CPU is idle. outbox_event has no pending rows older than a second, so the relay has published everything it holds. Identify the mechanism, give the ordered checks, and state what you do in the first ten minutes versus what you change permanently.

Approach

1. Read the lag distribution first. A slow consumer lags everywhere; zero on fifteen partitions and 400,000 on one is not throughput. Idle CPU on the stuck partition means the consumer is not advancing its offset at all, which points at one message it cannot get past rather than at a rate problem.
2. Exonerate the producer before touching the consumer. No pending outbox rows older than a second means the relay published, so the event exists in the log. This separates never sent from sent and never applied, which are different code paths and usually different owners.
3. Read the message at the stuck offset and the handler's log lines for its event_id. A flat error rate with no progress has two explanations and you must distinguish them: the handler is throwing and the retry loop is swallowing it, or the handler is blocking on something and never returning. Idle CPU with no error lines favours the second.
4. Mitigate before diagnosing further. Move the offending event to a dead-letter store and commit the offset past it. Adding consumers does nothing here, because a partition is consumed by exactly one member of the group, and the blast radius is every aggregate hashed to that partition, not only the aggregate that produced the bad event.

Follow-up

• The dead-lettered event carried aggregate_version 7 and the projection had applied 6. What must the replay do differently if 8 and 9 landed in the meantime?
• How do you show staleness to the user while the partition is behind, given the API already returns the projection's watermark?

Suggested practice checklist

Built from the rounds and topics Eversana candidates report.

Day 1 — Map the Eversana loop

• Write out the reported sequence: HR Screening, Technical Screening, Project Discussions, Online Assessment (Campus), Group Discussion (Campus), Technical and HR Interviews.
• 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 6 reported rounds, with the weakest marked.

Day 2 — Work Java (Core)

• Spend the session on Java (Core), which Eversana candidates report being tested on.
• Write one worked example in Java (Core) and time yourself on it.

Deliverable: One timed worked example in Java (Core).

Day 3 — Work Sorting Algorithms (Arrays)

• Spend the session on Sorting Algorithms (Arrays), which Eversana candidates report being tested on.
• Write one worked example in Sorting Algorithms (Arrays) and time yourself on it.

Deliverable: One timed worked example in Sorting Algorithms (Arrays).

Day 4 — Work Problem Solving

• Spend the session on Problem Solving, which Eversana candidates report being tested on.
• Write one worked example in Problem Solving and time yourself on it.

Deliverable: One timed worked example in Problem Solving.

Day 5 — Answer out loud: Core Java & Object-Oriented Programming

• Answer aloud, timed: Write a program to sort an array of integers without using built-in library sorting methods.
• Answer aloud, timed: Explain the difference between String, StringBuilder, and StringBuffer in Java. When would you use each?

Deliverable: Spoken answers to 2 reported Core Java & Object-Oriented Programming question(s), under time.

Day 6 — Answer out loud: Relational Databases & SQL

• Answer aloud, timed: Write a SQL query using different types of joins (inner, left, right, full) to combine patient and prescription records.
• Answer aloud, timed: What is database normalization, and why is it important in enterprise applications?

Deliverable: Spoken answers to 2 reported Relational Databases & SQL question(s), under time.

Day 7 — Answer out loud: Real-Time Scenarios & Project Requirements

• Answer aloud, timed: Walk me through the architecture of a project you previously worked on. What were the main technical challenges, and how did you resolve them?
• Answer aloud, timed: How would you design a system to handle real-time data feeds from multiple pharmaceutical distributors?

Deliverable: Spoken answers to 2 reported Real-Time Scenarios & Project Requirements question(s), under time.

Behavioural preparation

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

Reverse your own decision and price the reversal

Medium · reversibility · measurement · migrations

Describe a technical decision you made and later reversed. Pick one that cost something: a service you split and merged back, a cache you added and removed, an index you created that pushed the planner onto a worse plan, a projection you rebuilt from scratch. State what you believed when you decided, the measurement that changed your mind, how long the wrong version ran in production, and what the reversal cost in migrations, dual writes, and a deprecation window for callers you did not own.

Approach

1. State the original rationale without irony, in the version you would still defend given what was known then. If it is not defensible, the story is about carelessness rather than judgement, and a different example serves you better.
2. Give the measurement that moved with a before and after: the p99 that did not improve, the cache hit rate that sat at 40%, the plan that flipped to a sequential scan once the table passed a size you can name.
3. Cost the reversal in steps, not adjectives: expand-and-contract deploys, the dual-write window, the callers who had to be notified, the rows already written in the wrong shape that had to be backfilled or abandoned.
4. Distinguish reversal from rewrite by naming what you kept. Most good reversals preserve the schema or the interface and undo one decision inside it, which is also why they were affordable.

Follow-up

• What in that decision was irreversible, and did you know it was irreversible when you made it?
• How did you tell the people who had already built on top of the original decision?

Unblock an engineer without taking the keyboard

Easy · mentoring · leases · at-least-once

A teammate has spent two days on a job handler that occasionally writes duplicate rows. They are certain the queue is delivering twice by mistake. You suspect a lease expiring under a slow handler, so the job is running concurrently with itself. Describe how you have unblocked someone in this position: what you asked before offering a hypothesis, what you showed them rather than told them, and what you left them owning. Then say what you would do if their theory turned out to be the right one.

Approach

1. Ask before diagnosing, and ask for things answerable from data they already have: the attempt count on the job rows that produced duplicates, the handler's observed duration against its lease expiry, and whether the duplicate rows share a natural key that a unique constraint could have caught.
2. Teach the shape rather than the answer. A lease cannot distinguish a dead worker from a slow one, so a handler that outruns its lease is running twice by design, and deploys deliver the other half by killing handlers mid-run on every rollout. Both of their candidate theories produce identical duplicate rows, which is why the evidence has to come from timings rather than from argument.
3. Hand over a checklist they execute: a natural key on every write the handler performs so the second copy collides rather than appends, the record of intent written before any external effect, a lease heartbeat while running, and the metric that shows it working.
4. Keep ownership with them deliberately. Pair on the first write, then step back; if you finish it yourself you have closed one ticket and left the same person stuck on the next redelivery.

Follow-up

• How would you distinguish a genuine double-delivery from a lease expiry using only the data already stored?
• Their handler calls an external endpoint before recording that it did. What do you tell them to change first?

Estimate work you have never done and defend the range

Hard · estimation · backfills · expand-contract

You are asked to estimate a change you have never attempted: add a column to a 100-million-row table, populate it, move reads across, and drop the old shape. Give a range with the assumptions that generate it, including batch size, the signal your backfill throttles on, and wall-clock hours, and name the three unknowns that would move the number most. Then describe a real estimate you gave under comparable ignorance: how you expressed its uncertainty, what you committed to, and how wrong you turned out to be.

Approach

1. Decompose into independently deployable steps before estimating anything: add the column nullable, write both shapes, backfill in batches, verify, move reads, stop writing the old shape, drop it. That is four deploys spread over days, and the calendar estimate is dominated by them rather than by the loop's runtime.
2. Do the arithmetic aloud for the part that has arithmetic in it: batch size times number of batches times per-batch duration, at a write rate the primary can absorb alongside roughly 1.2k writes per second of production traffic. The loop is throttled by replication lag and lock waits, not by how fast it can issue statements.
3. Price the schema step by its lock rather than its statement duration. In PostgreSQL an ALTER TABLE taking ACCESS EXCLUSIVE waits for every open transaction on that table while later queries queue behind it, so a millisecond change issued during a thirty-second analytics query stalls that table for thirty seconds. Adding a nullable column with a non-volatile default avoids a rewrite from version 11; a new index wants CREATE INDEX CONCURRENTLY, which cannot run inside a transaction block and leaves an invalid index behind if it fails.
4. Express the answer as a range whose endpoints each trace to a stated assumption, then name the cheapest experiment that collapses it, which is almost always running one real batch against the real table and multiplying.

Follow-up

• How do you verify the backfill genuinely finished, given rows written by production traffic while it ran?
• Where does the backfill resume from after a worker is killed mid-batch, and what makes that resume point trustworthy?