Senior Manager, Coder Fellows

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. First, "About Snorkel" is intro, not a section heading we need? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create headings for sections that exist. We have "About The Role" heading in posting. That's similar to "About the role". So we can output

About the role

and then content. Then "What You Will Do" is responsibilities. So we can put

Responsibilities

with list. Then "What This Role Owns—and Does Not Own" maybe part of responsibilities? Could be included under responsibilities or separate? Probably responsibilities. Then "What We Are Looking For" is requirements/qualifications/skills. We need to split into Requirements, Qualifications, Skills as appropriate. The posting lists experience, degree not required, experience with AI/ML helpful, demonstrated experience hiring..., experience managing people across multiple projects..., experience in consultancy..., enough technical depth..., ability to evaluate performance..., strong written and verbal communication..., etc. These are qualifications/requirements/skills. We can put them under

Requirements

maybe combine. But we need separate headings only if content exists. Could put all under Requirements. Or we could split: Requirements (experience), Qualifications (education?), Skills (technical depth, communication). However the instruction: Prefer a few substantive sections over many thin ones. So maybe just one section for Requirements/Qualifications/Skills combined? But they asked to use those headings if content exists. We could include all three but ensure each has substantive content. Let's see: Requirements: maybe "3+ years of experience in software engineering, technical leadership, or a related environment, including direct management of programmers or software engineers." That's a requirement. Qualifications: "A computer-science degree is not required." That's a qualification? Could be under Qualifications. Skills: "Experience with AI/ML development, model evaluation, annotation, data quality, or technical-content production is helpful." plus "Demonstrated experience hiring, onboarding, coaching, conducting performance reviews, delivering actionable feedback, and handling difficult conversations." plus "Experience managing people across multiple projects, clients, teams, or changing assignments." plus "Experience in a consultancy, software agency, contract engineering shop, professional-services organization, staff-augmentation model, or similar distributed environment is strongly preferred." plus "Enough technical depth to read and discuss code and pull requests, assess engineering judgment, and understand core software-development practices." plus "Ability to evaluate performance thoughtfully rather than relying on throughput, ticket volume, or other simple metrics." plus "Strong written and verbal communication, sound judgment, discretion, empathy, and a collaborative, low-ego approach." Thus we can split. Benefits: The posting includes "Be Your Best at Snorkel" describing opportunities, but not explicit benefits like health insurance etc. It mentions "market proven solutions, robust funding, scaling rapidly—offering a unique combination of stability and the excitement of high growth." Also "meaningful opportunities to shape priorities and initiatives, influence key strategic decisions, and directly impact our ongoing success." Also "Whether you’re looking to deepen your technical expertise, explore leadership opportunities, or learn new skills across multiple functions, you’re fully supported in building your career in an environment designed for growth, learning, and shared success." That's more about culture/benefits. Could be considered Benefits. Also there is mention of equity? Actually Pay section includes salary range and equity. Benefits maybe not explicit. The instruction: only create Benefits section if posting actually states them. It does mention "Be Your Best at Snorkel" describing opportunities, but not typical benefits like health, 401k. Might be considered benefits? Safer to omit Benefits if not explicit. Pay: The posting includes: "This role is full time and will receive a base salary based on location and level plus equity. Actual compensation will be determined based on factors including skills, qualifications, experience, and geographic location. Salary range(s) for this role $175,000—$250,000 USD". That's pay info. So we need Pay section. Schedule: The posting says "This role is full time". That's schedule info. So we can include Schedule section with "Full-time". Now we need to remove boilerplate: EEO, equal opportunity, accommodation request etc. Remove those paragraphs. Also remove "About Snorkel" intro? The instruction: 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. The "About Snorkel" is not a required heading; we could include it as a

maybe? But the instruction says use

for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but we should focus on those sections. The "About Snorkel" is introductory; we could include as a

before sections. It's substantive. We'll keep it as a

. Now structure:

About Snorkel ... (the paragraph).

About the role

... (the "About The Role" paragraph up to "This is a people-first role." maybe). Actually the "About The Role" section includes paragraphs: "Coding Fellows create high-quality technical content...". We'll include that as content under About the role. Then responsibilities:

Responsibilities

with

• items from "What You Will Do" and maybe "What This Role Owns—and Does Not Own". We'll list each bullet. Then Requirements:

  Requirements

  with
  • items: "3+ years of experience in software engineering, technical leadership, or a related environment, including direct management of programmers or software engineers." Qualifications:

    Qualifications

    with
    • items: "A computer-science degree is not required." maybe also "Experience with AI/ML development, model evaluation, annotation, data quality, or technical-content production is helpful." but that could be skills. We'll decide. Skills:

      Skills

      with list of the rest. Pay:

      Pay

      with

      containing salary range and equity note. Schedule:

      Schedule

      with

      Full-time

      . We must not include empty sections. Now ensure we preserve all substantive information: need to include all details from responsibilities, requirements, qualifications, skills, pay, schedule. Let's extract details. About Snorkel paragraph: "At Snorkel, we believe meaningful AI doesn’t start with the model, it starts with the data. We’re on a mission to help enterprises transform expert knowledge into specialized AI at scale. The AI landscape has gone through incredible changes since 2015, when Snorkel started as a research project in the Stanford AI Lab, to the generative AI breakthroughs of today. But one thing has remained constant: the data you use to build AI is the key to achieving differentiation, high performance, and production-ready systems. We work with some of the world’s largest organizations to empower scientists, engineers, financial experts, product creators, journalists, and more to build custom AI with their data faster than ever before. Excited to help us redefine how AI is built? Apply to be the newest Snorkeler!" We'll keep that as a

      . About The Role: paragraphs: "Coding Fellows create high-quality technical content used to train and evaluate AI systems. Depending on the project and each Fellow’s strengths, their work may include writing and reviewing code, opening pull requests, creating annotations or documentation, improving others’ work, and coaching peers. We are looking for a leader to directly manage a portfolio of Fellows who may contribute across multiple projects over time. Project delivery teams own day-to-day tasks, priorities, and outcomes; this role owns the people-management layer across projects, including expectations, performance, support, development, administration, and a fair, consolidated view of each Fellow’s contribution. This is a people-first role. You should have enough technical depth to understand and discuss Fellow work, but you will not be the day-to-day technical lead or approver for every project." We'll put that as

      under About the role. Now Responsibilities: "What You Will Do" bullet points: - Lead and support Coding Fellows - Build trusted relationships through regular one-on-ones and ongoing communication. - Understand each Fellow’s strengths, goals, challenges, and support needs; set clear expectations; and partner with People Operations and project leaders on onboarding and administrative matters. - Own cross-project performance management - Set expectations for quality, reliability, collaboration, communication, flexibility, learning, and professional conduct. - Gather and synthesize feedback across projects, accounting for assignment complexity, project context, ramp time, and changing responsibilities. - Recognize strong performance, provide candid feedback, and address concerns early through focused improvement plans. - Maintain technical credibility and quality - Review representative work, including code, pull requests, reviews, annotations, documentation, and commentary, to understand quality and development needs. - Partner with delivery and quality leads to identify recurring issues and distinguish individual performance concerns from unclear requirements, insufficient context, or process gaps. - Partner with project delivery teams - Create effective feedback loops with project managers, technical leads, reviewers, and other delivery partners. - Establish clear expectations when Fellows join projects, preserve context during transitions, surface assignment mismatches or blockers, and resolve conflicts with fairness and discretion. - Coach growth and strengthen the program - Hold regular career conversations and help Fellows grow as individual contributors, reviewers, quality specialists, coaches, or mentors. - Use contextualized metrics to monitor quality, throughput, reliability, team health, and retention; improve feedback and calibration processes; and contribute to hiring and workforce planning as the program scales. Also "What This Role Owns—and Does Not Own" could be included but maybe not needed as separate. We could incorporate into responsibilities but we already have coverage. Might add a note: "You own: Fellow support, people administration, performance expectations, consolidated feedback, performance reviews, coaching, development, and long-term success. Project delivery teams own: day-to-day task assignment, project-specific priorities, delivery plans, immediate deliverable acceptance, and project execution." We could add as a

      after responsibilities or incorporate. Since it's substantive, we should include. Could add as a

      under Responsibilities heading. Thus Responsibilities section will have a

      summarizing ownership, then a

      with the detailed duties. Now Requirements: "What We Are Looking For" first bullet: "3+ years of experience in software engineering, technical leadership, or a related environment, including direct management of programmers or software engineers." We'll put that as
      • . Qualifications: maybe "A computer-science degree is not required." That's a qualification note. Skills: rest: - Experience with AI/ML development, model evaluation, annotation, data quality, or technical-content production is helpful. - Demonstrated experience hiring, onboarding, coaching, conducting performance reviews, delivering actionable feedback, and handling difficult conversations. - Experience managing people across multiple projects, clients, teams, or changing assignments. - Experience in a consultancy, software agency, contract engineering shop, professional-services organization, staff-augmentation model, or similar distributed environment is strongly preferred. - Enough technical depth to read and discuss code and pull requests, assess engineering judgment, and understand core software-development practices. - Ability to evaluate performance thoughtfully rather than relying on throughput, ticket volume, or other simple metrics. - Strong written and verbal communication, sound judgment, discretion, empathy, and a collaborative, low-ego approach. We'll list those as
      • under Skills