eClerx Software Engineer Interview Guide

The 60-second brief

As a Software Engineer at eClerx, you serve as a critical technical architect and problem-solver within a global organization that specializes in data-driven solutions and business process management. You will work at the intersection of complex data ecosystems and scalable software development, contributing to platforms that drive efficiency and decision-making for some of the world’s largest brands. The role demands a balance of deep technical proficiency and an analytical mindset. You are not just writing code; you are building robust, maintainable systems that must perform under high-volume requirements. Whether you are working on automation, full-stack development, or specialized AI-driven solutions, your work directly impacts the operational success of our clients.

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

Focus areas

• Java
• OOPs / Object-Oriented Programming
• Logical Reasoning & Problem Solving

The eClerx interview process

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

Initial Screening

The process begins with an initial screening to assess candidate fit.

What to demonstrate

• The process begins with an initial screening to assess candidate fit
• 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 Assessments

Candidates undergo a series of technical assessments to evaluate their skills.

What to demonstrate

• Candidates undergo a series of technical assessments to evaluate their skills
• Depth in Java

How to prepare

• Answer aloud and timed: Write a SQL query to solve a complex data retrieval problem involving joins and aggregations.
• Answer aloud and timed: Solve a coding challenge such as "Trapping Rain Water" or "Calculating Highest Average Marks."

Face-to-Face/Virtual Interviews

Candidates participate in face-to-face or virtual interviews to discuss their experience and skills.

What to demonstrate

• Candidates participate in face-to-face or virtual interviews to discuss their experience and skills
• Depth in Java

How to prepare

• Answer aloud and timed: Explain how you optimize code for performance and memory constraints.
• Answer aloud and timed: Walk us through a project you led—what were the primary technical hurdles?

Technical Coding Tasks

Candidates complete technical coding tasks to demonstrate their coding abilities.

What to demonstrate

• Candidates complete technical coding tasks to demonstrate their coding abilities
• Depth in Java

How to prepare

• Answer aloud and timed: How do you handle debugging and troubleshooting in a production environment?
• Answer aloud and timed: If you have experience with Java, React, or Python, describe the most challenging feature you implemented.

System Design Discussions

Candidates engage in discussions about system design to showcase their architectural skills.

What to demonstrate

• Candidates engage in discussions about system design to showcase their architectural skills
• Depth in Java

How to prepare

• Answer aloud and timed: How do you approach designing a system from scratch (e.g., "Design a BookMyShow-like application")?
• Answer aloud and timed: What is your experience with automation, scraping, or data-driven software development?

Managerial Interviews

Candidates meet with managerial staff to evaluate cultural fit and collaboration skills.

What to demonstrate

• Candidates meet with managerial staff to evaluate cultural fit and collaboration skills
• Depth in Java

How to prepare

• Answer aloud and timed: Tell us about a time you had to learn a new technology quickly to meet a project deadline.
• Answer aloud and timed: How do you handle feedback from senior developers or project leads?

Where candidates lose points

Structure your answers

Use the STAR method (Situation, Task, Action, Result) for behavioral questions to keep your responses focused.

Be honest about your experience

If you don't know an answer, it is better to explain your logical approach to finding the answer than to guess.

Master your resume

Be prepared to explain every single project, technology, and tool you have listed in detail.

Research the domain

Understanding the industry eClerx serves can give you a significant edge in demonstrating how your work adds value.

Questions & practice

Explain the core concepts of Object-Oriented Programming (OOPs) and how you apply them in your projects.

Medium · Technical Fundamentals and Coding

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 the difference between list and tuple in Python, or explain specific Java memory management concepts.

Medium · Technical Fundamentals and Coding

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?

Solve a coding challenge such as "Trapping Rain Water" or "Calculating Highest Average Marks."

Medium · Technical Fundamentals and Coding

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?

Explain how you optimize code for performance and memory constraints.

Medium · Technical Fundamentals and Coding

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?

Write a SQL query to solve a complex data retrieval problem involving joins and aggregations.

Medium · Technical Fundamentals and Coding

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?

Keep soft-deleted accounts from blocking re-registration

Easy · soft delete · unique constraints · engine differences

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

1. 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.
2. 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.
3. 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.
4. 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?

Walk us through a project you led—what were the primary technical hurdles?

Medium · Project Experience and Domain Knowledge

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?

If you have experience with Java, React, or Python, describe the most challenging feature you implemented.

Medium · Project Experience and Domain Knowledge

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 approach designing a system from scratch (e.g., "Design a BookMyShow-like application")?

Medium · Project Experience and Domain Knowledge

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 handle debugging and troubleshooting in a production environment?

Medium · Project Experience and Domain Knowledge

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 eClerx candidates report.

Day 1 — Map the eClerx loop

• Write out the reported sequence: Initial Screening, Technical Assessments, Face-to-Face/Virtual Interviews, Technical Coding Tasks, System Design Discussions, Managerial 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

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

Deliverable: One timed worked example in Java.

Day 3 — Work OOPs / Object-Oriented Programming

• Spend the session on OOPs / Object-Oriented Programming, which eClerx candidates report being tested on.
• Write one worked example in OOPs / Object-Oriented Programming and time yourself on it.

Deliverable: One timed worked example in OOPs / Object-Oriented Programming.

Day 4 — Work Logical Reasoning & Problem Solving

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

Deliverable: One timed worked example in Logical Reasoning & Problem Solving.

Day 5 — Answer out loud: Technical Fundamentals and Coding

• Answer aloud, timed: Explain the core concepts of Object-Oriented Programming (OOPs) and how you apply them in your projects.
• Answer aloud, timed: Describe the difference between list and tuple in Python, or explain specific Java memory management concepts.

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

Day 6 — Answer out loud: Project Experience and Domain Knowledge

• Answer aloud, timed: Walk us through a project you led—what were the primary technical hurdles?
• Answer aloud, timed: How do you handle debugging and troubleshooting in a production environment?

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

Day 7 — Answer out loud: Behavioral and Situational

• Answer aloud, timed: Tell us about a time you had to learn a new technology quickly to meet a project deadline.
• Answer aloud, timed: How do you handle feedback from senior developers or project leads?

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

Behavioural preparation

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

What is your experience with automation, scraping, or data-driven software development?

Medium · Project Experience and Domain Knowledge

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 us about a time you had to learn a new technology quickly to meet a project deadline.

Medium · Behavioral and Situational

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 feedback from senior developers or project leads?

Medium · Behavioral and Situational

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 manage competing priorities.

Medium · Behavioral and Situational

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 are you interested in joining eClerx specifically?

Medium · Behavioral and Situational

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?