Engineering Co-op, Advanced Manufacturing Group

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title. We must not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove Export Statement? It's not boilerplate but it's a requirement; but it's not a section heading we have. Could be part of Requirements? Might be considered a requirement. But we can include it under Requirements or Qualifications? The instruction: "Prefer a few substantive sections over many thin ones." So we can combine. We need to preserve all substantive information: About TTM (company description), Scope (Engineering Co-op description), Duties and Responsibilities (list), Essential Knowledge and Skills (list), Education and Experience (list), Compensation and Benefits (list benefits, note compensation varies). Also Export Statement (maybe as part of Requirements). Also note about benefits availability. We must not include sections with placeholder like "commensurate with experience". Compensation: they say varies depending on factors, and mention ranges for certain states. That's substantive enough to include a Pay section? They say compensation varies; not a specific number. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. For Pay, they state compensation varies depending on factors, and mention ranges for certain states. That's not a specific number but it's still stating something. Is "varies" considered placeholder? The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So if we put Pay section and the content is just "varies", that's not allowed. However we could include more detail: they mention compensation varies depending on factors including office location, role, skill set, level of experience. Also mention that as required by local law, TTM provides a reasonable range of compensation for roles that may be hired in New York, California and Colorado. For California-based roles, compensation ranges are based upon specific physical locations. That's more than just "varies". It gives some info. So we could include a Pay section with that description. Benefits: they list medical, dental, vision, 401K, FSA, HSA, accident benefits, life insurance, disability benefits, paid vacation & holidays. Also note benefits available 1st of month following date of hire. That's substantive. Schedule: not mentioned. So we should not create Schedule section. Thus sections: About the role (maybe "About the role" or "About TTM"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings when appropriate. For company description we could use "About the role"? Actually "About the role" is about the role, not company. But we have "Scope" describing the co-op role. Could use "About the role" heading for that. Or we could use "About TTM" but not in list. 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 suggests using those. Safer to use those headings where applicable. Thus:

About the role

- contain description of scope: Engineering Co-op in Advanced Manufacturing Group works across team, assigned to one of three areas, work directly for early career engineer.

Responsibilities

- list duties: Mechatronics, Electrical Engineering, Industry 4.0, plus shop team duties.

Requirements

- maybe combine Essential Knowledge and Skills, Education and Experience, Export Statement? Could be separate: Requirements and Qualifications. But we prefer few sections. Could have "Requirements" covering Essential Knowledge and Skills, Education and Experience, Export Statement. Or split into Requirements and Qualifications. Let's see: Essential Knowledge and Skills is more like skills/attributes. Education and Experience is qualifications. Could combine. We could do:

Requirements

- list essential knowledge and skills (bullet list) and education/experience (bullet list) and export statement (maybe as a note).

Benefits

- list benefits.

Pay

- description of compensation variability and ranges. We must not include schedule. We must not include duplicated lines. Ensure we preserve all substantive info. Let's extract details: About TTM: "TTM Technologies, Inc. is a leading global manufacturer of technology products, including mission systems, radio frequency (“RF”) components, RF microwave/microelectronic assemblies, and technologically advanced printed circuit boards (“PCB”s). TTM stands for time-to-market, representing how TTM's time-critical, one-stop design, engineering and manufacturing services enable customers to reduce the time required to develop new products and bring them to market. Additional information can be found at www.ttm.com" Scope: "An Engineering Co-op in Advanced Manufacturing Group works across our team to contribute to our work and to learn practical engineering skills to advance their own development as an engineer. You will be assigned (by preference and inclination to one of three areas of work, and work directly for one of our early career engineers." Duties and Responsibilities: - Mechatronics: Assemble, Test, Design and Build robotic workcells and advanced machine tools - Electrical Engineering: Learn, practice, test, evaluate and recommend processes for electronics manufacturing and design for manufacturing. Test machines, troubleshoot, debug, and recommend improvements. - Industry 4.0: Develop, Test, and Deploy industry leading software for connecting the factory, multiple factories, and empowering end users. Work with the users of software to better understand what can be improved for their experience. - Participate in shop team duties to include general purpose test, drafting, cleaning, installation of equipment Note: The statements herein are intended to describe the general nature and level of work being performed by employees, and are not to be construed as an exhaustive list of responsibilities, duties, and skills required of personnel. Furthermore, they do not establish a contract for employment and are subject to change at the discretion of the employer. Essential Knowledge and Skills: - Confident willingness to learn, grow and contribute in a hands on environment. - Demonstrated ability to solve problems for a team and push for better parts, systems, etc. - Participate in Formula Teams or other Engineering Club - Research independently and think of new solutions - Enjoy working with diverse teams of technicians and engineers - Want to do something different - Likes the idea of a startup environment in a different field - Passion for designing and building things and desire to improve skills Education and Experience: - Education: Currently enrolled in an engineering or technical program and will have completed 2 semesters or equivalent instruction or self-study. - Preferred Experience: Engineering Clubs, Volunteer Projects, Jobs that stressed mechanical, electrical, software aptitude Compensation and Benefits: - TTM offers a variety of health and well-being benefit programs. Benefit options include medical, dental, vision, 401K, Flexible Spending Account, Health Savings Account, accident benefits, life insurance, disability benefits, paid vacation & holidays. Benefits are available 1st of the month following date of hire. - Compensation for roles at TTM Technologies varies depending on a wide array of factors including but not limited to the specific office location, role, skill set and level of experience. As required by local law, TTM provides a reasonable range of compensation for roles that may be hired in New York, California and Colorado. For California-based roles, compensation ranges are based upon specific physical locations. Export Statement: Must comply with TTM Export Control Policies and Procedures and all applicable laws including ITAR, EAR and OFAC including but not limited to: a) being able to identify ITAR product on the manufacturing floor and understand that access to these products and related technical data is restricted to only US Citizens and US Permanent Residents; b) recognition of Foreign Person visitors by badge differentiation; c) understand and follow authorization procedures for bringing foreign visitors into facilities (VAL); d) understand the Export and ITAR requirements for shipments leaving the US; e) manage vendor approvals for ITAR manufacturing and services. EEO statement: All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, citizenship, disability or protected veteran status. (Remove as boilerplate) Now construct HTML. We'll have:

About the role

... (scope + maybe company description? Actually About the role could include scope and maybe brief company description? But we have separate About TTM description. Could put company description under About the role as well, but it's about company. Might be okay. But we could also add a separate

About TTM

but not in list. Safer to put company description under About the role? The instruction says use those headings for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings but suggests using those. I'd include company description in About the role as it's about the role context. Or we could add a

About TTM

but that deviates. I'd keep to the list. Thus About the role paragraph includes both company description and scope? Might be long but okay. Better: About the role: description of the co-op role (scope). Company description could be placed in a preceding paragraph before any heading? The instruction says output only HTML fragment, no extra text outside headings? It didn't forbid stray paragraphs before first heading. But to be safe, we can include a brief intro paragraph before headings? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It doesn't say we cannot have stray paragraphs. However typical answer expects sections with headings. I'd put a

for company description before the first heading? Might be considered not part of a section. But maybe okay. Alternatively, we can include company description inside About the role heading as a paragraph. Thus:

About the role

TTM Technologies, Inc. is a leading global manufacturer of technology products, including mission systems, radio frequency (“RF”) components, RF microwave/microelectronic assemblies, and technologically advanced printed circuit boards (“PCB”s). TTM stands for time-to-market, representing how TTM's time-critical, one-stop design, engineering and manufacturing services enable customers to reduce the time required to develop new products and bring them to market. Additional information can be found at www.ttm.com. An Engineering Co-op in Advanced Manufacturing Group works across our team to contribute to our work and to learn practical engineering skills to advance their own development as an engineer. You will be assigned (by preference and inclination to one of three areas of work, and work directly for one of our early career engineers.

Then Responsibilities:

Responsibilities

• Mechatronics: Assemble, Test, Design and Build robotic workcells and advanced machine tools
• Electrical Engineering: Learn, practice, test, evaluate and recommend processes for electronics manufacturing and design for manufacturing. Test machines, troubleshoot, debug, and recommend improvements.
• Industry 4.0: Develop, Test, and Deploy industry leading software for connecting the factory, multiple factories, and empowering end users. Work with the users of software to better understand what can be improved for their experience.
• Participate in shop team duties to include general purpose test, drafting, cleaning, installation of equipment

We could also include the note about