Candidates for eClerx analyst roles describe an aptitude test, an HR conversation, and an operations or manager round heavy on finance. One candidate also reports a Python scraping assessment.
$125K
Avg. Base Comp
$140K
Avg. Total Comp
3-5 rounds
Typical Rounds
Not reported
Process Length
Candidates who interviewed for eClerx analyst and senior analyst roles describe a process that tests more than data skills. Across five reports, an aptitude test comes up repeatedly, with one candidate describing verbal ability, logical reasoning and English sections. One candidate called it complicated and another called it relentless in pace.
The manager or operations round is where finance knowledge appears. Candidates report questions on capital markets, derivatives, futures, forwards, swaps, the trade lifecycle, and primary versus secondary markets. One candidate was also asked about financial ratios, accounting golden rules and types of financial assets. Two candidates mention riddles or logic puzzles, so practice reasoning aloud. One of them said confidence in explaining answers mattered as much as correctness.
Technical coding was reported by only one Senior Analyst candidate. That person had about an hour to scrape a live website in Python using Beautiful Soup and lxml. Treat this as a possibility for some teams and not as a standard step. Other reports describe HR and manager conversations about motivation, background and willingness to relocate.
Outcomes were mixed: three of five candidates received offers. One candidate who cleared three rounds was called back for an extra interview after being asked for offer documents, and was then rejected. Another reported about three months from interview to final outcome, so ask the recruiter about timing and stay engaged until you sign.
Synthesized from 5 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the eClerx process.
I interviewed at eClerx for a Senior Analyst role, and the process was pretty comprehensive. They started with a group discussion round, which caught me off guard—I wasn't expecting that format for a data analyst position. The GD was straightforward, just assessing how I communicated ideas in a group setting.
After that came an HR round, which was pretty standard: they asked about my background, why I was interested in the role, and what I was looking for in my next position. The manager round followed, and that's where the finance domain knowledge really mattered. They dug into questions about capital markets, derivatives, the trade lifecycle, and primary versus secondary markets. I realized going in that this role had a strong financial services component, not just pure data work.
The toughest part was the assessment. They had me write actual code—specifically Python web scraping using Beautiful Soup and lxml. I was given about an hour to scrape data from a live website and handle the code properly. That was technical and time-pressured, and it was definitely the part that separated people. They wanted to see if I could actually code and handle libraries I might not have used in a while.
One thing that surprised me: they also ran an aptitude test before the technical rounds, which I didn't expect. Overall, the process was structured but not overly complicated. Be ready for both domain knowledge on finance topics and practical coding skills.
Prep tip from this candidate
Focus on Python web scraping libraries—specifically Beautiful Soup and lxml—and be ready to write working code under time pressure. Also brush up on financial domain basics: capital markets, derivatives, options, trade lifecycle, and mutual funds, since those came up heavily in behavioral and manager rounds.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at eClerx
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Top Three Salaries | |
| Employee Salaries | |
| First to Six | |
| Longest Streak Users | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Top 3 Users | |
| Comments Histogram | |
| Closest SAT Scores | |
| Last Transaction | |
| Random SQL Sample | |
| Paired Products | |
| Find the Missing Number | |
| Employee Salaries (ETL Error) | |
| Size of Joins | |
| Monthly Customer Report | |
| Largest Salary by Department | |
| Lowest Paid | |
| Experiment Validity | |
| Download Facts | |
| Prime to N | |
| First Touch Attribution | |
| Fair Coin | |
| Upsell Transactions | |
| Button AB Test | |
| Assumptions of Linear Regression | |
| 500 Cards | |
| Duplicate Rows |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an aptitude test, described by one as covering verbal ability, logical reasoning and English. Its placement varies. One candidate took it online first, one says it was the final round, and another took it before the technical rounds. One called it complicated, so timed reasoning practice is sensible.
Candidates typically describe an HR or screening call about their background, why eClerx, and what they want next. One candidate without a finance background was asked why they were drawn to the role and was given puzzles. Prepare a specific, credible reason for choosing eClerx and this role.
Several candidates report that this round covers capital markets, derivatives, futures, forwards, swaps and the trade lifecycle. One also reports financial ratios, accounting golden rules and types of financial assets. Some mention riddles, relocation questions and interviewers looking for confident articulation. Expect domain depth beyond pure data work.
One Senior Analyst candidate reports an hour-long Python web scraping task using Beautiful Soup and lxml on a live website. The same candidate also reports a group discussion round. Another was called back for an additional manager interview after being asked for offer documents. These may not apply to every team or role.
