Software Engineer, ML Infrastructure, Level 5

We need to output HTML fragment with sections: About the role? Actually the posting includes description of company, role, responsibilities, qualifications, benefits, pay. We need headings:

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include. The posting includes: - Intro about Snap (company description) maybe "About the role" or "About Snap"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate. We have: - Description of role: "You’ll play a critical role in scaling our ML Infrastructure, optimizing AI training and inference systems, and driving innovations that make Snapchat’s ranking and recommendation systems more efficient and impactful." Also "We’re looking for a Software Engineer to join the ML Platform team." Then description of team builds foundational data platforms etc. That's more about responsibilities. - "What you’ll do:" list of duties. - "Knowledge, Skills & Abilities:" list. - "Minimum Qualifications:" list. - "Preferred Qualifications:" list. - "Our Benefits:" description. - "Compensation" with pay zones. - Also "Default Together" policy about office days (schedule). That's schedule info. - Also mention equity. We need to avoid boilerplate like EEO, disability accommodation statement, equal opportunity employer, etc. Also remove duplicated lines (there is duplicate "Develop high-performance inference systems to ensure fast and efficient AI model serving" appears twice). We should keep only one instance. We need to preserve all substantive information. So we need to include details about responsibilities, qualifications, skills, benefits, pay, schedule (office days). Also maybe a brief "About the role" or "About Snap" but we can incorporate company description into a short paragraph under maybe "About the role" or "About Snap". The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have content for: - About the role: could be the introductory paragraph about Snap and the role. - Responsibilities: the "What you’ll do:" list. - Requirements: could combine Minimum Qualifications and maybe Knowledge, Skills & Abilities? But we have separate sections for Knowledge, Skills & Abilities and Minimum Qualifications and Preferred Qualifications. The instruction allows sections like Requirements, Qualifications, Skills. We could map: - Skills: Knowledge, Skills & Abilities. - Qualifications: Minimum Qualifications. - Preferred Qualifications maybe could be included under Qualifications as additional bullet? Or we could have a separate "Preferred Qualifications" but not in allowed headings list. The allowed headings list includes Qualifications, Skills, Benefits, Pay, Schedule, About the role, Responsibilities, Requirements. We could treat "Preferred Qualifications" as part of Qualifications (maybe add a note). Or we could create a separate section "Preferred Qualifications" but that's not in the list; but the instruction says use headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning those are examples, not exhaustive? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we should stick to those. So we need to map content to those headings. Thus we can have: - About the role: company description + role overview. - Responsibilities: the "What you’ll do:" list (deduplicated). - Requirements: maybe combine Minimum Qualifications and Knowledge, Skills & Abilities? But we have separate Skills heading. So we can put Knowledge, Skills & Abilities under Skills heading. Minimum Qualifications under Qualifications heading. Preferred Qualifications maybe also under Qualifications (as additional bullets) or we could add a note under Qualifications that includes both minimum and preferred. But we need to preserve all substantive info; we can include both sets under Qualifications, maybe label them as "Minimum Qualifications:" and "Preferred Qualifications:" inside the

  ? But that would be mixing headings inside list; maybe better to have two separate
  under Qualifications: one for minimum, one for preferred. Or we could have a separate section "Preferred Qualifications" but not allowed. I'd rather include both under Qualifications with subheadings using

  or . But the instruction says use

  for prose,

  • for any list. So we can have a

    that says "Minimum Qualifications:" then a

    . Then another

    that says "Preferred Qualifications:" then a

    . That's acceptable. - Benefits: the "Our Benefits:" paragraph. - Pay: the compensation details with zones. - Schedule: the "Default Together" policy about office 4+ days per week. We should also maybe include a short paragraph about equity under Benefits or Pay? The posting mentions equity in the form of RSUs under Compensation. Could include in Pay section. We must remove boilerplate: EEO statements, disability accommodation request, "Default Together" policy is not boilerplate; it's schedule info. Also remove lines like "If you have a disability or special need that requires accommodation, please don’t be shy and provide us some information." That's boilerplate/accommodation statement; remove. Also remove "At Snap Inc. we believe that being together in person helps us build our culture faster..." Actually that's the Default Together policy; we keep that as schedule. Remove the equal opportunity employer paragraphs. Also remove "Our Benefits: Snap Inc. is its own community..." we keep benefits description. Remove the line "We are an Equal Opportunity Employer and will consider qualified applicants with criminal histories..." etc. Remove. Also remove duplicated lines: the "Develop high-performance inference systems..." appears twice; keep one. Now we need to output only HTML fragment, no /, no markdown. Let's craft. Structure:

    About the role

    Snap Inc is a technology company... (company description) ... We’re looking for a Software Engineer to join the ML Platform team. Our team builds the foundational data platforms (robusta/hashi, mds) to pump in the bloodstream - data to support offline model training and online feature serving. We provide the essential tools to help customers monitor and assure data quality (aegis), manage/register features, trace feature through its lifecycles and assist in feature deprecation. With the significant infra cost of this area, our team also focuses on continuous optimization of the storage/processing to sustain the ML growth of Snap.

    But we need to ensure we don't repeat job title. Already not. Now Responsibilities:

    Responsibilities

    • Design and optimize infrastructure systems for machine learning workloads at scale and drive reliability and efficiency improvements across Snapchat’s ML Infrastructure
    • Develop high-performance inference systems to ensure fast and efficient AI model serving
    • Build infrastructure to perform scalable ML model training, evaluation, and inference in the cloud
    • Build comprehensive data management systems for scalable data collection, labeling, processing, and evaluation
    • Work on state-of-the-art vector search algorithms to improve the precision, recall and scalability of our retrieval systems
    • Work closely with ML engineers to deploy cutting-edge models into production
    Note we removed duplicate. Now Skills:

    Skills

    Knowledge, Skills & Abilities:

    • Strong programming skills in Python, Java, Scala or C++
    • Strong problem-solving skills with a focus on system performance, scalability, and efficiency
    • Good understanding of distributed systems and the infrastructure components of large-scale ML
    • Experience with big data processing frameworks such as Spark, Flink, or Ray
    • Ability to collaborate and work well with others
    • Proven track record of operating highly-available systems at significant scale
    • Ability to proactively learn new concepts and apply them at work
    Now Qualifications:

    Qualifications

    Minimum Qualifications:

    • Bachelor’s degree in a technical field such as computer science or equivalent experience
    • 6+ years of post‑Bachelor’s software development experience; or Master’s degree in a technical field + 5+ year of post‑grad software development experience; or PhD in a relevant technical field + 2+ years of post‑grad software development experience
    • Experience building large scale production machine learning systems, distributed systems or big data processing

    Preferred Qualifications:

    • Masters/PhD in a technical field such as computer science or equivalent industry experience
    • Experience working with ML Training platforms or optimizing AI model inference
    • Familiarity with ML frameworks such as TensorFlow, PyTorch, Caffe2, Spark ML, scikit-learn, or related frameworks
    Now Benefits:

    Benefits

    Snap Inc. is its own community, so we’ve got your back! We do our best to make sure you and your loved ones have everything you need to be happy and healthy, on your own terms. Our benefits are built around your needs and include paid parental leave, comprehensive medical coverage, emotional and mental health support programs, and compensation packages that let you share in Snap’s long‑term success!

    Now Pay:

    Pay

    In the United States, work locations are assigned a pay zone which determines the salary range for the position. The successful candidate’s starting pay will be determined based on job‑related skills, experience, qualifications, work location, and market conditions. The starting pay may be negotiable within the salary range for the position. These pay zones may be modified in the future.

    • Zone A (CA, WA, NYC): $209,000‑$313,000 annually
    • Zone B: $199,000‑$297,000 annually
    • Zone C: $178,000‑$266,000 annually

    This position is eligible for equity in the form of RSUs.

    Now Schedule:

    Schedule

    At Snap Inc. we practice a “default together” approach and expect our team members to work in an office 4+ days per week.

    We should ensure we didn't include any boilerplate like EEO, disability accommodation, equal opportunity employer, etc. We removed those. Check for any leftover boilerplate: The snippet also had "If you have a disability or special need that requires accommodation, please don’t be shy and provide us some information." Removed. Also "At Snap, we believe that having a team of diverse