
One candidate describes a three-stage Celonis ML Engineer process: an HR call, a 40-minute hiring manager conversation, then a take-home technical challenge. They received no feedback afterward and no offer.
$162K
Avg. Base Comp
$195K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Celonis builds machine learning into its platform, and its ML engineers work on AI-powered product features. The interview experience we have for this role, from one candidate, is short and ends in a take-home. It began with a brief HR call covering introductions and background. Next came a roughly 40-minute conversation with the hiring manager, which stayed on general questions about the candidate's background and what they wanted in a new role.
The third stage was a take-home technical challenge. The candidate says they spent hours on it, and it appears to have been the main technical evaluation. After submitting, they say they got no feedback and no timeline, and follow-ups went unanswered. The outcome was no offer.
For preparation, expect to spend more effort on the take-home than on the earlier calls. Prepare a clear two-minute account of your background and why you want an ML role. Ask any clarifying questions about the challenge early, and keep your own notes on assumptions and results so you can explain them later. Because this is a single report, other candidates may see different formats, timelines, or levels of communication. The report names no specific ML topics, so review core machine learning fundamentals and be ready to present your work clearly.
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.
I went through the Celonis ML Engineer interview process and had a really frustrating experience overall. The first round was just a short call with HR—nothing intense, just standard introductions and a quick background chat. Then I had a 40-minute conversation with the hiring manager where they asked general questions about my background and what I was looking for in a new role. That part felt pretty standard, though I noticed the hiring manager seemed somewhat dismissive when I tried to ask clarifying questions.
The third round was where things fell apart. I was given a take-home technical challenge that I spent hours completing. I put real effort into it, but after submitting, I got absolutely nothing back—no feedback, no timeline, nothing. When I reached out multiple times asking for any kind of feedback or next steps, I was basically ghosted. The lack of communication and professionalism was shocking, especially after investing that much time. It felt like the hiring team didn't care about the candidate experience at all, which honestly soured me on the entire company.
Prep tip from this candidate
If you interview here, be prepared for a take-home challenge as the final round and don't expect feedback—set realistic expectations about communication. The process structure itself is straightforward (HR call, hiring manager chat, then a technical challenge), but the execution and follow-up are weak, so focus your energy on making your take-home submission as polished as possible since that's likely all they'll evaluate.
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
Given two sorted lists, write a function to merge them into one sorted list.
| Question | |
|---|---|
| Subscription Overlap | |
| First to Six | |
| Find the Missing Number | |
| String Shift | |
| Find Bigrams | |
| Scrambled Tickets | |
| Fair Coin | |
| P-value to a Layman | |
| Lasso vs Ridge | |
| Impression Reach | |
| Raining in Seattle | |
| Assumptions of Linear Regression | |
| Get Top N Frequent Words | |
| The Brackets Problem | |
| Priority Queue Using Linked List | |
| Bagging vs Boosting | |
| k-Means from Scratch | |
| Shortest Path Algorithms | |
| Duplicate Rows | |
| Bias vs. Variance Tradeoff | |
| LRU Cache 1 | |
| Median Probability | |
| Level Of Rain Water In 2D Terrain | |
| 500 Cards | |
| Optimal Host | |
| Random Forest from Scratch | |
| Type-ahead Search | |
| Random Forest Explanation | |
| Hurdles In Data Projects |
Synthesized from candidate reports. Individual experiences may vary.
The candidate describes the first stage as a short call with HR. It covered standard introductions and a quick chat about their background and was not intense. Typically, a stage like this checks fit and motivation, so have a concise account of your experience ready.
The candidate reports a conversation of about 40 minutes with the hiring manager. The questions were general, about their background and what they were looking for in a new role. They also felt the manager was somewhat dismissive of clarifying questions. You may want to prepare a clear career narrative and keep questions concise.
The candidate was given a take-home technical challenge as the third stage and says they spent hours on it. They report receiving no feedback, no timeline and no reply to repeated follow-ups, and the outcome was no offer. The report does not describe the task's content. Plan your time and document your reasoning.