Senior Machine Learning Engineer, Data Infrastructure
Unity · Bellevue, WA · 1 mo ago
Engineering$210k–$273k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes description. We need headings for sections present: About the role? The posting includes "The Role" and "What You’ll Do", "What We’re Looking For", "Additional Information" (includes pay range), "Benefits", "Life at Unity". Also maybe "About the role" not present. We'll include sections where there is real content.
We must not repeat job title. No Job ID. Remove boilerplate: EEO, equal opportunity, scam warning, application instructions, privacy policies, etc. Also remove duplicated lines (the Additional Information paragraph repeated). We'll keep pay range once. Benefits section: we have description of benefits. Keep that.
We need to use for section headings. Use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. So we need to include details from each section.
Let's extract content:
Intro paragraph: "Unity Vector builds an Data platform that powers insight, experimentation, attribution, and AI-driven decision-making across the company. Our systems operate at scale across batch and streaming data, supporting analytics, product intelligence, machine learning pipelines, and business operations. As data volume and complexity grow, our platform also supports large-scale model training, feature generation, and experimentation workflows that power production ML systems. To support this growth, we need strong technical ownership to ensure our ML pipelines remain reliable, scalable, and architecturally sound."
That's about the role? Could be "About the role" or maybe we can put under a heading "About the role". The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use About the role for that intro.
Then "The Role" heading: we could treat as "About the role" already covered; but we have "The Role We are seeking a senior data infra engineer to design and evolve the large-scale offline platform. This role focuses on building reliable infrastructure for generating data infrastructure, training datasets, and orchestrating data workflows. You will work closely with ML engineers and platform teams to ensure our pipelines can efficiently handle growing data volumes and increasingly complex training workloads. You will play a key role in shaping how model datasets are prepared to ensure the reliability, scalability, and performance of our data platform."
That's more detail; could be part of About the role. But we can keep as separate section maybe "About the role". However we should not duplicate. Let's combine into About the role: include both paragraphs.
Then "What You’ll Do" is responsibilities. Use heading Responsibilities? Actually they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map:
- About the role: intro + The Role description.
- Responsibilities: "What You’ll Do" bullet list (though it's sentences). We'll convert each sentence into
- .
- Requirements: "What We’re Looking For" bullet list.
- Qualifications? Not separate; maybe combine with Requirements. But we could have Requirements and Qualifications separate if content distinct. The posting only has "What We’re Looking For". Could treat as Requirements. Qualifications maybe not present; we should not create empty section.
- Skills: maybe not separate; could be part of Requirements. We'll not create Skills if no explicit list.
- Benefits: we have Benefits section.
- Pay: we have Additional Information with pay ranges. We'll create Pay section.
- Schedule: not present; omit.
Also we may have "Life at Unity" maybe could be About the company but not required heading; we could omit or put under About the role? Probably omit as not in list. But we must preserve all substantive information; we could include as a paragraph under About the role or separate section not in list? The instruction says use those headings for section headings (e.g...). It doesn't forbid other headings, but says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings when appropriate. Could also add other headings if needed but better to stick to those. Life at Unity could be considered "About the role"? Not really. Could be omitted? But we must preserve ALL substantive information. So we need to include that info somewhere. Could add a section "About Unity" but not in list. Might be okay to add a heading like "About Unity" but the instruction says use those headings for section headings (e.g...). It doesn't forbid other headings, but says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. However Life at Unity is substantive; we could incorporate it into About the role as a paragraph about company. That would preserve info.
Similarly, the duplicated Additional Information paragraph we need to include only once.
Now we need to remove boilerplate: EEO, equal opportunity, scam warning, application instructions, privacy policies, headhunter stuff, etc.
Let's extract Benefits paragraph: "Benefits At Unity, we want our team members to thrive. We offer a wide range of benefits designed to support well-being and work-life balance. Please note: Benefits eligibility, specific offerings, and coverage vary based on the country and employment status. While specific benefits vary, here are some of the ways we strive to take care of our eligible team members globally: Comprehensive health, life, and disability insurance | Commute subsidy | Employee stock ownership | Competitive retirement/pension plans | Generous vacation and personal days | Support for new parents through leave and family-care programs | Office food snacks | Mental Health and Wellbeing programs and support | Employee Resource Groups | Global Employee Assistance Program | Training and development programs | Volunteering and donation matching program"
We need to turn that list into - . The list separated by |. We'll split.
Now Pay section: include the pay ranges and note about equity awards etc. The Additional Information includes repeated paragraph; we need to include once.
Let's capture: "Zone A: $210,300 - $273,400 Zone B: $187,200 - $243,300 Zone C: $165,600 - $215,200 This range reflects the anticipated base salary for this position. Beyond base salary, this role may be eligible for equity awards and participation in our company incentive plans (such as annual discretionary bonuses or sales commissions). The final offer amount will depend on several factors, including geographic location and the candidate’s relevant experience, professional background, and skill set."
We should not repeat the sentence twice.
Now Responsibilities: list each bullet from "What You’ll Do". The text:
"Develop infrastructure that supports both batch and stream big data processing using technologies such as Flink, Spark, Ray, etc.
Design and operate large-scale data pipelines that generate training datasets used for machine learning training and experimentation
Integrate data pipelines with workflow orchestration systems (e.g., Flyte, Airflow, or similar) to enable reliable multi-stage training workflows
Improve reproducibility and observability of data pipelines through dataset validation, monitoring, and automated testing
Optimize performance and resource utilization across distributed compute systems used for data processing
Partner closely with ML engineers to enable efficient large-scale experimentation and model iteration
Lead architectural improvements to ensure our offline data pipelines remain scalable, reliable, and cost-efficient"
We'll make each as
- .
Requirements: "What We’re Looking For" list:
"Experience working with distributed computing frameworks such as Flink, Spark, Ray for distributed data processing
Experience building infrastructure for training data generation, dataset preparation, or ML feature pipelines
Experience optimizing big data pipelines and infrastructure for cost efficiency
Strong programming skills in Python and experience working with large-scale distributed workloads
Experience with modern data infrastructure (data lakes, warehouses, orchestration systems, streaming platforms)
Strong systems thinking, with the ability to reason about performance, scalability, reliability, and cost tradeoffs in distributed systems
Proven ability to lead technical direction and influence architectural decisions across teams without formal authority"
We'll make each
- .
Now About the role: combine intro paragraph and The Role paragraph.
Let's craft:
Intro: "Unity Vector builds a data platform that powers insight, experimentation, attribution, and AI-driven decision-making across the company. Our systems operate at scale across batch and streaming data, supporting analytics, product intelligence, machine learning pipelines, and business operations. As data volume and complexity grow, our platform also supports large-scale model training, feature generation, and experimentation workflows that power production ML systems. To support this growth, we need strong technical ownership to ensure our ML pipelines remain reliable, scalable, and architecturally sound."
The Role paragraph: "We are seeking a senior data infra engineer to design and evolve the large-scale offline platform. This role focuses on building reliable infrastructure for generating data infrastructure, training datasets, and orchestrating data workflows. You will work closely with ML engineers and platform teams to ensure our pipelines can efficiently handle growing data volumes and increasingly complex training workloads. You will play a key role in shaping how model datasets are prepared to ensure the reliability, scalability, and performance of our data platform."
Combine into About the role section.
Now we need to output only HTML fragment, no markdown fences.
We'll produce:
About the role
...
...
Responsibilities
- ...
...
Requirements
...
Benefits
Benefits At Unity, we want our team members to thrive. We offer a wide range of benefits designed to support well-being and work-life balance. Please note: Benefits eligibility, specific offerings, and coverage vary based on the country and employment status.
- Comprehensive health, life, and disability insurance
- Commute subsidy
- Employee stock ownership
- Competitive retirement/pension plans
- Generous vacation and personal days
- Support for new parents through leave and family-care programs
- Office food snacks
- Mental Health and Wellbeing programs and support
- Employee Resource Groups
- Global Employee Assistance Program
- Training and development programs
- Volunteering and donation matching program
Pay
Zone A: $210,300 - $273,400 Zone B: $187,200 - $243,300 Zone C: $165,600 - $215,200 This range reflects the anticipated base salary for this position. Beyond base salary, this role may be eligible for equity awards and participation in our company incentive plans (such as annual discretionary bonuses or sales commissions). The final offer amount will depend on several factors, including geographic location and the candidate’s relevant experience, professional background, and skill set.
We should ensure no duplicate sentences.
Check for any leftover boilerplate: we removed EEO, equal opportunity, scam warning, application instructions, privacy, headhunter, etc.
We kept Life at Unity? Not included. We could incorporate into About the role as an extra paragraph after The Role? Might be good to add a paragraph about Unity. Let's add a paragraph: "Life at Unity Unity [NYSE: U] is the world’s leading game engine, powering play for more than 3 billion consumers each month. The top mobile games in the world, the most played PC indie titles, the most innovative console games, and virtually all of the top XR and Web Games are developed, deployed, and grown in Unity. Unity also enables teams across industries like automotive, manufacturing, and healthcare to design, simulate
for prose. We must preserve all substantive information, not invent or summarize away detail. So we need to include details from each section. Let's extract content: Intro paragraph: "Unity Vector builds an Data platform that powers insight, experimentation, attribution, and AI-driven decision-making across the company. Our systems operate at scale across batch and streaming data, supporting analytics, product intelligence, machine learning pipelines, and business operations. As data volume and complexity grow, our platform also supports large-scale model training, feature generation, and experimentation workflows that power production ML systems. To support this growth, we need strong technical ownership to ensure our ML pipelines remain reliable, scalable, and architecturally sound." That's about the role? Could be "About the role" or maybe we can put under a heading "About the role". The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use About the role for that intro. Then "The Role" heading: we could treat as "About the role" already covered; but we have "The Role We are seeking a senior data infra engineer to design and evolve the large-scale offline platform. This role focuses on building reliable infrastructure for generating data infrastructure, training datasets, and orchestrating data workflows. You will work closely with ML engineers and platform teams to ensure our pipelines can efficiently handle growing data volumes and increasingly complex training workloads. You will play a key role in shaping how model datasets are prepared to ensure the reliability, scalability, and performance of our data platform." That's more detail; could be part of About the role. But we can keep as separate section maybe "About the role". However we should not duplicate. Let's combine into About the role: include both paragraphs. Then "What You’ll Do" is responsibilities. Use heading Responsibilities? Actually they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: - About the role: intro + The Role description. - Responsibilities: "What You’ll Do" bullet list (though it's sentences). We'll convert each sentence into
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings when appropriate. Could also add other headings if needed but better to stick to those. Life at Unity could be considered "About the role"? Not really. Could be omitted? But we must preserve ALL substantive information. So we need to include that info somewhere. Could add a section "About Unity" but not in list. Might be okay to add a heading like "About Unity" but the instruction says use those headings for section headings (e.g...). It doesn't forbid other headings, but says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. However Life at Unity is substantive; we could incorporate it into About the role as a paragraph about company. That would preserve info.
Similarly, the duplicated Additional Information paragraph we need to include only once.
Now we need to remove boilerplate: EEO, equal opportunity, scam warning, application instructions, privacy policies, headhunter stuff, etc.
Let's extract Benefits paragraph: "Benefits At Unity, we want our team members to thrive. We offer a wide range of benefits designed to support well-being and work-life balance. Please note: Benefits eligibility, specific offerings, and coverage vary based on the country and employment status. While specific benefits vary, here are some of the ways we strive to take care of our eligible team members globally: Comprehensive health, life, and disability insurance | Commute subsidy | Employee stock ownership | Competitive retirement/pension plans | Generous vacation and personal days | Support for new parents through leave and family-care programs | Office food snacks | Mental Health and Wellbeing programs and support | Employee Resource Groups | Global Employee Assistance Program | Training and development programs | Volunteering and donation matching program"
We need to turn that list into - . The list separated by |. We'll split.
Now Pay section: include the pay ranges and note about equity awards etc. The Additional Information includes repeated paragraph; we need to include once.
Let's capture: "Zone A: $210,300 - $273,400 Zone B: $187,200 - $243,300 Zone C: $165,600 - $215,200 This range reflects the anticipated base salary for this position. Beyond base salary, this role may be eligible for equity awards and participation in our company incentive plans (such as annual discretionary bonuses or sales commissions). The final offer amount will depend on several factors, including geographic location and the candidate’s relevant experience, professional background, and skill set."
We should not repeat the sentence twice.
Now Responsibilities: list each bullet from "What You’ll Do". The text:
"Develop infrastructure that supports both batch and stream big data processing using technologies such as Flink, Spark, Ray, etc.
Design and operate large-scale data pipelines that generate training datasets used for machine learning training and experimentation
Integrate data pipelines with workflow orchestration systems (e.g., Flyte, Airflow, or similar) to enable reliable multi-stage training workflows
Improve reproducibility and observability of data pipelines through dataset validation, monitoring, and automated testing
Optimize performance and resource utilization across distributed compute systems used for data processing
Partner closely with ML engineers to enable efficient large-scale experimentation and model iteration
Lead architectural improvements to ensure our offline data pipelines remain scalable, reliable, and cost-efficient"
We'll make each as
- .
Requirements: "What We’re Looking For" list:
"Experience working with distributed computing frameworks such as Flink, Spark, Ray for distributed data processing
Experience building infrastructure for training data generation, dataset preparation, or ML feature pipelines
Experience optimizing big data pipelines and infrastructure for cost efficiency
Strong programming skills in Python and experience working with large-scale distributed workloads
Experience with modern data infrastructure (data lakes, warehouses, orchestration systems, streaming platforms)
Strong systems thinking, with the ability to reason about performance, scalability, reliability, and cost tradeoffs in distributed systems
Proven ability to lead technical direction and influence architectural decisions across teams without formal authority"
We'll make each
- .
Now About the role: combine intro paragraph and The Role paragraph.
Let's craft:
Intro: "Unity Vector builds a data platform that powers insight, experimentation, attribution, and AI-driven decision-making across the company. Our systems operate at scale across batch and streaming data, supporting analytics, product intelligence, machine learning pipelines, and business operations. As data volume and complexity grow, our platform also supports large-scale model training, feature generation, and experimentation workflows that power production ML systems. To support this growth, we need strong technical ownership to ensure our ML pipelines remain reliable, scalable, and architecturally sound."
The Role paragraph: "We are seeking a senior data infra engineer to design and evolve the large-scale offline platform. This role focuses on building reliable infrastructure for generating data infrastructure, training datasets, and orchestrating data workflows. You will work closely with ML engineers and platform teams to ensure our pipelines can efficiently handle growing data volumes and increasingly complex training workloads. You will play a key role in shaping how model datasets are prepared to ensure the reliability, scalability, and performance of our data platform."
Combine into About the role section.
Now we need to output only HTML fragment, no markdown fences.
We'll produce:
About the role
...
...
Responsibilities
- ...
...
Requirements
...
Benefits
Benefits At Unity, we want our team members to thrive. We offer a wide range of benefits designed to support well-being and work-life balance. Please note: Benefits eligibility, specific offerings, and coverage vary based on the country and employment status.
- Comprehensive health, life, and disability insurance
- Commute subsidy
- Employee stock ownership
- Competitive retirement/pension plans
- Generous vacation and personal days
- Support for new parents through leave and family-care programs
- Office food snacks
- Mental Health and Wellbeing programs and support
- Employee Resource Groups
- Global Employee Assistance Program
- Training and development programs
- Volunteering and donation matching program
Pay
Zone A: $210,300 - $273,400 Zone B: $187,200 - $243,300 Zone C: $165,600 - $215,200 This range reflects the anticipated base salary for this position. Beyond base salary, this role may be eligible for equity awards and participation in our company incentive plans (such as annual discretionary bonuses or sales commissions). The final offer amount will depend on several factors, including geographic location and the candidate’s relevant experience, professional background, and skill set.
We should ensure no duplicate sentences.
Check for any leftover boilerplate: we removed EEO, equal opportunity, scam warning, application instructions, privacy, headhunter, etc.
We kept Life at Unity? Not included. We could incorporate into About the role as an extra paragraph after The Role? Might be good to add a paragraph about Unity. Let's add a paragraph: "Life at Unity Unity [NYSE: U] is the world’s leading game engine, powering play for more than 3 billion consumers each month. The top mobile games in the world, the most played PC indie titles, the most innovative console games, and virtually all of the top XR and Web Games are developed, deployed, and grown in Unity. Unity also enables teams across industries like automotive, manufacturing, and healthcare to design, simulate
- . The list separated by |. We'll split. Now Pay section: include the pay ranges and note about equity awards etc. The Additional Information includes repeated paragraph; we need to include once. Let's capture: "Zone A: $210,300 - $273,400 Zone B: $187,200 - $243,300 Zone C: $165,600 - $215,200 This range reflects the anticipated base salary for this position. Beyond base salary, this role may be eligible for equity awards and participation in our company incentive plans (such as annual discretionary bonuses or sales commissions). The final offer amount will depend on several factors, including geographic location and the candidate’s relevant experience, professional background, and skill set." We should not repeat the sentence twice. Now Responsibilities: list each bullet from "What You’ll Do". The text: "Develop infrastructure that supports both batch and stream big data processing using technologies such as Flink, Spark, Ray, etc. Design and operate large-scale data pipelines that generate training datasets used for machine learning training and experimentation Integrate data pipelines with workflow orchestration systems (e.g., Flyte, Airflow, or similar) to enable reliable multi-stage training workflows Improve reproducibility and observability of data pipelines through dataset validation, monitoring, and automated testing Optimize performance and resource utilization across distributed compute systems used for data processing Partner closely with ML engineers to enable efficient large-scale experimentation and model iteration Lead architectural improvements to ensure our offline data pipelines remain scalable, reliable, and cost-efficient" We'll make each as
- . Requirements: "What We’re Looking For" list: "Experience working with distributed computing frameworks such as Flink, Spark, Ray for distributed data processing Experience building infrastructure for training data generation, dataset preparation, or ML feature pipelines Experience optimizing big data pipelines and infrastructure for cost efficiency Strong programming skills in Python and experience working with large-scale distributed workloads Experience with modern data infrastructure (data lakes, warehouses, orchestration systems, streaming platforms) Strong systems thinking, with the ability to reason about performance, scalability, reliability, and cost tradeoffs in distributed systems Proven ability to lead technical direction and influence architectural decisions across teams without formal authority" We'll make each
- .
Now About the role: combine intro paragraph and The Role paragraph.
Let's craft:
Intro: "Unity Vector builds a data platform that powers insight, experimentation, attribution, and AI-driven decision-making across the company. Our systems operate at scale across batch and streaming data, supporting analytics, product intelligence, machine learning pipelines, and business operations. As data volume and complexity grow, our platform also supports large-scale model training, feature generation, and experimentation workflows that power production ML systems. To support this growth, we need strong technical ownership to ensure our ML pipelines remain reliable, scalable, and architecturally sound."
The Role paragraph: "We are seeking a senior data infra engineer to design and evolve the large-scale offline platform. This role focuses on building reliable infrastructure for generating data infrastructure, training datasets, and orchestrating data workflows. You will work closely with ML engineers and platform teams to ensure our pipelines can efficiently handle growing data volumes and increasingly complex training workloads. You will play a key role in shaping how model datasets are prepared to ensure the reliability, scalability, and performance of our data platform."
Combine into About the role section.
Now we need to output only HTML fragment, no markdown fences.
We'll produce:
About the role
...
...
Responsibilities
- ... ...
Requirements
- ...
Benefits
Benefits At Unity, we want our team members to thrive. We offer a wide range of benefits designed to support well-being and work-life balance. Please note: Benefits eligibility, specific offerings, and coverage vary based on the country and employment status.
- Comprehensive health, life, and disability insurance
- Commute subsidy
- Employee stock ownership
- Competitive retirement/pension plans
- Generous vacation and personal days
- Support for new parents through leave and family-care programs
- Office food snacks
- Mental Health and Wellbeing programs and support
- Employee Resource Groups
- Global Employee Assistance Program
- Training and development programs
- Volunteering and donation matching program
Pay
Zone A: $210,300 - $273,400 Zone B: $187,200 - $243,300 Zone C: $165,600 - $215,200 This range reflects the anticipated base salary for this position. Beyond base salary, this role may be eligible for equity awards and participation in our company incentive plans (such as annual discretionary bonuses or sales commissions). The final offer amount will depend on several factors, including geographic location and the candidate’s relevant experience, professional background, and skill set.
We should ensure no duplicate sentences. Check for any leftover boilerplate: we removed EEO, equal opportunity, scam warning, application instructions, privacy, headhunter, etc. We kept Life at Unity? Not included. We could incorporate into About the role as an extra paragraph after The Role? Might be good to add a paragraph about Unity. Let's add a paragraph: "Life at Unity Unity [NYSE: U] is the world’s leading game engine, powering play for more than 3 billion consumers each month. The top mobile games in the world, the most played PC indie titles, the most innovative console games, and virtually all of the top XR and Web Games are developed, deployed, and grown in Unity. Unity also enables teams across industries like automotive, manufacturing, and healthcare to design, simulate