Director, Data Center Business Development

We need to output HTML fragment with sections: About the role? The posting includes intro paragraphs about UCT, then role description. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real, specific content. We have content for About the role (intro), Responsibilities (list), Knowledge, Skills and Experience (which includes Minimum Qualifications, Preferred Qualifications). Also Education, Certifications, and Requirement. Work Environment, Physical Demands. Benefits, Pay, Schedule not mentioned. So we should not include those sections. We need to preserve all substantive info, not invent. Remove boilerplate like EEO, equal opportunity, etc. Also remove navigation, cookie, legal, application instructions. There's no explicit application instructions but there is EEO statement; we remove that. We need to format using

headings,

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

  for prose. We need to decide sections: About the role (intro), Responsibilities (duties), Requirements (maybe Minimum Qualifications?), Qualifications (maybe Preferred Qualifications?), Skills (maybe combine?), but we need to avoid thin sections. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements, Qualifications, Skills into one section? But they said use headings for those categories if content exists. However we can decide to include only sections with substantive content: About the role, Responsibilities, Knowledge, Skills and Experience (maybe as Requirements), Education, Certifications, and Requirement (maybe as Qualifications), Work Environment, Physical Demands. But we must not create sections with filler like "commensurate with experience". We have actual content. We need to ensure we don't repeat job title as heading. The job title is Director, Data Center Business Development. Not to repeat. We need to output only HTML fragment, no /, no markdown. Let's extract content: Intro paragraph: "Join UCT and be part of the fastest-growing sector in the world! We indirectly touch every semiconductor chip that goes into every smartphone, smart car, and device that uses artificial intelligence. This is a critical time for the semiconductor industry and for UCT - as technology evolves, we evolve with it. UCT is a diverse workplace where every talented employee is committed to continuous innovation, challenging the status quo and exceeding customer expectations. If you are a person with a relentless drive to succeed, a strong focus on quality with a passion for success - join us today! UCT is looking for a talented Director, Data Center Business Development to join us in Hillsboro, OR!" Then role description: "The Director of Data Center Business Development is responsible for establishing and expanding the company’s presence in the rapidly growing data center cooling infrastructure market. This role will develop strategic customer relationships, identify project opportunities, and lead capture efforts for liquid cooling systems including TRW/TCW skid platforms used in hyperscale and colocation data centers.This is a highly strategic role focused on building a new vertical market. The Director will work closely with engineering, product development, and executive leadership to position the company as a preferred supplier of engineered cooling skids and fluid handling systems. Success in this role will be measured by pipeline development, awarded backlog, and the establishment of long-term relationships with hyperscale operators, cooling system OEMs, and mechanical contractors." Then "Duties and Responsibilities:" followed by list items: - Develop and execute the market entry strategy for data center liquid cooling infrastructure systems. - Identify and pursue project opportunities with hyperscale data center operators, colocation providers, and engineering contractors. - Build strategic relationships with cooling system OEMs, mechanical contractors, and engineering firms supporting large data center campuses. - Lead capture strategy and commercial negotiations for pump skid and liquid cooling system programs. - Collaborate with engineering and product teams to align customer requirements with scalable TRW/TCW skid platform offerings. - Maintain a robust opportunity pipeline and provide regular reporting on project status, market trends, and competitive positioning. - Support proposal development, pricing strategy, and technical positioning during RFQ and bidding processes. - Represent the company at industry events, customer meetings, and technical discussions related to data center infrastructure. - Provide voice-of-customer feedback to guide product development and platform standardization. Then "Knowledge, Skills and Experience:" with Minimum Qualifications list: - 8+ years of experience in business development, strategic sales, or capture management within data center infrastructure, mission-critical mechanical systems, or industrial equipment markets. - Demonstrated success developing new business opportunities and closing multi-million-dollar system or equipment programs. - Experience working with hyperscale data center operators, mechanical contractors, or cooling infrastructure OEMs. - Strong written and verbal communication skills, including experience presenting proposals and technical concepts to executive and engineering audiences. - Proven ability to build strategic customer relationships and lead complex commercial negotiations. - Ability to manage long sales cycles and coordinate cross-functional teams to support opportunity capture. Preferred Qualifications list: - Experience selling or supporting liquid cooling systems, pump skids, heat exchanger systems, or chilled water infrastructure. - Prior experience working with hyperscale or colocation data center customers. - Background in mechanical engineering, industrial systems, or fluid handling technologies. - Experience supporting capital infrastructure projects in data center, semiconductor, or mission-critical environments. - Familiarity with engineering procurement and construction (EPC) project structures. Then "Education, Certifications, and Requirement:" list: - Bachelor’s Degree in Engineering, Business, or related technical field. - Master’s Degree in Business Administration (MBA) or Engineering preferred. Then "Work Environment:" paragraph: "This role is primarily office-based with regular interaction with engineering teams and manufacturing operations. The position may require visits to manufacturing facilities and customer sites. Travel expectations include occasional domestic travel (approximately 25-40%) to support customer meetings, project development, and industry events." Then "Physical Demands:" paragraph: "This role primarily involves desk-based work including extended periods of sitting and computer use. Occasional travel to manufacturing environments may require walking on production floors and wearing appropriate personal protective equipment." Then EEO boilerplate to remove. We need to decide sections. We could have:

  About the role

  with intro paragraph(s).

  Responsibilities

  with
  • list.

    Requirements

    maybe combine Minimum Qualifications and Preferred Qualifications? But they are separate. Could have

    Minimum Qualifications

    and

    Preferred Qualifications

    but those are not in the allowed headings list (they listed Requirements, Qualifications, Skills). The allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to those headings. We can put Minimum Qualifications under Requirements, Preferred Qualifications under Qualifications, and maybe Skills under Skills (but we have skills listed in Minimum Qualifications). However we could combine skills into Requirements or Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But they said use headings for those categories if content exists. However we can decide to include only sections with substantive content: About the role, Responsibilities, Requirements (including both minimum and preferred), Education, Certifications (maybe under Requirements?), Work Environment, Physical Demands. But we need to follow the allowed headings list; we cannot invent headings like Education, Certifications, Work Environment, Physical Demands unless they map to allowed headings. The allowed headings are limited; we cannot add others. So we must fit content into those headings only. That means we can only use those headings. If we have content that doesn't fit, we need to embed it under appropriate heading or maybe not include a heading and just use

    ? The instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples, but likely they expect only those headings. It says "include a section ONLY when the posting has real, specific content for it". So we can only create those headings if we have content for them. If we have content that doesn't map, we could still include it under a relevant heading like Requirements or Skills. For example, Education could go under Requirements or Qualifications. Work Environment could go under Skills? Not really. Physical Demands maybe under Skills? Not ideal. But we could omit those sections if they don't fit allowed headings? But we must preserve ALL substantive information. So we need to include that info somewhere. We could put Work Environment and Physical Demands under a generic heading like "Requirements" or "Skills"? Might be a stretch but acceptable. Better: Use "Requirements" for minimum qualifications, "Qualifications" for preferred qualifications and education, "Skills" for skills/competencies, and maybe "About the role" for intro, "Responsibilities" for duties. Then we still have Work Environment and Physical Demands; we could add them under "Skills" as well? Or maybe we can create a section "Work Environment" but it's not in the allowed list; risk of being rejected. The instruction says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not an exhaustive list. So we could use other headings if needed, but they gave examples. However they also say "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could create headings for Work Environment and Physical Demands if we have content. The examples are not restrictive. So we can add headings like Work Environment, Physical Demands. That seems okay. Thus we can output sections: About the role, Responsibilities, Requirements (minimum qualifications), Qualifications (preferred qualifications + education), Skills (maybe communication skills etc), Work Environment, Physical Demands. But we need to avoid thin sections. Each should have substantive content. Let's map: About the role: intro paragraphs (two paragraphs maybe combine into one

    ). Responsibilities: list of duties. Requirements: Minimum Qualifications list. Qualifications: Preferred Qualifications list plus Education, Certifications, and Requirement (Bachelor's, Master's preferred). Could combine. Skills: maybe we could extract skills from Minimum Qualifications (communication, relationship building, negotiation, managing sales cycles, cross-functional coordination). But those are already in Requirements. Could instead put Skills as communication, relationship building, negotiation, etc. But we might duplicate. Better to not have Skills section if it's thin; we can omit. Work Environment: paragraph. Physical Demands: paragraph. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Work Environment, Physical Demands. Check if any content missing: The "Knowledge, Skills and Experience" heading includes both Minimum and Preferred Qualifications. We split them. Education is under Qualifications. Now we need to ensure we don't repeat job title as heading. Not. We must not include boilerplate EEO. Now produce HTML:

    About the role

    Join UCT and be part of the fastest-growing sector in the world! We indirectly touch every semiconductor chip that goes into every smartphone, smart car, and device that uses artificial intelligence. This is a critical time for the semiconductor industry and for UCT - as technology evolves, we evolve with it. UCT is a diverse workplace where every talented employee is committed to continuous innovation, challenging the status quo and exceeding customer expectations. If you are a person with a relentless drive to succeed, a strong focus on quality with a passion for success - join us today! UCT is looking for a talented Director, Data Center Business Development to join us in Hillsboro, OR!

    The Director of Data Center Business Development is responsible for establishing and expanding the company’s presence in the rapidly growing data center cooling infrastructure market. This role will develop strategic customer relationships, identify project opportunities, and lead capture efforts for liquid