
What to expect in a Celonis data scientist interview: one candidate's associate-level experience centered on a first-round project deep dive with scenario follow-ups, followed by a rejection that came without feedback.
$143K
Avg. Base Comp
$165K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
The one Celonis experience we have, from an associate data scientist candidate, describes a first round that was entirely a project discussion rather than a coding or technical screen. After a recruiter explained the process in advance, the interviewer asked the candidate to explain one project from start to finish. They then probed the implementation choices and posed scenario-based questions about what the candidate would do differently under other conditions.
That suggests choosing one project you know thoroughly and being ready to defend each decision: why you framed the problem as you did, which methods you used, and how your approach would change if the data, constraints or goals shifted. Practicing aloud with a friend who keeps asking "what if" is a sensible way to prepare.
The candidate left feeling confident and was told everything was good, but was later rejected with no feedback after following up with HR for three days. Expect that a polished walkthrough may not guarantee progress, so aim for clear reasoning, not just completeness.
Synthesized from 1 candidate report by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Celonis process.
The part I keep coming back to is that my entire first round was a project discussion, and I still can't tell what sank me. The recruiter had walked me through the process beforehand, so I knew this was coming. The interviewer asked me to explain one of my projects from start to finish. I did that, then went deeper into the implementation choices and worked through several scenario-based questions about how I'd handle things differently under other conditions. Near the end I asked whether there was anything I could improve. The interviewer said no, everything was good, and that I had answered all the questions. I left feeling confident.
Then came the silence. I followed up with HR for three days and was rejected with no feedback at all. I understand being turned down over weak technical or coding performance, since that's what you expect from a technical screen. But this round was entirely me talking through work I had done, and I answered everything I was asked. Without any signal, I can't tell whether the problem was the project itself, how I explained it, or something outside the interview. That uncertainty is the frustrating part, because it makes it hard to learn anything from the experience.
Prep tip from this candidate
Expect the first round to be a full project discussion, so prepare to walk through one project end-to-end and defend your implementation choices against scenario-based follow-ups. Since feedback may not come, go in ready to explain your reasoning clearly rather than assuming a confident answer will carry the round.
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 Celonis
How would you diagnose and speed up a slow SQL query when system metrics look healthy?
| Question | |
|---|---|
| Count Transactions | |
| Empty Neighborhoods | |
| 2nd Highest Salary | |
| Closest SAT Scores | |
| First to Six | |
| Upsell Transactions | |
| Longest Streak Users | |
| Merge Sorted Lists | |
| Comments Histogram | |
| Top Three Salaries | |
| Fair Coin | |
| Subscription Overlap | |
| Last Transaction | |
| Customer Orders | |
| Random SQL Sample | |
| Rolling Bank Transactions | |
| Impression Reach | |
| Raining in Seattle | |
| Monthly Customer Report | |
| Experiment Validity | |
| Top 5 Turnover Risk | |
| Button AB Test | |
| Employee Salaries (ETL Error) | |
| String Shift | |
| Find the Missing Number | |
| Find Bigrams | |
| 500 Cards | |
| Top 3 Users | |
| Download Facts |
Synthesized from candidate reports. Individual experiences may vary.
The candidate reports that a recruiter explained the process beforehand, so the project-focused format was not a surprise. Applicants may want to ask the recruiter what each stage covers and how long to prepare.
The candidate describes the entire first round as a project discussion. They explained one project end to end, went deeper into implementation choices, and answered several scenario-based questions on how they would handle things under different conditions. Prepare one project thoroughly and rehearse defending trade-offs.
The candidate asked the interviewer for improvement areas and was told everything was good. After three days of following up with HR, they were rejected without feedback. Applicants should expect that detailed feedback may not be provided and should plan to debrief their own performance after the interview.