Senior Product Engineer
About the role
thenwith description. - Responsibilities: The "Helping You Thrive By:" bullet points are more about benefits? Actually they are about what Steelcase offers: competitive wages, learning, inclusion, impact. Those could be Benefits? But they are more about company offerings. Could be Benefits section. However responsibilities might be the duties: "create, develop, and implement new products", "work with other product developers", maybe also "envision how product and manufacturing processes can be developed together", etc. The "Who You Are" list is more about qualifications/skills. The "Minimum Qualifications" and "Desired Skills And Experience" are qualifications/skills. Thus we need to map. Responsibilities: The core duties: "create, develop, and implement new products", "work in Storage Solutions team with other product developers", "create, develop, and implement new products", maybe also "apply mechanical engineering principles", "define performance requirements on engineering drawings", "tolerance analysis", "prototyping", etc. Those are more qualifications. But we can extract responsibilities from the first paragraph: "We are hiring a Senior Product Engineer to work in our Storage Solutions team with other product developers to create, develop, and implement new products." Also maybe "Helping You Thrive By:" is not responsibilities but benefits. Thus we can have Responsibilities section with bullet list: - Collaborate with product developers in the Storage Solutions team to create, develop, and implement new products. - Contribute to the design of thoughtfully designed workplace storage solutions that support flexibility, mobility, efficient use of space. - Ensure integration of storage solutions into various work environments, providing secure personal storage, shared team storage, and architectural elements enhancing functionality and aesthetics. - Apply human-centered approach to develop storage products that promote productive, clutter-free spaces and better employee experience. But we must not invent details not in posting. The posting includes description of team and its purpose. We can use that as responsibilities? It's more about what the team does, not necessarily the role's duties. However we can infer that the role contributes to those. Might be okay as long as we don't invent. The posting says: "The Steelcase Storage Solutions team provides thoughtfully designed workplace storage that helps individuals and teams stay organized while supporting flexibility, mobility, and efficient use of space. These solutions integrate seamlessly into a variety of work environments, offering secure personal storage, shared team storage, and architectural elements that enhance both functionality and aesthetics. Designed with a human-centered approach, Steelcase storage products help create productive, clutter-free spaces that support changing workstyles and promote a better employee experience." That is description of team's output. Could be considered responsibilities: to help produce those solutions. It's not invented, it's from posting. So we can use that as responsibilities. Thus Responsibilities section bullet list can be derived from that paragraph. Now Requirements: Could be the "Minimum Qualifications" and maybe "Desired Skills And Experience"? But we have separate Qualifications and Skills sections. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide what goes where. We have Qualifications (minimum qualifications) and Skills (desired skills). Requirements could be something like "Must be authorized to work in the United States on a full-time basis." That's a requirement. Also maybe "Bachelor’s Degree in Mechanical Engineering or equivalent technical degree required" is qualification. But we can put that under Qualifications. Requirements could be things like "Ability to apply mechanical engineering principles..." etc. But those are also qualifications. Better to follow typical pattern: Requirements = mandatory qualifications; Qualifications = maybe preferred? But we have both Minimum Qualifications and Desired Skills And Experience. So we can map: - Requirements: Minimum Qualifications (Bachelor's degree, 5+ years experience, ability to apply mechanical engineering principles, tolerance analysis, authorized to work in US). Also maybe "Experience creating and defining performance requirements on engineering drawings". That's also minimum. - Qualifications: Could be the same? Hmm. Alternatively, we could treat Requirements as the list of mandatory items (minimum qualifications) and Qualifications as the desired skills/experience (desired). But the heading list includes both Qualifications and Skills. So maybe Qualifications = minimum qualifications, Skills = desired skills/experience. And Requirements could be something else like "Ability to manage and prioritize multiple ongoing projects", "Enjoy working with your hands..." etc. Those are from "Who You Are" list (attributes). Those could be considered Requirements (personal attributes). So we can assign: - Requirements: The "Who You Are" list (problem-solving, verbal abilities, envision product, builds connections, responsibility, inquisitiveness, pursues answers, manage projects, enjoy hands-on prototyping, love exploring ideas, passion for creating). Those are personal attributes required. - Qualifications: Minimum Qualifications (degree, experience, performance requirements, mechanical engineering principles, tolerance analysis, work authorization). - Skills: Desired Skills And Experience (Creo/Windchill, 7+ years experience, FEA, furniture industry experience, problem-solving techniques). - Benefits: The "Helping You Thrive By:" bullet points (competitive wages and benefits, continuous learning opportunities, culture of inclusion, empowering impact). Those are benefits. - Pay: The salary range info. - Schedule: Not mentioned; we should not create Schedule section if not present. - About the role: Intro paragraphs describing role and team. Thus we will have sections: About the role, Responsibilities (maybe we can skip if we think responsibilities covered elsewhere? But we have a Responsibilities heading; we need to decide if we have content. Could we put responsibilities as the core duties: "create, develop, and implement new products" etc. That is present. We'll include Responsibilities. Thus final HTML:
About the role
... (intro paragraphs)
Responsibilities
- Collaborate with product developers in the Storage Solutions team to create, develop, and implement new products.
- Contribute to the design of thoughtfully designed workplace storage solutions that support flexibility, mobility, and efficient use of space.
- Help integrate storage solutions into various work environments, offering secure personal storage, shared team storage, and architectural elements that enhance functionality and aesthetics.
- Apply a human‑centered approach to develop storage products that promote productive, clutter‑free spaces and a better employee experience.
Requirements
- Superior problem‑solving skills
- Strong verbal abilities as well as analytical skills
- Ability to envision how the product and manufacturing processes can be developed together and how the product will function in the market
- Builds strong connections by seeking input and fostering open dialogue across departments/functions
- Demonstrates a strong sense of responsibility and ownership for outcomes, driving initiatives to successful completion
- A high level of inquisitiveness over a number of areas; an avid curiosity about how things work
- Tirelessly pursues answers with the belief that a solution always exists—sometimes it just requires exploring new perspectives and looking in unexpected places
- Ability to manage and prioritize multiple ongoing projects
- Enjoy working with your hands and using various methods of prototyping
- A love for exploring new ideas, places, and things outside as well as in work
- A genuine and real passion for creating
Qualifications
- Bachelor’s Degree in Mechanical Engineering or equivalent technical degree required
- Minimum 5+ years’ work experience in product development within an engineering discipline
- Experience creating and defining performance requirements on engineering drawings
- Ability to apply mechanical engineering principles and knowledge of material science, manufacturing processes, and tools in product engineering
- Strong understanding of tolerance analysis
- Qualified applicants must be authorized to work in the United States on a full‑time basis. Steelcase will not provide support for or sponsor work authorization and/or visas for this role.
Skills
- Proficiency in Creo and/or Windchill
- 7+ years’ work experience in product development within an engineering discipline
- Experience performing and understanding FEA
- Prior experience in furniture industry or working with related materials
- Ability to use various methods and techniques in solving technical problems
Benefits
- Competitive wages and benefits that support your life both in and out of work
- Continuous learning opportunities to help you grow and upskill
- A culture of inclusion where employees feel seen, heard and valued — lived out every day
- Empowerment to make a meaningful impact on people and the planet through your work and Steelcase’s ongoing commitment
Pay
The starting annual base salary range for this position is $99,000 – $115,000. Please note that the salary information is a general guideline only. Steelcase considers factors such as (but not limited to) scope and responsibilities of the position, candidate's work experience, education/training, key skills, internal peer equity, as well as market and business considerations when extending an offer.
We should not include Schedule section. We must ensure we don't include any boilerplate like EEO, accommodation email, hashtags, etc. Check that we didn't repeat job title as heading. Good. Check that we didn't include any filler like "commensurate with experience". Not present. Check that we preserved all substantive information: Did we miss any? Let's review original text for any other substantive info not captured. Original includes: - "Do you love to develop new products? Do you enjoy taking ideas to reality? Do you love to tackle tough problems? We are hiring a Senior Product Engineer to work in our Storage Solutions team with other product developers to create, develop, and implement new products." That's covered in About the role maybe