Manager, AV Evaluation Framework

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to parse the job posting. First, identify sections: - About the role: The description: "This position is listed on behalf of a partner company... Manager, AV Evaluation Framework based in United States. This is a full-time Remote/Hybrid leadership role focused on building and operating evaluation frameworks for autonomous vehicle development. The position combines people leadership, technical strategy, and execution ownership across critical metrics and data platforms. You will lead a team of software and data engineers responsible for transforming large-scale simulation and real-world driving data into trustworthy metrics and actionable engineering insights. The role partners closely with autonomy, simulation, systems, test engineering, AI, and release teams to support confident development decisions. You will shape technical roadmaps, improve platform reliability, and establish operational practices that enable teams to evaluate AV performance efficiently. This is an opportunity to lead complex, data-intensive engineering systems in a rapidly evolving and safety-critical environment." That's about the role. - Responsibilities: The "Accountabilities" bullet list: Lead, coach, and develop a high-performing team... etc. Those are responsibilities. - Requirements: The list after "Requirements": Bachelor’s degree..., 8+ years..., 3+ years..., Proven experience..., Experience building..., Strong understanding..., Ability to translate..., Strong written..., Experience in autonomous vehicles..., Experience evaluating..., Familiarity with metrics platforms..., Production engineering experience with Python, C++, and SQL..., Experience with large-scale analytical data stores..., Familiarity with workflow orchestration..., Knowledge of simulation..., Experience leading platform migrations..., Demonstrated ability to build trust... These are requirements. - Qualifications: Might be overlapping with requirements. The posting doesn't have a separate "Qualifications" heading; but we could treat "Requirements" as qualifications. However we need to decide: Should we include a Qualifications section? The instruction: Use headings for sections if posting has real specific content. There's no explicit "Qualifications" heading, but we could still create a Qualifications section if we think the content fits. However we must not invent sections; we should only include sections that correspond to content present. The posting has "Requirements" and then later "Benefits". There's no separate "Qualifications". So we should not create a Qualifications section unless we think the requirements also serve as qualifications; but we already have a Requirements section. The instruction says we can use headings like Qualifications, Skills, Benefits, Pay, Schedule. We should include only those that have content. There's no explicit Skills list separate from requirements; but there are many skill-like items (Python, C++, SQL, etc.) Could treat as Skills. However we must not invent or summarize away detail. If we create a Skills section, we need to pull out skill-specific content from the posting. The posting includes many skill/experience items: "Experience building or operating scalable data-processing pipelines, workflow systems, developer tooling, or distributed services." "Strong understanding of software engineering fundamentals, including system design, testing, code review, observability, performance tradeoffs, and operational reliability." "Experience using data and operational metrics to improve reliability, prioritization, and execution." "Ability to translate complex technical challenges and ambiguous customer requirements into clear priorities, technical plans, and decisions." "Strong written and verbal communication skills..." "Experience in autonomous vehicles, robotics, simulation, advanced driver-assistance systems, or another safety-critical and data-intensive environment is preferred." "Experience evaluating complex systems using statistical, numerical, machine learning, or time-series methods is preferred." "Familiarity with metrics platforms, data quality systems, experiment analysis, telemetry, or performance monitoring is preferred." "Production engineering experience with Python, C++, and SQL is preferred." "Experience with large-scale analytical data stores such as BigQuery, Databricks, or similar technologies is preferred." "Familiarity with workflow orchestration, batch processing, cloud infrastructure, and data-pipeline operations is preferred." "Knowledge of simulation, sensor data, road testing, or evaluation of perception, prediction, planning, or control systems is advantageous." "Experience leading platform migrations, reducing technical debt, or consolidating fragmented frameworks is advantageous." "Demonstrated ability to build trust with technical and non-technical partners and create clarity in rapidly changing environments." These could be considered skills/qualifications. However we already have a Requirements section that includes many of these. The instruction says "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Skills into one section? But we have headings for both; we need to decide. We have explicit "Requirements" block. That's a section. We could also have a "Skills" section if we extract skill-specific items not covered elsewhere. But many of those are also requirements. To avoid duplication, we could put all under Requirements and not create Skills. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must use all; we just use those that have content. So we can have About the role, Responsibilities, Requirements, Benefits. Possibly Pay and Schedule if present. Pay: The posting includes "Base salary range of $218,800–$335,300, with the actual offer determined by factors such as skills, experience, training, certifications, and organizational needs." That's pay info. So we should include a Pay section. Schedule: The posting mentions "Full-time Remote/Hybrid work arrangement in the United States. If located within a 50-mile radius of Austin, Detroit, Warren, Milford, or Sunnyvale, CA, employees are expected to report to the applicable location at least three times per week." That's schedule info (remote/hybrid, expectation). So we should include a Schedule section. Benefits: There's a Benefits block: "Full-time Remote/Hybrid work arrangement in the United States.... Base salary range... Eligibility for an incentive compensation program... Eligibility to participate in a company vehicle evaluation program... Inclusive workplace... Reasonable accommodations..." Actually the Benefits block includes salary and schedule info as well. But we need to avoid duplication. The Benefits block includes: "Full-time Remote/Hybrid work arrangement in the United States. If located within a 50-mile radius of Austin, Detroit, Warren, Milford, or Sunnyvale, CA, employees are expected to report to the applicable location at least three times per week. Base salary range of $218,800–$335,300, with the actual offer determined by factors such as skills, experience, training, certifications, and organizational needs. Eligibility for an incentive compensation program based on organizational performance, job level, and individual performance. Eligibility to participate in a company vehicle evaluation program following successful completion of a motor vehicle report review, subject to program requirements. Inclusive workplace with employment opportunities available to qualified candidates, including individuals with disabilities. Reasonable accommodations are available for candidates who require support during the job search or application process." Thus Benefits includes remote/hybrid, salary, incentive, vehicle program, workplace, accommodations. Since we already have Pay and Schedule sections, we might still include Benefits for other benefits (incentive, vehicle program, inclusive workplace, accommodations). However we must not repeat same info. We could keep Benefits section for the non-pay/schedule benefits: incentive compensation, vehicle evaluation program, inclusive workplace, reasonable accommodations. The remote/hybrid and salary could be moved to Schedule and Pay respectively. But the Benefits block also mentions those; we need to ensure we preserve all substantive information. So we can extract: - Benefits: incentive compensation program, company vehicle evaluation program, inclusive workplace, reasonable accommodations. - Pay: base salary range. - Schedule: full-time remote/hybrid, expectation to report 3 days/week if within 50-mile radius of listed locations. Now, we need to ensure we don't create sections with filler like "commensurate with experience". We have concrete info. Now, we need to format as HTML fragment: use

for each section heading, then content:

for prose,

• for lists. We need to decide what content goes where. About the role: paragraph(s). Could be one paragraph summarizing. Responsibilities: list of accountabilities. Requirements: list of requirements (maybe split into required and preferred? The posting lumps them together; we can keep as one list. Pay: paragraph with salary range. Schedule: paragraph with remote/hybrid and expectation. Benefits: list of benefits (incentive, vehicle program, inclusive workplace, accommodations). We must not include job title heading, no Job ID, no application instructions, no boilerplate like How Jobgether Works, Data Privacy Notice, etc. Remove those. Now, let's craft. First, About the role: combine the initial description. Paragraph: "This position is listed on behalf of a partner company, who manages all applications and next steps. Our partner is looking for a Manager, AV Evaluation Framework based in the United States. This is a full-time Remote/Hybrid leadership role focused on building and operating evaluation frameworks for autonomous vehicle development. The position combines people leadership, technical strategy, and execution ownership across critical metrics and data platforms. You will lead a team of software and data engineers responsible for transforming large-scale simulation and real-world driving data into trustworthy metrics and actionable engineering insights. The role partners closely with autonomy, simulation, systems, test engineering, AI, and release teams to support confident development decisions. You will shape technical roadmaps, improve platform reliability, and establish operational practices that enable teams to evaluate AV performance efficiently. This is an opportunity to lead complex, data-intensive engineering systems in a rapidly evolving and safety-critical environment." That's fine. Responsibilities: list from Accountabilities. Items: - Lead, coach, and develop a high-performing team of software and data engineers through hiring, onboarding, career development, feedback, and performance management. - Define and communicate the team’s technical vision, roadmap, priorities, and operating plan in partnership with evaluation and broader autonomous vehicle leadership. - Own the delivery of scalable frameworks for creating, executing, and monitoring metrics across simulated and real-world driving data. - Ensure evaluation platforms are reliable, observable, performant, maintainable, and accessible to internal engineering and evaluation teams. - Establish meaningful service-level objectives, health metrics, dashboards, and operational practices for critical data and analysis pipelines. - Balance new feature delivery with platform modernization, technical debt reduction, operational support, and long-term architecture investments. - Partner with internal and external stakeholders to translate ambiguous evaluation needs into clear technical plans, priorities, and measurable outcomes. - Raise engineering standards through architecture and design reviews, testing, code reviews, documentation, security practices, and operational excellence. - Establish clear boundaries between shared framework ownership and metric-specific business logic to improve collaboration and accountability. - Participate in and strengthen production support and incident-response practices for critical metrics and data pipelines. We'll put each as
• . Requirements: list. Items: - Bachelor’s degree in Computer Science, Engineering, Data Science, or a related technical field, or equivalent practical experience. - 8+ years of experience building software, data platforms, analytics infrastructure, or evaluation systems in production environments. - 3+ years of direct experience managing and developing engineers or other technical professionals. - Proven experience setting technical direction and delivering roadmaps for platforms, frameworks, or infrastructure products used by multiple teams. - Experience building or operating scalable data-processing pipelines, workflow systems, developer tooling, or distributed services. - Strong understanding of software engineering fundamentals, including system design, testing, code review, observability, performance tradeoffs, and operational reliability. - Experience using data and operational metrics to improve reliability, prioritization, and execution. - Ability to translate complex technical challenges and ambiguous customer requirements into clear priorities, technical plans, and decisions. - Strong written and verbal communication skills, with the ability to influence and collaborate across organizational boundaries. - Experience in autonomous vehicles, robotics, simulation, advanced driver-assistance systems, or