Eshares, Inc. Data Scientist interview typically runs 4 rounds: recruiter chat, hiring manager screen, take-home assignment, onsite loop. It usually takes a few weeks and can feel subjective, with leveling and decisions not always clearly explained.
$158K
Avg. Base Comp
$253K
Avg. Total Comp
4
Typical Rounds
3-5 weeks
Process Length
Our candidate experience suggests Eshares cares less about exotic modeling and more about whether you can speak confidently about experimentation, applied statistics, and product judgment. The technical questions reported were straightforward — OLS, A/B testing, and core experimentation concepts — but the evaluation felt more subjective than the questions themselves. That tells us the bar is not just correctness; it’s whether your thinking sounds crisp and immediately useful to a team shipping product in a regulated, trust-sensitive space.
A recurring theme is that the hiring manager’s read seems to carry outsized weight. One candidate described being downleveled without a clear explanation, and later learned that pausing to think before answering was viewed negatively. That’s an important signal: this process appears to reward fast, polished verbal delivery as much as analytical depth. We’ve seen that kind of dynamic trip up otherwise strong candidates who are used to taking a beat before responding.
The other non-obvious factor is transparency. The same candidate felt the process became frustrating once leveling changed midstream, which suggests Eshares may not always surface expectations early enough. Our read is that candidates do best when they proactively clarify scope and decision criteria before investing heavily, because the outcome may hinge on fit and communication style as much as technical substance.
Synthetized from 1 candidates 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 Eshares, Inc. process.
The process started with a recruiter chat, then a hiring manager screen, followed by a take-home assignment and an onsite loop. I was originally being considered for a manager role, but at some point I was downleveled to senior data scientist without a clear explanation, which was frustrating because I had already invested time before that became obvious. I still moved forward through the full process, but the lack of transparency set a weird tone early on.
The technical side was pretty focused on experimentation and applied stats. In the onsite, I was asked what OLS is and then got into A/B testing and experimentation questions. Those weren’t especially tricky on their own, but the process felt more subjective than technical overall. The bigger issue came from the behavioral side: I was later told that pausing to think before answering was a negative, and that ended up weighing heavily in the decision. I didn’t feel like that reflected the quality of my answers, just my style of thinking through responses.
In the end I was rejected, even though I got the sense that other interviewers were more positive. What stood out most was how much the outcome seemed to hinge on the hiring manager’s impression rather than a clearly explained rubric. If you interview here, I’d ask directly about leveling and how decisions are made before spending too much time on the take-home, and I’d be ready for fairly standard stats/experimentation questions like OLS and A/B testing.
Prep tip from this candidate
Be ready to explain OLS clearly and talk through A/B testing and experimentation concepts in a practical way. I’d also ask upfront how leveling decisions are made, since the role can be downleveled without much explanation before the take-home and onsite.
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 Eshares, Inc.
Describing a data project and its challenges
| Question | |
|---|---|
| Empty Neighborhoods | |
| 2nd Highest Salary | |
| Rolling Bank Transactions | |
| Top Three Salaries | |
| Customer Orders | |
| Comments Histogram | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Upsell Transactions | |
| Monthly Customer Report | |
| Experiment Validity | |
| First Touch Attribution | |
| First to Six | |
| Last Transaction | |
| Compute Deviation | |
| Bank Fraud Model | |
| Top 3 Users | |
| Download Facts | |
| Button AB Test | |
| Top 5 Turnover Risk | |
| String Shift | |
| Average Quantity | |
| 500 Cards | |
| Random SQL Sample | |
| Manager Team Sizes | |
| Unique Work Days | |
| Minimum Change | |
| Month Over Month |
Synthesized from candidate reports. Individual experiences may vary.
An initial conversation with recruiting to discuss the role, background, and fit. In this case, the candidate was first considered for a manager-level role before later being downleveled, so it’s worth clarifying leveling early.
A screen with the hiring manager to go deeper on experience and role fit. The process appeared to place significant weight on this stage, and the candidate felt the hiring manager’s impression strongly influenced the outcome.
A take-home exercise completed after the initial screens. The experience suggests this was a meaningful time investment, so candidates should ask about expectations and leveling before starting.
A series of interviews covering technical and behavioral evaluation. Technical questions focused on experimentation and applied statistics, including OLS and A/B testing, while the behavioral portion also factored into the final decision.