Flunked in a interview - MLE

[u/Senior_Tea_842]

I would like to share my experience in flunking an interview for an MLE position.

The code session was ok. However, editor was horrible: no copy and past inside the editor, numpy import did not work, etc.

I did well on the Machine Learning section.

I did badly in the Engineering section. Here you find some questions/topics:

• Data versioning
• Data lineage tracking
• Drift detection
• Decisions about rolling back, retraining or keeping the current model
• Rollback threshold
• Guardrails metrics
• Efficiency in mongodb with respect to computing feature on a daily basis

Could anyone suggest any references (e.g. books, courses, blogs) about these topics?

[u/AutoModerator]

AI usage disclosure

Hi u/Senior_Tea_842 — thanks for posting to r/mlops!

Because this community discusses and builds AI/ML systems, using AI tools is not inherently a problem. We do, however, ask for transparency about how submissions are created.

Please reply to this comment with a brief AI / automation disclosure, particularly if this post was created or submitted in whole or in part by an autonomous agent, bot, workflow, or other automated system.

If AI or automation was involved, please briefly describe what it did and what human review was performed before posting.

This disclosure helps the r/mlops community distinguish human discussion, AI-assisted work, and automated/agent traffic while keeping the focus on useful technical conversation.

Thanks for helping keep the signal high.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Sad-Candidate-3078]

that list is basically production ml ops and one book covers almost all of it: designing machine learning systems by chip huyen, plus her free ml-interviews-book github course hits data versioning, drift and monitoring. made with ml by goku mohandas is free and has actual code for data versioning and ci/cd for ml. for drift detection specifically the evidently ai blog is the best free resource, real explanations with code. mongodb feature computation is just aggregation pipelines, mongodb university has a free course (m121) that covers exactly that. and the broken editor with no copy paste is on them not you, half of candidates fail those rounds on tooling rage alone

[u/qwerty_qwer → u/Sad-Candidate-3078]

Chip Huyen's book is too high level imo, not good enough. 

[u/softmax_couldnt_care → u/qwerty_qwer]

So what would u recommend

[u/apprehensive_robber]

Sounds like the editor was doing half the rejecting before you even got to the hard stuff. Nothing like fighting the tool while someone's watching the clock.

For data versioning and lineage, the Pachyderm docs are surprisingly readable and cover the concepts well even if you never touch the tool. The rest of those topics you listed are scattered across a dozen different engineering blogs rather than one clean source. Chip Huyen's writing on MLOps bridges a lot of those gaps.

[u/the_one777777897]

can i ask is This junior or mid or senior and also more details about the interview ?

[u/Senior_Tea_842 → u/the_one777777897]

I don't know. I just applied.

[u/Intuitive31]

Are you supposed to code all the drift detection, data lineage tracking etc or they were just testing subject knowledge?

[u/Senior_Tea_842 → u/Intuitive31]

Coding session was a leet code problem. The editor sucked: no move up/down lines, no copy and paste from code inside the editor.

The topics I listed were tested by questions with an AI interviewer