Model Optimization Engineer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: EEO, application instructions, etc. Must preserve all substantive info. Let's parse the posting: Company description: Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential. Job Title: Model Optimization Engineer (we don't repeat as heading) Location: 100% Remote (U.S.) Position Type: Full-time, Direct W2 Salary Range: $150,000–$175,000 Annually Experience Required: 6+ years Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position. Job Summary: We are seeking an Model Optimization Engineer... (the paragraph). That's about role. Then Required Qualifications list bullet points. Preferred Qualifications list bullet points. How To Apply: instructions (to be removed). EEO statement removed. Thus we need sections: About the role (maybe from company description + job summary). Responsibilities? The job summary includes responsibilities: focusing on extracting maximum throughput, minimizing latency, reducing cost across training and inference workloads; spans full stack; work closely with cross-functional partners; translate ambiguous requirements; raise bar through code review, design review, mentorship. That's responsibilities. Requirements: maybe experience required (6+ years) and sponsorship? But we have Required Qualifications list. Could combine. Qualifications: maybe education and experience? But we have Required Qualifications (list) and Preferred Qualifications (list). Could treat Required Qualifications as "Requirements" and Preferred Qualifications as "Preferred Qualifications" but we only have headings list: Requirements, Qualifications, Skills. We could map: Requirements = experience required (6+ years) and sponsorship? Qualifications = education + required qualifications list? Skills = maybe technical skills from required qualifications? But we need to avoid thin sections. Better to have a few substantive sections: About the role (company description + job summary), Responsibilities (detailed responsibilities), Requirements (experience + sponsorship + required qualifications?), maybe Qualifications (education + required qualifications list?), Skills (maybe list of skills from required qualifications). However we must not create sections with filler. We need to ensure each section has real content. Let's think: The posting includes: - Company description (About the role) - Job Summary (role focus) - Responsibilities (implied in job summary) - Required Qualifications (list) - Preferred Qualifications (list) - Salary Range (Pay) - Location (maybe Schedule? Not schedule) - Position Type (Full-time) maybe Schedule? Not schedule. - Experience Required (6+ years) could be part of Requirements. - Sponsorship info maybe part of Requirements. We have Pay: Salary Range given. So we can include Pay section. Schedule: Not given (no mention of hours, shift). So we should NOT include Schedule section. Benefits: Not given. So no Benefits section. Thus we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay. But we need to avoid duplication. Let's decide: About the role: company description + job summary (first paragraph). Could be two paragraphs. Responsibilities: bullet list of duties from job summary: "extracting maximum throughput, minimizing latency, reducing cost across training and inference workloads for large neural network systems", "spans the full stack from low-level kernel optimization to distributed system tuning", "work closely with cross-functional partners — product, design, engineering, operations, and business stakeholders — to translate ambiguous requirements into well-engineered solutions", "raise the bar through code review, design review, and mentorship of more junior engineers". That's responsibilities. Requirements: maybe experience required (6+ years) and sponsorship info (US citizens etc). Could also include "Full-time, Direct W2" as position type but that's not a requirement. We'll keep Requirements as experience + sponsorship + position type? Might be okay. Qualifications: education (Bachelor’s or Master’s degree in CS, CE, or related field) plus maybe the Required Qualifications list? But that list is more like qualifications. Could treat Required Qualifications as Qualifications. Then Skills could be derived from those qualifications (proficiency in Python/C++, etc). But that would duplicate. Better: Use sections as per typical job posting: About the role, Responsibilities, Requirements (including experience, education, qualifications), Pay. But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use multiple of them if content exists. Let's assign: - About the role: company description + job summary (narrative) - Responsibilities: bullet list of duties (as above) - Requirements: experience required (6+ years) + sponsorship + position type (Full-time, Direct W2) + location (100% Remote US) maybe. - Qualifications: education (Bachelor’s/Master’s) + Required Qualifications list (the bullet points) - Skills: maybe we can extract specific skills from Required Qualifications: proficiency in Python and C++, hands-on experience optimizing deep learning workloads on modern GPUs, understanding of distributed training/inference, experience with profiling tools, familiarity with model compression techniques, grasp of memory hierarchies, communication primitives, parallelism strategies, measurement/debugging/analytical reasoning, communication/collaboration. That's essentially same as qualifications. Might be redundant but we can still list them as skills. But we need to avoid thin sections. If we put both Qualifications and Skills with overlapping content, might be considered thin? However each will have substantive content. Alternatively, we could combine Qualifications and Skills into one section called Qualifications, and omit Skills. But we must follow instruction: "Prefer a few substantive sections over many thin ones." So we should not create many thin sections. Better to have fewer sections: About the role, Responsibilities, Requirements (including experience, sponsorship, location, position type), Qualifications (education + required qualifications list), Pay. That's 5 sections. That seems reasonable. We must not include Benefits or Schedule. Thus output HTML with headings

for each section. Inside each section, use

for prose,

• for lists. We must not repeat job title as heading. We must not include Job ID etc. We must not include boilerplate. Let's craft content. About the role: combine company description and job summary. Company description: "Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential." Job Summary: "We are seeking an Model Optimization Engineer to focus on extracting maximum throughput, minimizing latency, and reducing cost across training and inference workloads for large neural network systems. The role spans the full stack from low-level kernel optimization to distributed system tuning, requiring deep understanding of GPU architecture, model parallelism, memory management, and compiler-level optimization. The ideal candidate has demonstrated impact on production AI workloads, with strong instrumentation and measurement discipline that enables rigorous, data-driven optimization decisions. In this role you will work closely with cross-functional partners — product, design, engineering, operations, and business stakeholders — to translate ambiguous requirements into well-engineered solutions, and will be expected to raise the bar through code review, design review, and mentorship of more junior engineers. The successful candidate brings strong engineering discipline, a clear communication style, and a track record of shipping meaningful work that holds up well in production." We can merge into a couple paragraphs. Responsibilities: bullet list: - Extract maximum throughput, minimize latency, and reduce cost across training and inference workloads for large neural network systems. - Span the full stack from low-level kernel optimization to distributed system tuning. - Work closely with cross-functional partners (product, design, engineering, operations, business stakeholders) to translate ambiguous requirements into well-engineered solutions. - Raise the bar through code review, design review, and mentorship of more junior engineers. Requirements: include: - Location: 100% Remote (U.S.) - Position Type: Full-time, Direct W2 - Experience: 6+ years of relevant experience. - Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply; unable to sponsor new H-1B visa petitions. We can put as prose or list. Probably list. Qualifications: education + required qualifications list. Education: Bachelor’s or Master’s degree in Computer Science, Computer Engineering, or a related field. Required Qualifications (list): - Six or more years of experience in performance engineering, ML systems, or HPC - Strong proficiency in Python and C++ - Hands-on experience optimizing deep learning workloads on modern GPUs - Deep understanding of distributed training and inference techniques - Experience with profiling tools across CPU, GPU, and distributed systems - Familiarity with model compression techniques and their accuracy implications - Strong grasp of memory hierarchies, communication primitives, and parallelism strategies - Excellent measurement, debugging, and analytical reasoning skills - Strong communication and collaboration skills We could also include Preferred Qualifications as a subsection? But we don't have a heading for Preferred Qualifications. Could we add a separate section? Not in allowed headings. Could we incorporate them into Qualifications as a separate list labeled "Preferred Qualifications"? That would still be under Qualifications heading. That's okay. Thus under Qualifications we could have two sublists: Required Qualifications and Preferred Qualifications. But we need to use
  • for any list. We can have nested? Probably just separate
    with a preceding

    indicating "Required Qualifications:" then list, then another

    "Preferred Qualifications:" then list. Preferred Qualifications list: - Experience optimizing LLM inference at production scale - Contributions to vLLM, TensorRT-LLM, DeepSpeed, or similar projects - Familiarity with custom kernel authoring in Triton or CUTLASS - Experience with FinOps for AI workloads - Publications or talks on AI systems performance Now Pay section: Salary Range: $150,000–$175,000 Annually. We can put as

    . Now ensure we don't include any fluff like "commensurate with experience". Not present. Now produce HTML fragment. We must not include or . Just the fragment. Let's construct:

    About the role

    Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential.

    We are seeking an Model Optimization Engineer to focus on extracting maximum throughput, minimizing latency, and reducing cost across training and inference workloads for large neural network systems. The role spans the full stack from low-level kernel optimization to distributed system tuning, requiring deep understanding of GPU architecture, model parallelism, memory management, and compiler-level optimization. The ideal candidate has demonstrated impact on production AI workloads, with strong instrumentation and measurement discipline that enables rigorous, data-driven optimization decisions. In this role you will work closely with cross-functional partners — product, design, engineering, operations, and business stakeholders — to translate ambiguous requirements into well-engineered solutions, and will be expected to raise the bar through code review, design review, and mentorship of more junior engineers. The successful candidate brings strong engineering discipline, a clear communication style, and a track record of shipping meaningful work that holds up well in production.

    Responsibilities

    • Extract maximum throughput, minimize latency, and reduce cost across training and inference workloads for large neural network systems.
    • Span