Senior Machine Learning Engineer
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to parse the posting.
First, there is "About The Team" which is not a heading we need? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only include those headings if they have content. "About The Team" is not in list, but could be considered "About the role"? Actually there is "About The Role" heading in posting. So we will create About the role
and put the prose under it.
We need to separate responsibilities, requirements, qualifications, skills, benefits, pay, schedule.
Let's extract.
Posting sections:
- About The Team (maybe not needed)
- About The Role (description)
- You Will (list of responsibilities)
- You Have (list of requirements/qualifications/skills)
- Our Benefits (list)
- Learn More About Us And Our Benefits Click Here. (maybe ignore)
- Equal Opportunity Employer ... (boilerplate remove)
- Reasonable Accommodation ... (remove)
- Business Area: Dow Jones - Technology Job Category: Software Product Engineering Union Status Union role Base Pay Range: $125,000 - $155,000 ... (pay info)
- Then more description about compensation, benefits, company description (maybe ignore as boilerplate? but we need to preserve substantive info; but these are generic company description maybe not needed? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description maybe not required. However "Learn More About Us And Our Benefits Click Here." is likely a link, we can drop. The company description may be considered boilerplate? Not sure. It's not EEO but it's generic about the company. Might be considered not required. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The company description is substantive? It's about the company, not the role. Might be considered not needed for job posting? Usually we keep it? The instruction didn't explicitly say to drop company description. It says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we can keep the company description if it's not boilerplate. However it's fairly generic but still substantive about the employer. Might keep as a paragraph under maybe "About the team"? But we already have About The Team earlier. That is substantive about the team. We could keep that as a paragraph under maybe a heading? Not in list. But we could treat "About The Team" as a section heading? Not in allowed headings list. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use for section headings (e.g. those). Likely they expect only those headings. So we should not output a heading for About The Team. Instead we could fold its content into a
About the role
and put the prose under it. We need to separate responsibilities, requirements, qualifications, skills, benefits, pay, schedule. Let's extract. Posting sections: - About The Team (maybe not needed) - About The Role (description) - You Will (list of responsibilities) - You Have (list of requirements/qualifications/skills) - Our Benefits (list) - Learn More About Us And Our Benefits Click Here. (maybe ignore) - Equal Opportunity Employer ... (boilerplate remove) - Reasonable Accommodation ... (remove) - Business Area: Dow Jones - Technology Job Category: Software Product Engineering Union Status Union role Base Pay Range: $125,000 - $155,000 ... (pay info) - Then more description about compensation, benefits, company description (maybe ignore as boilerplate? but we need to preserve substantive info; but these are generic company description maybe not needed? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description maybe not required. However "Learn More About Us And Our Benefits Click Here." is likely a link, we can drop. The company description may be considered boilerplate? Not sure. It's not EEO but it's generic about the company. Might be considered not required. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The company description is substantive? It's about the company, not the role. Might be considered not needed for job posting? Usually we keep it? The instruction didn't explicitly say to drop company description. It says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we can keep the company description if it's not boilerplate. However it's fairly generic but still substantive about the employer. Might keep as a paragraph under maybe "About the team"? But we already have About The Team earlier. That is substantive about the team. We could keep that as a paragraph under maybe a heading? Not in list. But we could treat "About The Team" as a section heading? Not in allowed headings list. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use for section headings (e.g. those). Likely they expect only those headings. So we should not output a heading for About The Team. Instead we could fold its content into a
under maybe no heading? But we need to output only HTML fragment; we could just put a
with that content at start. However they said "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can have a
for About The Team content. Thus structure:
About The Team Our Technology team drives the evolution of our Technology, Engineering, Data, Product and User Experience functions. With a keen focus on delivering cutting-edge solutions, we shape the digital landscape for our customers, readers and users. From revolutionizing visuals to optimizing tools and harnessing the power of data, mobile, video and social platforms, our team is committed to providing a seamless and immersive experience across all touchpoints. Collaborating closely with our newsrooms and strategic partners, we spearhead the development of groundbreaking products and technologies.
ThenAbout the role
with the paragraph: "As Senior Machine Learning Engineer in the AI & ML foundations team, you will design and build the core systems behind our LLM applications: the orchestration layer, the reusable tooling and the evaluation harness that keeps it trustworthy in production. In this role, you will not be applying AI research or model training - but to real problems in production. You will report to the Director, Data Science & Insights." Then responsibilities: list underResponsibilities
with- items from "You Will". Those bullet points:
- Design and build the orchestration, prompting, and workflow layers behind production AI features
- Create composable tools and integrations, including retrieval and MCP servers and clients
- Build evaluators, dashboards, and alerts that track accuracy, latency, cost, and hallucination
- Harden the platform for production scale: caching, reliability, incidents, and model rollbacks
- Set the technical bar through architecture decisions, design reviews, and mentoring
Then requirements/qualifications/skills: The "You Have" list includes many items. We need to decide how to split into Requirements, Qualifications, Skills. The instruction: prefer a few substantive sections over many thin ones. Could combine into one section like "Requirements" or "Qualifications". But we have headings for Requirements, Qualifications, Skills. We could put all under
Requirements
as a list. Or split: Requirements (experience), Qualifications (education?), Skills (technical). But we don't have explicit education. So maybe just one section "Requirements". However we have also "Skills" heading available. Could put technical skills under Skills, and experience under Requirements. Let's parse: You Have: - At least 2+ years’ experience in software/ML engineering - which includes at least 1 years’ experience building LLM systems in production - Expert Python, hands on with LLM APIs and cloud platforms (AWS, Snowflake, Vertex) - Deep experience orchestrating multistep LLM workflows as execution graphs (e.g. LangChain/LangGraph). - Experience building agent harnesses: memory compression, skill disclosure, and tool design - Strong prompt engineering: tuning, versioning, and evaluation of prompts and model configs - A proven track record in AI evaluation, observability, and retrieval over enterprise data - Ability to explain complex AI concepts and tradeoffs clearly to nontechnical stakeholders - Fluency with agentic coding tools (e.g. Claude Code) and their architecture patterns (a strong plus) We could treat first bullet as Requirements (experience). Others as Skills. Or we could have Requirements (experience + proven track record) and Skills (technical). But to keep simple, we can have one sectionRequirements
with all bullets. Benefits: list underBenefits
with bullets from "Our Benefits". Items: - Comprehensive Healthcare Plans - Paid Time Off - Retirement Plans - Comprehensive Insurance Plans - Lifestyle Programs & Wellness Resources - Education Benefits - Family Care Benefits & Caregiving Support - Commuter Transit Program - Subscription Discounts - Employee Referral Program - Financial Health Programs - Cybersecurity Protection Pay: we have Base Pay Range: $125,000 - $155,000 plus description about compensation. So we should createPay
with a paragraph: "Base Pay Range: $125,000 - $155,000. We’re committed to offering competitive and flexible compensation to attract top talent. This pay range reflects our good faith estimate for the role and may vary based on a candidate’s experience, skills, location, and other relevant factors. For bonus-eligible roles, targets are determined based on multiple considerations, including market benchmarks and individual contributions." Schedule: not mentioned. So we omit Schedule section. Also we have "Business Area: Dow Jones - Technology Job Category: Software Product Engineering Union Status Union role". This is metadata; we can fold into a shortmaybe after benefits or before pay. The instruction: fold minor metadata into a short
or drop it. So we can add a
with that line. Also there is "Learn More About Us And Our Benefits Click Here." which is likely a link; we can drop as application instruction? It's not exactly application instruction but maybe a call to action. Could drop. We also have boilerplate about Equal Opportunity Employer etc. Remove. Now produce HTML fragment. We need to ensure we don't include any markdown fences. Let's craft:
About The Team Our Technology team drives the evolution of our Technology, Engineering, Data, Product and User Experience functions. With a keen focus on delivering cutting-edge solutions, we shape the digital landscape for our customers, readers and users. From revolutionizing visuals to optimizing tools and harnessing the power of data, mobile, video and social platforms, our team is committed to providing a seamless and immersive experience across all touchpoints. Collaborating closely with our newsrooms and strategic partners, we spearhead the development of groundbreaking products and technologies.
About the role
As Senior Machine Learning Engineer in the AI & ML foundations team, you will design and build the core systems behind our LLM applications: the orchestration layer, the reusable tooling and the evaluation harness that keeps it trustworthy in production. In this role, you will not be applying AI research or model training - but to real problems in production. You will report to the Director, Data Science & Insights.
Responsibilities
- Design and build the orchestration, prompting, and workflow layers behind production AI features
- Create composable tools and integrations, including retrieval and MCP servers and clients
- Build evaluators, dashboards, and alerts that track accuracy, latency, cost, and hallucination
- Harden the platform for production scale: caching, reliability, incidents, and model rollbacks
- Set the technical bar through architecture decisions, design reviews, and mentoring
Requirements
- At least 2+ years’ experience in software/ML engineering - which includes at least 1 years’ experience building LLM systems in production
- Expert Python, hands on with LLM APIs and cloud platforms (AWS, Snowflake, Vertex)
- Deep experience orchestrating multistep LLM workflows as execution graphs (e.g. LangChain/LangGraph)
- Experience building agent harnesses: memory compression, skill disclosure, and tool design
- Strong prompt engineering: tuning, versioning, and evaluation of prompts and model configs
- A proven track record in AI evaluation, observability, and retrieval over enterprise data
- Ability to explain complex AI concepts and tradeoffs clearly to nontechnical stakeholders
- Fluency with agentic coding tools (e.g. Claude Code) and their architecture patterns (a strong plus)
Benefits
- Comprehensive Healthcare Plans
- Paid Time Off
- Retirement Plans
- Comprehensive Insurance Plans
- Lifestyle Programs & Wellness Resources
- Education Benefits
- Family Care Benefits & Caregiving Support
- Commuter Transit Program
- Subscription Discounts
- Employee Referral Program
- Financial Health Programs
- Cybersecurity Protection
Business Area