Senior Engineer, ML Data Services

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions. Must not create sections with filler like "commensurate with experience". So we need to parse the posting. Let's extract content: Mission Summary: We are seeking a Senior Engineer to join our ML Data Services team and help us build and improve data infrastructure for Autonomy ML teams. As a Senior Engineer, you will be responsible for building scalable microservices, APIs, and tooling to support Autonomy labeling needs. You will also help architect and implement scalable pipelines to process terabytes of data and deliver datasets for ML training, Simulation, and evaluation. What you'll be doing: (list) - Design and implement Restful APIs and microservices for data labeling and annotations - Architect, build and maintain scalable data processing pipelines with cloud ETL technology to deliver datasets for Autonomy teams - Take ownership of highly-available, critical backend services and APIs that store and expose terabytes of data - Work closely with leadership and stakeholders to define objectives, align timelines, agree on key deliverables, and build the execution plan - Design and develop monitoring and observability services for the MLOps data service pipelines - Mentor and teach junior engineers in the team to develop good SDLC skills and better quality code with pairing sessions What we're looking for: - 5+ years of software development experience with Python preferred - 5+ years of web backend development experience with REST APIs and microservices - 3+ years of AWS cloud experience (e.g., DynamoDB, API Gateway, EKS, Lambda, OpenSearch, Redshift, S3 ) - 3+ years of data engineering experience with AWS Step Functions, Airflow or Prefect - Strong written and oral communication skills - Experience working in cross-functional development teams, including quarterly road map design - Hands-on experience using modern AI coding tools (e.g., Cursor, Claude Code, GitHub Copilot) to accelerate development, refactoring, and code review - Ability to mentor junior engineers - BS or MS in Computer Science or related field Bonus points (not required): - Hands-on experience with using Ray, Beam, Spark, or related big data processing in a large-scale environment - Expertise in deploying and optimizing vector databases for retrieval pipelines and multi-dimensional data embeddings - Experience in Docker Containerization - Autonomous driving industry experience Salary Range: $149,000 USD - $198,500 USD Benefits: Motional’s benefits include but are not limited to medical, dental, vision, 401k with a company match, health saving accounts, life insurance, pet insurance, and more. Company description: Motional is a driverless technology company making autonomous vehicles a safe, reliable, and accessible reality. We’re driven by something more. Our journey is always people first. We aren't just developing driverless cars; we're creating safer roadways, more equitable transportation options, and making our communities better places to live, work, and connect. Our team is made up of engineers, researchers, innovators, dreamers and doers, who are creating a technology with the potential to transform the way we move. Higher purpose, greater impact. We’re creating first-of-its-kind technology that will transform transportation. To do so successfully, we must design for everyone in our cities and on our roads. We believe in building a great place to work through a progressive, global culture that is diverse, inclusive, and ensures people feel valued at every level of the organization. Diversity helps us to see the world differently; it’s not only good for our business, it’s the right thing to do. Scale up, not starting up. Our team is behind some of the industry's largest leaps forward, including the first fully-autonomous cross-country drive in the U.S, the launch of the world's first robotaxi pilot, and operation of the world's longest-standing public robotaxi fleet. We’re driven to scale; we’re moving towards commercialization of our technology, and we need team members who are ready to embrace change and challenges. Formed as a joint venture between Hyundai Motor Group and Aptiv, Motional is fundamentally changing how people move through their lives. Headquartered in Boston, Motional has operations in the U.S and Asia. For more information, visit www.Motional.com and follow us on Twitter, LinkedIn, Instagram and YouTube. We need to remove EEO/E-Verify etc. Also remove "Motional AD Inc. is an EOE..." and the E-Verify paragraph. Now decide sections: - About the role: could be the Mission Summary paragraph(s). Could combine mission summary and maybe company description? Usually "About the role" is description of role responsibilities. But we have separate "What you'll be doing" which is responsibilities. So we could have:

About the role

Mission Summary paragraph(s)

Responsibilities

• ... list items

Requirements

maybe combine "What we're looking for" (required) as Requirements.

Qualifications

maybe education? Could be part of Requirements. But we can keep Requirements as the list of required experience/skills. Could also have Skills section for specific technical skills? But we already have them in Requirements. The instruction: prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Benefits, Pay. Possibly also Skills? But we can incorporate skills into Requirements. We must not create Schedule section because no schedule info. We must not create Benefits unless posting actually states them - yes we have benefits description. We must not create Pay unless posting actually states salary range - yes we have salary range. We must not create Qualifications if it's just filler; but we have education requirement (BS/MS) which could be part of Requirements. Could also have a Qualifications section for education/bonus? But we can keep Requirements covering required experience, and maybe a separate "Preferred Qualifications" for bonus points? However instruction: prefer few substantive sections. Could combine required and preferred into Requirements? But we could separate "Requirements" (required) and "Preferred Qualifications" (bonus). However that adds another section. Might be okay if we have substantive content. But we need to avoid thin sections. Bonus points list is substantive. Could make a section "Preferred Qualifications". That's okay. Thus sections: About the role, Responsibilities, Requirements, Preferred Qualifications, Benefits, Pay. Check each for real content. About the role: Mission Summary paragraph(s). We have two sentences: "We are seeking a Senior Engineer..." and "As a Senior Engineer, you will be responsible..." plus maybe also "You will also help architect..." Actually that's part of responsibilities. But we can put mission summary as About the role. Responsibilities: list of what you'll be doing. Requirements: list of required experience/skills (the bullet list under "What we're looking for"). Preferred Qualifications: bonus points list. Benefits: description of benefits. Pay: salary range. We must not include any fluff like "The salary range for this role is an estimate based on a wide range of compensation factors..." That's boilerplate but still part of salary description; we can keep the salary range line and maybe a brief note that it's base salary only? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the salary range sentence and maybe the note about base salary only and additional compensation? That is substantive. However the sentence "The salary range for this role is an estimate based on a wide range of compensation factors including but not limited to specific skills, experience and expertise, role location, certifications, licenses, and business needs." is somewhat generic but still part of posting. It's not boilerplate like EEO; it's about compensation. Might be considered substantive. We can keep it. Also "The estimated compensation range listed in this job posting reflects base salary only. This role may include additional forms of compensation such as a bonus or company equity. The recruiter assigned to this role can share more information about the specific compensation and benefit details associated with this role during the hiring process." That's also substantive. We'll keep that. Similarly for benefits: "Candidates for certain positions are eligible to participate in Motional’s benefits program. Motional’s benefits include but are not limited to medical, dental, vision, 401k with a company match, health saving accounts, life insurance, pet insurance, and more." We'll keep that. Now we need to remove EEO/E-Verify and other legal boilerplate: "Motional AD Inc. is an EOE. We celebrate diversity..." and "To comply with Federal Law, we participate in E-Verify..." etc. Remove those. Also remove navigation/social media links? The paragraph about visiting website and follow us on Twitter etc is maybe considered boilerplate but it's substantive about company? It's more like marketing. Might be considered boilerplate but it's not EEO. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The social media links could be considered navigation? Might be considered navigation. Safer to remove that line. Also remove "For more information, visit www.Motional.com and follow us on Twitter, LinkedIn, Instagram and YouTube." That's navigation/promotional. Remove. Also remove "Headquartered in Boston, Motional has operations in the U.S and Asia." That's company description but maybe okay. It's not navigation. Keep. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

About the role

We are seeking a Senior Engineer to join our ML Data Services team and help us build and improve data infrastructure for Autonomy ML teams. As a Senior Engineer, you will be responsible for building scalable microservices, APIs, and tooling to support Autonomy labeling needs. You will also help architect and implement scalable pipelines to process terabytes of data and deliver datasets for ML training, Simulation, and evaluation.

Responsibilities

• Design and implement Restful APIs and microservices for data labeling and annotations
• Architect, build and maintain scalable data processing pipelines with cloud ETL technology to deliver datasets for Autonomy teams
• Take ownership of highly-available, critical backend services and APIs that store and expose terabytes of data
• Work closely with leadership and stakeholders to define objectives, align timelines, agree on key deliverables, and build the execution plan
• Design and develop monitoring and observability services for the MLOps data service pipelines
• Mentor and teach junior engineers in the team to develop good SDLC skills and better quality code with pairing sessions

Requirements

• 5+ years of software development experience with Python preferred
• 5+ years of web backend development experience with REST APIs and microservices
• 3+ years of AWS cloud experience (e.g., DynamoDB, API Gateway, EKS, Lambda, OpenSearch, Redshift, S3)
• 3+ years of data engineering experience with AWS Step Functions, Airflow or Prefect
• Strong written and oral communication skills
• Experience working in cross-functional development teams, including quarterly road map design
• Hands-on experience using modern AI coding tools (e.g., Cursor, Claude Code, GitHub Copilot) to accelerate development, refactoring, and code review
• Ability to mentor junior engineers
• BS or MS in Computer Science or related field

Preferred Qualifications