Wheel Design Engineer II
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content.
We have:
- About Us: "A Bit About Us Trek is an awesome place to work..." That's about company culture. Could be "About the role"? Actually "About the role" is typical heading for description of role. But we have "Job Description" which includes responsibilities. So we can have sections: About the role (maybe summarizing the role description?), Responsibilities (the bullet list under "YOU WILL"), Requirements/Qualifications/Skills (the "What You Need To Succeed" and "ALSO, OF INTEREST!" sections), Benefits (the "Trek Benefits:" list). No Pay or Schedule mentioned, so we omit those sections.
We must not repeat job title as heading. No Job ID etc.
We must preserve all substantive information, not invent or summarize away detail. Must not create sections with filler like "commensurate with experience". So we include only sections with real content.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all details: The "A Bit About Us" paragraph: "A Bit About Us Trek is an awesome place to work, with amazing benefits for all employees. We build only products we love, provide incredible hospitality to our customers, and change the world by getting more people on bikes. When you’re on our team, you’re taken care of, encouraged to learn and grow, and given lots of opportunities to do so. Give us your best, and we’ll give it right back. Sound pretty sweet? Then come join us!"
We need to keep that as prose under maybe "About the role"? Or maybe "About the company"? But headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the company". Could we use "About the role" for that paragraph? It's not exactly about the role but about the company. However we need to include a section only when posting has real specific content for it. The "A Bit About Us" is about company culture, not role specifics. Could we treat it as "About the role"? Might be okay but maybe better to not create a heading if not matching allowed headings? The instruction says: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says use for section headings (e.g. About the role, Responsibilities...). Likely they expect us to use those headings where appropriate. If we have content that doesn't fit any of those, maybe we should not create a heading? But we need to preserve all substantive information. Could we embed the "A Bit About Us" paragraph inside a
without a heading? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't say we must have headings for every paragraph. It said use
for section headings (e.g. About the role, Responsibilities...). So we can have headings for sections we decide to include, and other paragraphs without headings? Probably yes. But they said "Prefer a few substantive sections over many thin ones." So we can have sections like About the role (maybe combine A Bit About Us and role overview), Responsibilities, Requirements, Qualifications, Skills, Benefits.
We need to decide what goes where.
Responsibilities: The "YOU WILL" bullet list.
Requirements/Qualifications/Skills: The "What You Need To Succeed" and "ALSO, OF INTEREST!" could be split into Requirements (hard requirements) and Qualifications/Skills (preferred). But we can combine into one section "Requirements" with both required and preferred? The instruction: prefer few substantive sections over many thin ones. So maybe we have one section "Requirements" that includes all the needed qualifications and skills. Or we could have "Qualifications" and "Skills" separate but that would be thin. Better to have one "Requirements" section that includes both required and preferred.
Benefits: The list under "Trek Benefits:".
We must not include Pay or Schedule.
We must remove boilerplate: EEO, E-Verify, etc.
We must not include application instructions.
Now we need to format.
Structure:
About the role
A Bit About Us Trek is an awesome place to work, with amazing benefits for all employees. We build only products we love, provide incredible hospitality to our customers, and change the world by getting more people on bikes. When you’re on our team, you’re taken care of, encouraged to learn and grow, and given lots of opportunities to do so. Give us your best, and we’ll give it right back. Sound pretty sweet? Then come join us!
Job Description Are you looking to be part of a motivated team that is pushing the limits of product performance, bringing new and innovative wheels to riders everywhere? Do you love solving problems, iterating quickly, and delivering creative solutions? Do you want to work within a culture that embraces continuous learning and development of new skills through exposure to evolving opportunities? Trek’s engineering team is looking for a highly motivated and experienced engineer to come work in our inspiring work hard / play hard environment, take the lead on wheel design and development, and help create the next generation of road wheel products that will have a big impact on the cycling industry.
But note: The "Job Description" heading is not allowed as heading (we shouldn't repeat job title as heading, but "Job Description" is not a job title; but the instruction says use for section headings (e.g. About the role, Responsibilities...). It didn't forbid "Job Description". However they said "Do NOT repeat the job title as a heading (the page already shows it)". So we could use "Job Description" as a heading? But they gave examples of headings; maybe they expect us to use those specific headings. Safer to not add extra headings beyond those examples. So we could incorporate the Job Description paragraph into About the role or Responsibilities? The "Job Description" paragraph is more about the role overview, not specific duties. Could go under About the role.
Thus About the role section will contain both the "A Bit About Us" and the "Job Description" paragraph.
Then Responsibilities: list of YOU WILL items.
Then Requirements: combine What You Need To Succeed and ALSO, OF INTEREST! items.
Then Benefits: list of Trek Benefits.
We need to preserve all details exactly, not summarizing.
We need to convert bullet points into - . The original text uses line breaks and bullet points? It's a paragraph with sentences separated by periods. We need to parse each duty as separate item. The "YOU WILL" section: list of sentences each starting with a verb. We'll split by sentences.
Let's extract:
YOU WILL
Lead the technical design and development of road wheel systems, including carbon rims, hubs, and spoke/lacing configurations, focusing on aerodynamics, weight, stiffness, and durability from the concept phase through to production.
Create and deliver engineering specification packages that communicate effectively with internal and external partners to ensure products meet project requirements.
Translate customer and rider feedback into engineering specifications for wheel products.
Work with Trek racing teams to develop products that perform at the highest level, and provide expertise to bike groups, athletes, marketing, and other internal customers.
Develop collaborative relationships with vendors and coordinate engineering activities with domestic and international teammates, traveling as necessary.
Learn, create, and implement new engineering tools that will enable you and your teammates to create best-in-class products.
Mentor and provide technical guidance to other engineers, and own technical decisions across wheel programs.
Conduct patent searches, generate ideas, and stay informed of new technology through technical publications and seminars.
That's 8 items.
Now What You Need To Succeed:
Bachelor’s degree in mechanical engineering or equivalent, with 5+ years of experience in product development.
Experience with bicycle wheel design, build, and manufacturing.
Experience designing composite structures, including laminate/layup design, with an understanding of how material and process choices affect performance.
Execution experience of multiple project cycles from concept through to production.
Ability to iterate quickly on designs, with an eagerness to take a hands-on approach to rapid prototyping and identifying problems.
Experience using CAD modeling software (preferably Onshape) to create 3D models and 2D engineering drawings.
Ability to understand and apply GD&T methodology.
Skills in structural analysis, design failure risk analysis, design for manufacturing and assembly, test plan creation, troubleshooting test results, and creating technical documentation and reports.
Experience with wheel test development and validation, such as impact, fatigue, stiffness, and aerodynamic testing, and knowledge of relevant standards.
Ability to interpret data and solve complex problems, bringing a creative approach to open-ended technical problems with a drive to innovate!
Self-motivated and detail oriented, with strong planning, communication, and accountability skills in a fast-paced team environment working with domestic and international teammates.
That's many items; we need to split each sentence as separate
- . Some sentences have multiple clauses but we treat each sentence as an item.
Let's list them:
1. Bachelor’s degree in mechanical engineering or equivalent, with 5+ years of experience in product development.
2. Experience with bicycle wheel design, build, and manufacturing.
3. Experience designing composite structures, including laminate/layup design, with an understanding of how material and process choices affect performance.
4. Execution experience of multiple project cycles from concept through to production.
5. Ability to iterate quickly on designs, with an eagerness to take a hands-on approach to rapid prototyping and identifying problems.
6. Experience using CAD modeling software (preferably Onshape) to create 3D models and 2D engineering drawings.
7. Ability to understand and apply GD&T methodology.
8. Skills in structural analysis, design failure risk analysis, design for manufacturing and assembly, test plan creation, troubleshooting test results, and creating technical documentation and reports.
9. Experience with wheel test development and validation, such as impact, fatigue, stiffness, and aerodynamic testing, and knowledge of relevant standards.
10. Ability to interpret data and solve complex problems, bringing a creative approach to open-ended technical problems with a drive to innovate!
11. Self-motivated and detail oriented, with strong planning, communication, and accountability skills in a fast-paced team environment working with domestic and international teammates.
Now ALSO, OF INTEREST! items:
Experience with design analysis using FEA and CFD, and with wind tunnel testing.
Proficient in bike assembly and wheel building.
Experience researching and developing new testing methods and standards to improve performance and quality.
Knowledge of tire and rim interface standards (ETRTO / ISO) and tubeless system design.
Experience designing for manufacturing with composite materials, plastics, and metals, using processes such as bladder molding, compression molding, forging, CNC machining, and injection molding.
Positive attitude that fosters continuous improvement and flexibility.
That's 6 items.
We could combine all into Requirements section.
Now Benefits list:
Trek Benefits: Flexible and fun company culture Competitive health care PPO & HDHP medical plan options, Dental insurance, Vision insurance Flexible Spending Accounts (FSA) Free life insurance & optional term life insurance Competitive vacation package 401(k) with match and Employee Stock Ownership Plans (ESOP) 12 weeks of maternity leave with 100% pay Flexible holiday schedule – 10 company holidays Tuition Reimbursement up to $15,000! (Undergraduate & Masters programs) Employee discounts on all product Deep partner retail discounts
We need to split into sensible items. The text is a run-on sentence with commas. We can split by commas and "and". But better to keep as list items each representing
for prose. We need to preserve all details: The "A Bit About Us" paragraph: "A Bit About Us Trek is an awesome place to work, with amazing benefits for all employees. We build only products we love, provide incredible hospitality to our customers, and change the world by getting more people on bikes. When you’re on our team, you’re taken care of, encouraged to learn and grow, and given lots of opportunities to do so. Give us your best, and we’ll give it right back. Sound pretty sweet? Then come join us!" We need to keep that as prose under maybe "About the role"? Or maybe "About the company"? But headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the company". Could we use "About the role" for that paragraph? It's not exactly about the role but about the company. However we need to include a section only when posting has real specific content for it. The "A Bit About Us" is about company culture, not role specifics. Could we treat it as "About the role"? Might be okay but maybe better to not create a heading if not matching allowed headings? The instruction says: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says use for section headings (e.g. About the role, Responsibilities...). Likely they expect us to use those headings where appropriate. If we have content that doesn't fit any of those, maybe we should not create a heading? But we need to preserve all substantive information. Could we embed the "A Bit About Us" paragraph inside a
without a heading? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't say we must have headings for every paragraph. It said use
for section headings (e.g. About the role, Responsibilities...). So we can have headings for sections we decide to include, and other paragraphs without headings? Probably yes. But they said "Prefer a few substantive sections over many thin ones." So we can have sections like About the role (maybe combine A Bit About Us and role overview), Responsibilities, Requirements, Qualifications, Skills, Benefits.
We need to decide what goes where.
Responsibilities: The "YOU WILL" bullet list.
Requirements/Qualifications/Skills: The "What You Need To Succeed" and "ALSO, OF INTEREST!" could be split into Requirements (hard requirements) and Qualifications/Skills (preferred). But we can combine into one section "Requirements" with both required and preferred? The instruction: prefer few substantive sections over many thin ones. So maybe we have one section "Requirements" that includes all the needed qualifications and skills. Or we could have "Qualifications" and "Skills" separate but that would be thin. Better to have one "Requirements" section that includes both required and preferred.
Benefits: The list under "Trek Benefits:".
We must not include Pay or Schedule.
We must remove boilerplate: EEO, E-Verify, etc.
We must not include application instructions.
Now we need to format.
Structure:
About the role
A Bit About Us Trek is an awesome place to work, with amazing benefits for all employees. We build only products we love, provide incredible hospitality to our customers, and change the world by getting more people on bikes. When you’re on our team, you’re taken care of, encouraged to learn and grow, and given lots of opportunities to do so. Give us your best, and we’ll give it right back. Sound pretty sweet? Then come join us!
Job Description Are you looking to be part of a motivated team that is pushing the limits of product performance, bringing new and innovative wheels to riders everywhere? Do you love solving problems, iterating quickly, and delivering creative solutions? Do you want to work within a culture that embraces continuous learning and development of new skills through exposure to evolving opportunities? Trek’s engineering team is looking for a highly motivated and experienced engineer to come work in our inspiring work hard / play hard environment, take the lead on wheel design and development, and help create the next generation of road wheel products that will have a big impact on the cycling industry.
But note: The "Job Description" heading is not allowed as heading (we shouldn't repeat job title as heading, but "Job Description" is not a job title; but the instruction says use