Foundry Process & Equipment Lead

We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes: Overview (maybe About the role? Actually "Why this work matters", "Overview", "What you will own", "Technical territory", "Representative outputs", "What success looks like", "What you bring", "Helpful experience", "How the role works". Also mention "Applications are open; the exact work location, arrangement, compensation, and start date will be discussed during hiring." No specific compensation or schedule given, so we should NOT create Pay or Schedule sections because they are not stated. Benefits not mentioned. So we should include sections like About the role (maybe Overview), Responsibilities (What you will own), Requirements/Qualifications (What you bring, Helpful experience), Skills maybe? Could combine. But we must not create empty sections. We need to use

for section headings. Use

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

  for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. No navigation, EEO, etc. There's none. We need to output only HTML fragment. Let's parse content: - Title: Open role Foundry Process & Equipment Lead (but we do NOT repeat job title as heading). So we start with sections. - Why this work matters: paragraph. - Overview: paragraph. - What you will own: list of bullet points? It's a paragraph with several sentences each starting with a verb. Could treat as list. - Technical territory: paragraph. - Representative outputs: list of bullet points. - What success looks like: paragraph with bullet-like sentences. - What you bring: list of bullet points. - Helpful experience: list. - How the role works: paragraph. We need to decide headings: About the role (maybe combine Why this work matters + Overview). Responsibilities (What you will own). Requirements (maybe Technical territory? Actually technical territory is domain knowledge). Qualifications (What you bring). Skills (Helpful experience). Could also have a section for Representative outputs? Not a standard heading but we could include under Responsibilities or maybe a separate section like "Key Deliverables". But the instruction says use headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must map content to those headings only. We cannot create other headings like "Representative outputs". We need to embed that content under appropriate headings. Thus we need to decide which heading each piece fits. - About the role: could include Why this work matters + Overview. - Responsibilities: What you will own + Representative outputs (since those are outputs/deliverables) + maybe How the role works? Actually How the role works describes process, could be part of Responsibilities. - Requirements: maybe Technical territory (knowledge required) + What you bring? Actually What you bring is qualifications. Requirements could be "What you bring" (experience). But we have separate Qualifications and Skills headings. Usually Requirements = qualifications needed. Skills = specific skills. We'll allocate: - Qualifications: What you bring (released semiconductor or advanced-packaging processes; led a process through qualification; can review tool capability; can make documented recommendation; experience coordinating; ability to translate spec). - Skills: Helpful experience (high-mix packaging, equipment installation, tool acceptance, cost-of-ownership modeling, customer qualification, external foundry transfer). - Requirements: Technical territory (semiconductor and advanced-package process flows; equipment capability; process windows and metrology; safety and utilities; supplier transfer; qualification, yield, cycle time, cost of ownership, independent release authority). This is more like knowledge domain. - Benefits: none given, so omit. - Pay: none given, omit. - Schedule: none given, omit. We must not create sections with filler. So we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills. Now we need to format content: Use

  for prose,

  • for any list of duties/requirements/benefits. We need to decide which parts are lists. - About the role: two paragraphs: Why this work matters and Overview. Could combine into one

    with two sentences? Better separate

    each. - Responsibilities: What you will own (list of bullet-like sentences) and Representative outputs (list). Also How the role works (maybe prose). We'll treat What you will own as

    • . Representative outputs as another
      • . How the role works as

        . - Requirements: Technical territory paragraph (maybe a list? It's a sentence with semicolons; could be a list but it's a paragraph). We'll treat as

        . - Qualifications: What you bring list of bullet-like sentences ->

        • . - Skills: Helpful experience list ->
          • . We must preserve all substantive information, not invent or summarize away detail. So we need to copy the exact sentences. Let's extract text exactly. From posting: "Why this work matters Touchdown is engineering the manufacturing behind storage, memory systems, and other chips. This role helps turn a buyer's physical result into a qualified process or a defensible decision to use an existing supplier. Advanced packaging is our intended first fab class; no production fab is operating today." We need to keep that as is. "Overview This is the technical lead for deciding what physical work Touchdown should attempt first. Start with a customer's workpiece and accepted output, compare a qualified outside route with an owned process, and define the people, site, tools, utilities, controls, and capital each would require. The job includes saying no when a safer or stronger supplier wins. No production fab or first process has been selected." Now "What you will own Own the first-process comparison, process/equipment team, technical rejection, and qualified work boundary.Compare a merchant or partner route with any proposed internal process against the same customer workpiece and acceptance test.Set process-owner, equipment-owner, EHS, quality, and independent release responsibilities before physical trials.Reject a route when safety, rights, utility, cost, yield, or supplier evidence is missing.Build a stage-gated process plan connecting customer acceptance, sample size, measurement, repeatability, and ownership of each release.Lead cross-discipline reviews of tool readiness, process capability, supplier evidence, and the cost of a rejected lot." We need to split into list items. Each sentence starts with a verb. We'll make each as
          • . Now "Technical territory Semiconductor and advanced-package process flows; equipment capability and matching; process windows and metrology; safety and utilities; supplier transfer; qualification, yield, cycle time, cost of ownership, and independent release authority." Now "Representative outputs A first-process decision packet with candidate workpiece, process, partner baseline, site/tool requirements, qualified owners, cost, and stop conditions.A role and authority map that names who can hold, reject, and release work.A gated trial plan with sample size, measurements, cost ceiling, and failure response.A technical decision log with the chosen route, rejected alternatives, evidence gaps, capital exposure, and the next stop or promotion gate." Now "What success looks like The first process decision can be reviewed against an external route.No physical work begins without qualified people, site access, safety review, and written authorization.The team can explain why this process and workpiece merit a controlled trial before purchasing a tool or committing a site.A quality or safety owner can stop the work without relying on the process lead's permission." Now "What you bring Released semiconductor or advanced-packaging processes; equipment, safety, supplier, and transfer judgment.Led a semiconductor or packaging process through qualification, transfer, or production release.Can review tool capability, process windows, utilities, maintenance, and vendor service together.Can make a documented buy, partner, build, or stop recommendation with incomplete data.Experience coordinating process, equipment, facilities, quality, and product engineers through a formal release decision.Ability to translate a customer specification into measurable process capability, supplier comparisons, and a capital decision." Now "Helpful experience High-mix packaging or heterogeneous integrationEquipment installation and process transferTool acceptance and factory start-upCost-of-ownership and capacity modelingCustomer qualification and external foundry transfer" Now "How the role works Applications are open; the exact work location, arrangement, compensation, and start date will be discussed during hiring.Early work can produce engineering plans and partner comparisons. Hands-on work begins only at qualified, authorized facilities.You will work with process, equipment, quality, test, customer, and supplier owners as the scope requires." Now we need to ensure we don't include boilerplate like "Apply for this role → Show a real process..." That's application instruction, we must remove. Also the line "Show a real process, tool, workpiece, or product decision you owned, the measurements behind it, and what another team could reproduce." That's also application instruction. Remove. Now produce HTML. We'll start with

            About the role

            then two

            paragraphs. Then

            Responsibilities

            then maybe a

            for How the role works? Actually How the role works is more about how role works, could be part of Responsibilities. We'll put it as a

            after the lists. We need to decide ordering: Responsibilities: What you will own (list), Representative outputs (list), How the role works (p). Could also include What success looks like? That seems like outcome metrics, could be part of Responsibilities? But we already have many sections; maybe we could put What success looks like under Responsibilities as well. However we must not create extra headings. We can embed that content under Responsibilities as a list or paragraph. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine What success looks like into Responsibilities as a list. Thus Responsibilities will contain: - What you will own (list) - Representative outputs (list) - What success looks like (list) - How the role works (p) That's a lot but still under one heading. Now Requirements: Technical territory (p). Qualifications: What you bring (list). Skills: Helpful experience (list). Now ensure we don't repeat any content inadvertently. Let's copy the exact sentences, preserving punctuation. I'll extract each piece. About the role: Paragraph1: "Why this work matters Touchdown is engineering the manufacturing behind storage, memory systems, and other chips. This role helps turn a buyer's physical result into a qualified process or a defensible decision to use an existing supplier. Advanced packaging is our intended first fab class; no production fab is operating today." Paragraph2: "Overview This is the technical lead for deciding what physical work Touchdown should attempt first. Start with a customer's workpiece and accepted output, compare a qualified outside route with an owned process, and define the people, site, tools, utilities, controls, and capital each would require. The job includes saying no when a safer or stronger supplier wins. No production fab or first process has been selected." Note: There's no period after "today." Actually original: "Advanced packaging is our intended first fab class; no production fab is operating today." We'll keep. Now Responsibilities: What you will own sentences: 1. "Own the first-process comparison, process/equipment team, technical rejection, and qualified work boundary." 2. "Compare a merchant or partner route with any proposed internal process against the same customer workpiece and acceptance test." 3. "Set process-owner, equipment-owner, EHS, quality, and independent release responsibilities before physical trials." 4. "Reject a route when safety, rights, utility, cost, yield, or supplier evidence is missing." 5. "Build a stage-gated process plan connecting customer acceptance, sample size, measurement, repeatability, and ownership of each release." 6. "Lead cross-discipline reviews of tool readiness, process capability, supplier evidence, and the cost of a rejected lot." Representative outputs: 1. "A first-process decision packet with candidate workpiece, process, partner baseline, site/tool requirements, qualified owners, cost, and stop conditions." 2