Senior Staff Product Engineer

We need to output HTML fragment with sections only if content exists. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. The job description includes Role Summary/Purpose (that's about the role). Then Essential Responsibilities. Then Qualifications/Requirements (includes qualifications and desired characteristics). Also there is "Relocation assistance may be provided..." and "Wabtec will only employ..." etc. Also salary range info. Benefits info: "More information on offered benefits, which include health, welfare, and retirement, are available at mywabtecbenefits.com. Other benefit offerings for this role may include annual bonus, if eligible." So we have Benefits content. Pay: salary range $104800-149300. Schedule: not mentioned. So we should NOT include Schedule section. Skills: we could extract from Desired Characteristics etc. But we have Qualifications/Requirements section that includes required qualifications and desired characteristics. Could split into Requirements (mandatory) and Skills (desired). However instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect possibly both Requirements and Qualifications separate? But they gave list includes both Requirements and Qualifications as possible headings. We need to decide what to include based on content. The posting has "Qualifications/Requirements:" then bullet list of qualifications (education, experience). Then "Desired Characteristics:" list. So we could map "Requirements" to the mandatory qualifications, and "Skills" to desired characteristics. Or we could combine into Qualifications section. But they said "Prefer a few substantive sections over many thin ones." So maybe combine Qualifications and Requirements into one section? However they gave both as possible headings; we can choose to include only those with real content. We have content for both mandatory qualifications and desired characteristics. Could make two sections: Requirements (mandatory) and Skills (desired). That seems reasonable. We also need About the role (role summary/purpose). Responsibilities (essential responsibilities). Benefits (benefits info). Pay (salary range). Possibly also include "Qualifications" if we keep both? But we already have Requirements and Skills. The list includes Qualifications as a possible heading; we could omit if we split. But we need to ensure we don't miss any content. The mandatory qualifications and desired characteristics cover all qualification content. So we can omit Qualifications heading. Check for any other sections: maybe "About the role" includes role summary/purpose. Good. Now we need to format: Use

for each heading. Then content: For prose use

. For lists use

• . Ensure we preserve all substantive information, no boilerplate. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is EEO statement etc. Remove that. Also remove "Relocation assistance may be provided if eligibility requirements are met." That's a benefit? Could be part of Benefits. It's a specific benefit. We'll include in Benefits. Also "Wabtec will only employ those who are legally authorized to work in the U.S. for this opening." That's a requirement (legal authorization). Could be part of Requirements (maybe as a note). It's substantive. We'll include. Also "Any offer of employment is conditioned upon the successful completion of a drug screen (as applicable) and fitness for duty test (as applicable)." That's also a requirement. We need to preserve all substantive info. Now let's extract content. Role Summary/Purpose paragraph: "As the Senior Staff Product Engineer, you will be responsible for leading the design, development, and deployment of Digital Onboard Solutions Engineering (DOSE) Electronic Braking technology. Additionally, the successful candidate will work closely with Product Management, Program Management and railroad customers to develop world class solutions that bring advanced automation and data analytics to the rail industry with high quality and reliability. The Senior Staff Product Engineer will be the technical architect developing long term strategy for the Electronic Braking product line by leveraging industry experience, input from customers and collaboration with Product Management. The Senior Staff Product Engineer will be the focal point for all technical inquiries for the engineering department with respect to Electronic Braking product line. They will interact with both internal and external engineering organizations to steward the braking product line through all product lifecycle phases." We'll put that in

  . Essential Responsibilities: a list of bullet points (though they are sentences separated by periods). We need to convert to

  • . Let's list each responsibility: - Lead future concepts and design enhancements for the Transport Intelligence products using sound engineering principles and adhering to business standards, practices, procedures, and product / program requirements. - Support development of the R&D strategy for the product - Serve as a primary customer contact for the Transport Intelligence product line. - Translate customer needs / requirements, resolve specification issues, handle technical correspondence, provide periodic updates, ensure customer satisfaction, and negotiate / coordinate with cross-functional teams as appropriate. - Provide guidance to the internal engineering teams on design tradeoff considerations during the development lifecycle - Be a Technical Leader for the projects across global cross-functional teams (Product / Program Management, SW COE, Electrical Integration, Train Control, Office Systems, Safety, Validation and Applications Engineering) assuring “cradle to grave” success. - Participate in the development of proposals for projects. - Work with Wabtec’s scientific community and railroad subject matter experts to develop freight automation solutions, evaluate them in field trials and productize the solutions to function in a railroad revenue environment. - Lead and participate in technical and program reviews. - Maintain broad awareness of technical trends to ensure technical quality excellence, timely completion of work, and reviews and responsiveness to customer/program needs. - Work collaboratively with the Global Supply Chain Organization across the various locations to support procurement of parts from an engineering requirements perspective. - Provide technical input to customer facing documentation such as but not limited to product descriptions, operational manuals, installation instructions, troubleshooting guides, and product marketing material. - Interface with the Global Locomotive Operations group to ensure factory-built locomotives are manufactured successfully and delivered to customers in a timely manner. - Provide design input into external teams for locomotive integration of Digital Solutions products. - Manage program execution of engineering team to deliver on time, within budget, and meet contractual obligations - Highlight dependencies to Project Management Organization (PMO) and escalate engineering impeding items We need to ensure each is a separate
  • . Some sentences are short like "Support development of the R&D strategy for the product". Keep as is. Now Qualifications/Requirements (mandatory): - Bachelor’s degree or Associate’s degree in Engineering, Mathematics, Computer Science, or a related technical discipline from an accredited institution, or equivalent technical training and demonstrated relevant experience. - Minimum of 7 years hands-on design, requirements development and implementation experience involving; Engineering Systems, Hardware / Software Engineering, and/or Data Information Systems. - Minimum 1 years experience with Locomotive Electronic Braking Systems - Locomotive control systems experience - Strong analytical and problem-solving skills. - Experience with communication systems - Experience in computer networking - Experience in software deployment and configuration management - Proven ability to work in a cross-functional, global environment. - Willingness and ability to travel domestically and internationally. - Wabtec will only employ those who are legally authorized to work in the U.S. for this opening. - Any offer of employment is conditioned upon the successful completion of a drug screen (as applicable) and fitness for duty test (as applicable). Note: The phrase "Minimum 1 years experience with Locomotive Electronic Braking Systems" maybe missing a word but keep as is. Now Desired Characteristics (skills): - Master’s Degree in Engineering, Mathematics or Computer Science. - Locomotive Systems Design Experience. - Railroad Industry Experience. - Prior system design experience with large-scale wireless communication-based projects. - Experience working in the Agile Development Environment - Self-starter with the ability to lead design efforts with minimum supervision. - Strong oral and written communication skills. - Strong interpersonal and leadership skills. - Knowledge of AAR and CENELEC standards for the rail industry - Desire to be involved in hiring and onboarding process of future team members Now Benefits: - Relocation assistance may be provided if eligibility requirements are met. - More information on offered benefits, which include health, welfare, and retirement, are available at mywabtecbenefits.com. - Other benefit offerings for this role may include annual bonus, if eligible. We could combine into a
    . Pay: - The salary rate for this role is currently $104800-149300 - The actual salary offered to a candidate may be influenced by a variety of factors, such as: training, transferable skills, work experience, education, business needs, market demands and work location. - The base pay range is subject to change and may be modified in the future. We could put as

    or

    . Since it's prose, maybe

    . But we have multiple sentences; could be

    with line breaks? Better to use

    for each sentence? The instruction: use

    for prose. Could combine into one

    with sentences. We'll do one

    containing all. Now we need to output only HTML fragment, no /, no markdown. We'll produce:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Requirements

    • ...
    ...

    Skills

    • ...
    ...

    Benefits

    • ...
    ...

    Pay

    ...

    We must not include Schedule. Check for any duplicated lines: ensure we didn't repeat. Now verify we preserved all substantive info: role summary, responsibilities, qualifications (mandatory), desired characteristics (skills), benefits, pay. Also included legal authorization and drug screen etc in Requirements. Check if any other info like "Our job titles may span more than one career level." That's fluff; maybe not needed. It's generic. Could be omitted as boilerplate? It's not exactly boilerplate but it's not substantive to the role. Might be considered filler. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. That line is not really substantive to the job; it's about job titles. Could be omitted? It's not about the role. I'd say it's not essential; but it's part of the posting. However it's generic and not specific to the role. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not those. It's more about job titles. Might be considered filler but not explicitly prohibited. However they said "Prefer a few substantive sections over many thin ones." Including that line would create a thin section maybe. I'd omit it as it's not substantive to the role. Similarly the paragraph about "What could you accomplish..." and "Who are we?" etc is marketing fluff; could be considered boilerplate? It's not legal/EEO but it's generic marketing. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It doesn't explicitly say to remove marketing fluff. However they said "Preserve ALL substantive information". Is that marketing fluff substantive? It's not about the role specifics; it's about company. Might be considered not substantive to the job description. I'd lean to omit it to keep focused. But risk of removing something they consider substantive. However they said "do NOT invent or summarize away detail". Removing that is summarizing away detail (the company description). Might be considered summarizing away. But they also said "remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate".