Technical Marketing Engineer

We need to output HTML fragment with sections: About the role? The posting includes intro paragraph about UCT, then description of role, duties, knowledge/skills, education, work environment, physical demands. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we only include sections that have real specific content. The posting does not mention Benefits, Pay, Schedule. So we should not include those headings. We can include About the role (intro), Responsibilities (duties), Requirements (maybe knowledge/skills and experience), Qualifications (education, certifications), Skills (maybe separate? but we have knowledge/skills and experience; could combine). The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should only include sections with real content. So we can have About the role, Responsibilities, Requirements, Qualifications, Skills. Possibly also Work Environment? Not in list but we could treat as part of About the role? Better to stick to allowed headings. However we could also add a section like Work Environment if we consider it as part of About the role? The instruction says use those headings for section headings (e.g. ...). It doesn't forbid other headings, but says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. We'll include those that have content. Let's extract content: About the role: The introductory 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 Engineer III to join us in Hillsboro, OR! The Technical Marketing Engineer for Data Center Cooling and Infrastructure serves as the bridge between engineering, business development, and customer technical teams. This role is responsible for defining standardized TRW/TCW skid platforms and supporting customer engagements related to liquid cooling infrastructure used in hyperscale and colocation data centers. The position focuses on translating engineering capabilities into customer-ready product platforms, technical documentation, and proposal support. The Technical Marketing Engineer will work closely with engineering and sales teams to ensure system designs align with customer requirements, industry standards, and scalable manufacturing practices." That's the role description. Responsibilities: The list under "Duties and Responsibilities:" bullet points. We need to put each as

inside

. Responsibilities list: - Define and develop standardized TRW/TCW skid system platforms for data center cooling applications. - Generate technical documentation including system architecture diagrams, P&IDs, general arrangement drawings, and technical submittals. - Support business development teams during customer meetings by providing technical expertise and system architecture guidance. - Evaluate customer specifications and translate requirements into scalable system designs. - Develop product positioning materials including technical presentations, application notes, and system capability documentation. - Collaborate with engineering and manufacturing teams to ensure designs align with fabrication and assembly capabilities. - Support RFQ responses by preparing technical proposals and assisting with scope definition. - Analyze competing cooling infrastructure solutions to identify opportunities for product differentiation and improvement. - Develop standard testing procedures, documentation templates, and system configuration guidelines for cooling skid platforms. Requirements: Could be "Knowledge, Skills and Experience:" section includes Minimum Qualifications and Preferred Qualifications. We could split into Requirements (minimum) and Qualifications (preferred) but we have separate headings for Requirements and Qualifications. Let's treat Requirements as Minimum Qualifications, and Qualifications as Preferred Qualifications plus Education, Certifications. But we also have Education, Certifications, and Requirement section. That could go under Qualifications. Skills: Could be the skills listed in Minimum Qualifications: ability to interpret docs, communication skills, collaboration. We need to avoid duplication. Let's structure:

About the role

...

Responsibilities

...

Requirements

maybe list Minimum Qualifications items? They are sentences. Could be

for prose? The instruction: Use

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

  for prose. So if we have a list of requirements, we should use

  . Minimum Qualifications are a list of items. Let's list them: - 5+ years of experience in mechanical engineering, applications engineering, or technical product marketing. - Experience working with fluid systems, pump skids, heat exchangers, or chilled water infrastructure. - Ability to interpret and develop engineering documentation including P&IDs, general arrangement drawings, and system diagrams. - Strong written and verbal communication skills with the ability to explain technical concepts to both engineering and commercial audiences. - Experience collaborating across engineering, manufacturing, and sales teams to support product development or customer projects. That's a list.

  Qualifications

  We could include Preferred Qualifications and Education, Certifications. Preferred Qualifications list: - Experience with data center cooling infrastructure or mission-critical mechanical systems. - Familiarity with liquid cooling architectures including coolant distribution units and heat exchanger systems. - Experience using CAD or engineering design tools such as SolidWorks, Inventor, or similar platforms. - Background in semiconductor or advanced manufacturing equipment systems. - Experience supporting technical proposals or system applications engineering. Education, Certifications, and Requirement: Minimum Education and Certification Qualifications: Bachelor’s Degree in Mechanical Engineering, Chemical Engineering, or related technical field. Preferred Education and Certification Qualifications: Professional engineering certification or advanced technical degree preferred. We could present as
  for each? Might be better to have

  for prose? But they are list-like. We'll use

  . We could combine Preferred Qualifications and Education into one Qualifications section with two sublists? But we need to keep it simple: maybe separate headings? Not allowed. We'll just put all items in one
  under Qualifications. But we need to differentiate minimum vs preferred? Not required. Skills: Could be the skills like communication, collaboration, ability to interpret docs. But we already covered those in Requirements. Might be redundant. Perhaps we can omit Skills section if content overlaps. The instruction: Prefer a few substantive sections over many thin ones. So we could skip Skills if it's thin. Thus sections: About the role, Responsibilities, Requirements, Qualifications. Check for any mention of Benefits, Pay, Schedule: none, so omit. Now ensure we preserve all substantive information: we have included intro, duties, minimum qualifications, preferred qualifications, education. Also we have work environment and physical demands not included. Those are substantive but not covered by allowed headings. Should we include them? The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use

  for section headings (e.g. ...). It might be okay to add other headings like Work Environment, Physical Demands. However they said "Prefer a few substantive sections over many thin ones." Adding Work Environment and Physical Demands would be extra sections. But they are substantive. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This could be interpreted as you should use those headings when applicable, but you can also use other headings if needed? The examples are just examples. Safer to stick to those headings only. However we would lose work environment and physical demands info. The instruction says "Preserve ALL substantive information". So we must include that info somewhere. If we cannot add a heading for it, we could fold it into About the role or Responsibilities as prose. That would preserve it. So we can add a paragraph about Work Environment and Physical Demands within About the role or maybe a separate paragraph after Responsibilities but without a heading? The instruction says use

  for section headings (e.g. ...). It doesn't forbid having paragraphs without headings. So we can include a

  for work environment and physical demands after the sections, maybe as part of About the role? Better to add a

  after Qualifications with that info, no heading. That preserves info. Thus final 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 Engineer III to join us in Hillsboro, OR! The Technical Marketing Engineer for Data Center Cooling and Infrastructure serves as the bridge between engineering, business development, and customer technical teams. This role is responsible for defining standardized TRW/TCW skid platforms and supporting customer engagements related to liquid cooling infrastructure used in hyperscale and colocation data centers. The position focuses on translating engineering capabilities into customer-ready product platforms, technical documentation, and proposal support. The Technical Marketing Engineer will work closely with engineering and sales teams to ensure system designs align with customer requirements, industry standards, and scalable manufacturing practices.

  Responsibilities

  • Define and develop standardized TRW/TCW skid system platforms for data center cooling applications.
  • Generate technical documentation including system architecture diagrams, P&IDs, general arrangement drawings, and technical submittals.
  • Support business development teams during customer meetings by providing technical expertise and system architecture guidance.
  • Evaluate customer specifications and translate requirements into scalable system designs.
  • Develop product positioning materials including technical presentations, application notes, and system capability documentation.
  • Collaborate with engineering and manufacturing teams to ensure designs align with fabrication and assembly capabilities.
  • Support RFQ responses by preparing technical proposals and assisting with scope definition.
  • Analyze competing cooling infrastructure solutions to identify opportunities for product differentiation and improvement.
  • Develop standard testing procedures, documentation templates, and system configuration guidelines for cooling skid platforms.

  Requirements

  • 5+ years of experience in mechanical engineering, applications engineering, or technical product marketing.
  • Experience working with fluid systems, pump skids, heat exchangers, or chilled water infrastructure.
  • Ability to interpret and develop engineering documentation including P&IDs, general arrangement drawings, and system diagrams.
  • Strong written and verbal communication skills with the ability to explain technical concepts to both engineering and commercial audiences.
  • Experience collaborating across engineering, manufacturing, and sales teams to support product development or customer projects.

  Qualifications

  • Experience with data center cooling infrastructure or mission-critical mechanical systems.
  • Familiarity with liquid cooling architectures including coolant distribution units and heat exchanger systems.
  • Experience using CAD or engineering design tools such as SolidWorks, Inventor, or similar platforms.
  • Background in semiconductor or advanced manufacturing equipment systems.
  • Experience supporting technical proposals or system applications engineering.
  • Bachelor’s Degree in Mechanical Engineering, Chemical Engineering, or related technical field.
  • Professional engineering