EVERSANA INTOUCH Software Engineer Interview Guide

The 60-second brief

A Software Engineer at EVERSANA INTOUCH plays a critical role in bridging the gap between cutting-edge technology and healthcare marketing. As a leading digital creative agency in the pharmaceutical and life sciences sectors, the company relies on its engineering team to build highly interactive web applications, digital campaign assets, and complex enterprise-level platforms. The solutions you build directly impact how patients, healthcare providers, and pharmaceutical brands communicate and share life-saving information. In this role, you will work in a fast-paced, highly collaborative environment alongside front-end architects, creative designers, copywriters, and project managers. Unlike traditional software environments where engineering is siloed, a Software Engineer at EVERSANA INTOUCH must possess a strong visual sensibility and a deep appreciation for user experience.

This guide is scoped to a Software Engineer candidate at EVERSANA INTOUCH.

Focus areas

• JavaScript
• HTML
• CSS

The EVERSANA INTOUCH interview process

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

HR Screen

Initial assessment of your background and general fit for the role.

What to demonstrate

• Initial assessment of your background and general fit for the role
• Depth in JavaScript

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 Panel

Deeper technical evaluation involving rapid-fire questions and a written or visual test.

What to demonstrate

• Deeper technical evaluation involving rapid-fire questions and a written or visual test
• Depth in JavaScript

How to prepare

• Answer aloud and timed: Explain the concept of event delegation in JavaScript and why you would use it.
• Answer aloud and timed: What are the different ways to handle asynchronous operations in JavaScript, and how do promises differ from async/await?

Final Conversation

Discussion with leadership to assess alignment with the company's collaborative culture.

What to demonstrate

• Discussion with leadership to assess alignment with the company's collaborative culture
• Depth in JavaScript

How to prepare

• Answer aloud and timed: How do you optimize a web page for performance and asset loading speed?
• Answer aloud and timed: Describe your typical process when taking a design mockup from a creative team and turning it into functional code.

Where candidates lose points

Master the fundamentals

Do not rely solely on your knowledge of frameworks like React or Angular. The technical panel will drill down into vanilla JavaScript, HTML structure, and core CSS behavior. Make sure you can write and explain raw code without framework-specific abstractions.

Spend time reviewing the nuances of CSS layout techniques

Be prepared to explain exactly how Flexbox and Grid behave, as layout precision is highly valued by the creative teams you will support.

Highlight your collaboration skills

Throughout your interviews, emphasize your experience working with creative designers, product managers, and QA specialists. Share concrete examples of how you negotiated technical constraints with creative teams to deliver a successful product.

Questions & practice

Explain the difference between block-level and inline elements in HTML.

Medium · Front-End Web Fundamentals

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?

What are the different ways to handle asynchronous operations in JavaScript, and how do promises differ from a

Medium · Front-End Web Fundamentals

What are the different ways to handle asynchronous operations in JavaScript, and how do promises differ from async/await?

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?

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

Easy · hashing · at-least-once · aggregation

You drain a batch of up to 5,000,000 events, each (aggregate_id BIGINT, aggregate_version INT, event_type, payload). The log guarantees order within one aggregate only; the batch merges 64 partitions, and a relay failover has redelivered a range, so an older version for an aggregate can appear after a newer one. Given a map of last_applied_version per aggregate, produce the events worth applying, at most one per (aggregate_id, version), plus the count discarded. Target O(n) time. State the memory for 2,000,000 distinct aggregates and what you do when it does not fit.

Approach

1. One pass, one hash map from aggregate_id to the highest version kept, and a discard counter. An event whose version is at or below last_applied_version for its aggregate is dropped without further work, which is the whole reason the event carries its version rather than a delta. O(n) expected time, O(d) space in distinct aggregates.
2. Keep the maximum, never the last occurrence. The redelivered range means the final appearance of an aggregate in the batch can be an older version than one seen earlier in the same batch, so last-wins applies stale state over newer state and the projection regresses with no error anywhere.
3. Cost the memory instead of calling it large: an 8-byte key plus a 4-byte version is 12 bytes of payload, and an open-addressed table held at a 0.7 load factor costs roughly 17 bytes per entry before per-slot metadata, so 2,000,000 aggregates is tens of megabytes in a native layout and several times that in a runtime that boxes both key and value.
4. If the distinct set exceeds memory, partition on hash(aggregate_id) mod P and reduce each partition independently. Every event for one aggregate hashes to the same partition, so the per-partition result is exact and the merge is concatenation rather than a second reduction.

Follow-up

• The payload is a patch rather than a snapshot, so applying only the highest version loses the intermediate changes. What changes in your reduction?
• How do you detect that version 7 arrived while version 6 was never delivered, and what should the consumer do about the gap?

Write the update path that detects a concurrent edit

Medium · optimistic concurrency · transactional outbox · audit history

resource carries version INT NOT NULL DEFAULT 1. resource_revision holds revision_id, resource_id, version, actor_user_id, change_kind, patch JSONB, request_id, created_at with UNIQUE (resource_id, version). outbox_event holds aggregate_type, aggregate_id, aggregate_version, event_type, payload, status. A PUT carries the version the client read. Write the exact statements for the single transaction that applies the edit, records the revision and enqueues 'resource.updated', and give the handler's branch on zero affected rows. Then say what PostgreSQL 16 does under READ COMMITTED when two of these updates hit one row at once.

Approach

1. One transaction, three writes, no network call inside it: UPDATE resource SET title = $3, version = version + 1, updated_at = now() WHERE resource_id = $1 AND tenant_id = $4 AND version = $2; then INSERT the resource_revision row at version $2 + 1; then INSERT the outbox_event row at the same aggregate_version. The event goes to a table rather than a broker because no transaction spans both.
2. Branch on the affected-row count before doing anything else. Zero has three causes — stale version, wrong tenant, row gone — so re-read once and map to 409 carrying the current version, or 404 for an id outside the caller's tenant, which also stops the endpoint confirming that another tenant's id exists.
3. State the engine behaviour instead of assuming it. Under READ COMMITTED the second UPDATE blocks on the row lock, and when the first commits PostgreSQL re-evaluates the WHERE clause against the newly committed row, so the version predicate now fails and the statement reports zero rows. Under REPEATABLE READ the identical collision raises SQLSTATE 40001 instead, so the handler must fold both shapes into one conflict response.
4. Keep UNIQUE (resource_id, version) even though the predicate already serialises writers. It is what makes a lost update unwritable if any other path ever reaches the revision table, and it converts a logic bug into 23505 rather than into a silently missing history row.

Follow-up

• A client sends the version it read ten minutes ago and the resource has moved three versions. What is in your 409 so it can resolve the conflict without a full re-fetch?
• Two editors, two disjoint fields, no overlap. Does your answer still refuse the second write, and should it?

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?

What is the CSS Box Model, and how does box-sizing: border-box change it?

Medium · Front-End Web Fundamentals

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 event delegation in JavaScript and why you would use it.

Medium · Front-End Web Fundamentals

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 do you optimize a web page for performance and asset loading speed?

Medium · Front-End Web Fundamentals

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?

Describe your typical process when taking a design mockup from a creative team and turning it into functional

Medium · Application Architecture & Process

Describe your typical process when taking a design mockup from a creative team and turning it into functional code.

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 cross-browser compatibility and responsive design across mobile, tablet, and desktop devices

Medium · Application Architecture & Process

How do you ensure cross-browser compatibility and responsive design across mobile, tablet, and desktop devices?

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?

What methodologies (like BEM or utility-first CSS) do you use to structure your stylesheets, and why?

Medium · Application Architecture & Process

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 state management in modern JavaScript frameworks?

Medium · Application Architecture & Process

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?

What tools and strategies do you use for debugging complex front-end issues?

Medium · Application Architecture & Process

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 EVERSANA INTOUCH candidates report.

Day 1 — Map the EVERSANA INTOUCH loop

• Write out the reported sequence: HR Screen, Technical Panel, Final Conversation.
• 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 3 reported rounds, with the weakest marked.

Day 2 — Work JavaScript

• Spend the session on JavaScript, which EVERSANA INTOUCH candidates report being tested on.
• Write one worked example in JavaScript and time yourself on it.

Deliverable: One timed worked example in JavaScript.

Day 3 — Work HTML

• Spend the session on HTML, which EVERSANA INTOUCH candidates report being tested on.
• Write one worked example in HTML and time yourself on it.

Deliverable: One timed worked example in HTML.

Day 4 — Work CSS

• Spend the session on CSS, which EVERSANA INTOUCH candidates report being tested on.
• Write one worked example in CSS and time yourself on it.

Deliverable: One timed worked example in CSS.

Day 5 — Answer out loud: Front-End Web Fundamentals

• Answer aloud, timed: Explain the difference between block-level and inline elements in HTML.
• Answer aloud, timed: What is the CSS Box Model, and how does box-sizing: border-box change it?

Deliverable: Spoken answers to 2 reported Front-End Web Fundamentals question(s), under time.

Day 6 — Answer out loud: Application Architecture & Process

• Answer aloud, timed: Describe your typical process when taking a design mockup from a creative team and turning it into functional code.
• Answer aloud, timed: How do you ensure cross-browser compatibility and responsive design across mobile, tablet, and desktop devices?

Deliverable: Spoken answers to 2 reported Application Architecture & Process question(s), under time.

Day 7 — Answer out loud: Behavioral & Culture Fit

• Answer aloud, timed: Tell me about a time you had to work with a non-technical stakeholder or designer who had unrealistic expectations. How did you handle it?
• Answer aloud, timed: Describe a project where you had to quickly learn a new technology or framework to deliver a feature.

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

Behavioural preparation

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

Tell me about a time you had to work with a non-technical stakeholder or designer who had unrealistic expectat

Medium · Behavioral & Culture Fit

Tell me about a time you had to work with a non-technical stakeholder or designer who had unrealistic expectations. How did you handle it?

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 project where you had to quickly learn a new technology or framework to deliver a feature.

Medium · Behavioral & Culture 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 or sudden shifts in project requirements?

Medium · Behavioral & Culture 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?

Why do you want to work in the pharmaceutical and healthcare marketing space at EVERSANA INTOUCH?

Medium · Behavioral & Culture 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?