Read a machine learning job description critically

A title and tool list rarely tell you how the work is divided. Read the verbs, deliverables and operating expectations. Then turn ambiguity into questions for the recruiter or hiring team.

Extract signals and unknowns

The career evidence lab analyses an invented description.

from career_cases import job_description_case

result = job_description_case()
assert result["title_alone_sufficient"] is False
assert result["questions_to_ask"] == 4
print(result["signals"])
print(result["unknowns"])

“Own experimentation and evaluation” signals modelling responsibility. “Partner with platform engineers to deploy batch models” suggests shared production work. “Present uncertainty to operations” requires communication. The description still leaves on-call ownership, label availability, deployment frequency and decision authority unknown.

Build a responsibility table

Classify each sentence under problem framing, data engineering, analysis, modelling, software, deployment, operations, governance and stakeholder work. Mark the verb: contribute, build, own, lead or support. Identify the output—a notebook, decision memo, batch job, API, platform, experiment or dashboard.

Look for contradictions. A role asking one person to own exploratory research, 24/7 infrastructure, data-platform architecture and executive reporting may be intentionally broad or may lack clear support. “Production experience” can mean packaging a batch model or operating a high-availability service; ask which.

Ask evidence-seeking questions

• What decision does the team’s most recent model support?
• Who owns labels, feature pipelines, release approval and incidents?
• How often do models reach production, and what blocks them?
• Which baseline and evaluation gate must a candidate beat?
• What does success in the first 90 days produce?

Compare answers with your preferred work and current evidence. Do not keyword-match every listed library. Identify transferable skills and the few gaps central to actual ownership. Treat years-of-experience and education requirements as employer criteria to clarify, not evidence you should misrepresent experience.

The Data Science course builds evidence across modelling and basic deployment. Individual job fit still depends on the current vacancy, prior experience and demonstrated depth.

Exercise

Annotate five current descriptions from your target market. Summarize the median task mix without claiming the sample represents the whole market. Choose one portfolio artifact that answers each recurring responsibility and list the questions that remain.

Continue learning

This article is part of the Data science careers and portfolio decisions sequence. Use the neighbouring tasks when you need the prerequisite or the next application.

• Review the prerequisite or neighbouring task in Present an unsuccessful model project as honest learning.
• Continue with Build a portfolio evidence index for interviewers.

Reference: O*NET Data Scientists occupation profile.