Requirements Management Engineer
ALTEN Technology USA · Twinsburg, OH · 1 mo ago
On-siteEngineering$120k–$130k/yrFull-time
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 if posting has real specific content.
We need to parse the posting.
Content:
- Intro about ALTEN Technology USA: description of company. Could be "About the role"? Actually "About the role" is typical heading for role description. The intro is about company and role context. Could be placed under "About the role" or maybe not needed. But we need to include sections only if there is real content.
We have sections:
- Responsibilities: includes bullet points: Requirements Capture & Management (with sub-bullets), Verification & Validation Support, Tools & Processes, Additional Responsibilities.
- Requirements: Education and Experience (Bachelor's degree, min 2 years experience). Also maybe "Requirements" heading.
- Skills: Required Skills & Competencies (list). Also Preferred Qualifications (could be under Skills or Qualifications). The instruction: Use headings for Skills, Qualifications, Benefits, Pay, Schedule. So we can have "Skills" for required skills, "Qualifications" for preferred qualifications? Or "Qualifications" for education/experience? Actually they said headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
Thus:
- About the role: company description and role overview.
- Responsibilities: bullet list of duties.
- Requirements: education and experience (mandatory).
- Qualifications: preferred qualifications? Or maybe "Qualifications" includes both required and preferred? But we have separate Skills heading for skills/competencies. So Qualifications could be preferred qualifications (hands-on experience with tools, knowledge of aircraft electrical power generation, MBSE, etc). We'll put that.
- Skills: required skills & competencies (solid understanding, experience using tools, familiarity with standards, analytical, communication, collaboration).
- Benefits: not explicitly mentioned besides "comprehensive benefits" in intro. The posting says: "supported by mentorship, career growth opportunities, and comprehensive benefits." That's a mention of benefits but not detailed. Should we include Benefits section? The rule: include a section ONLY when the posting has real, specific content for it — 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. Here we have "comprehensive benefits" but not specific. Is that considered specific enough? It's vague. Likely not enough to create a Benefits section. So we omit Benefits.
- Pay: Salary Range: $120,000- $130,000. That's specific. So we include Pay section.
- Schedule: not mentioned. So omit.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay.
We need to format as HTML fragment: use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the posting.
Content:
- Intro about ALTEN Technology USA: description of company. Could be "About the role"? Actually "About the role" is typical heading for role description. The intro is about company and role context. Could be placed under "About the role" or maybe not needed. But we need to include sections only if there is real content.
We have sections:
- Responsibilities: includes bullet points: Requirements Capture & Management (with sub-bullets), Verification & Validation Support, Tools & Processes, Additional Responsibilities.
- Requirements: Education and Experience (Bachelor's degree, min 2 years experience). Also maybe "Requirements" heading.
- Skills: Required Skills & Competencies (list). Also Preferred Qualifications (could be under Skills or Qualifications). The instruction: Use headings for Skills, Qualifications, Benefits, Pay, Schedule. So we can have "Skills" for required skills, "Qualifications" for preferred qualifications? Or "Qualifications" for education/experience? Actually they said headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
Thus:
- About the role: company description and role overview.
- Responsibilities: bullet list of duties.
- Requirements: education and experience (mandatory).
- Qualifications: preferred qualifications? Or maybe "Qualifications" includes both required and preferred? But we have separate Skills heading for skills/competencies. So Qualifications could be preferred qualifications (hands-on experience with tools, knowledge of aircraft electrical power generation, MBSE, etc). We'll put that.
- Skills: required skills & competencies (solid understanding, experience using tools, familiarity with standards, analytical, communication, collaboration).
- Benefits: not explicitly mentioned besides "comprehensive benefits" in intro. The posting says: "supported by mentorship, career growth opportunities, and comprehensive benefits." That's a mention of benefits but not detailed. Should we include Benefits section? The rule: include a section ONLY when the posting has real, specific content for it — 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. Here we have "comprehensive benefits" but not specific. Is that considered specific enough? It's vague. Likely not enough to create a Benefits section. So we omit Benefits.
- Pay: Salary Range: $120,000- $130,000. That's specific. So we include Pay section.
- Schedule: not mentioned. So omit.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay.
We need to format as HTML fragment: use for each section heading. Use - for any list of duties/requirements/benefits, and
for prose.
We must not repeat job title as heading. The job title is "Requirements Management Engineer". Not to be used as heading.
We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: EEO, drug screening, compliance notice, scam warning, etc. Also remove duplicated lines.
We need to keep the substantive content: company description, responsibilities bullet points, education/experience, required skills, preferred qualifications, salary range.
We need to ensure we don't lose any details.
Let's extract content.
Company description paragraph:
"We’re ALTEN Technology USA, an engineering company helping clients bring groundbreaking ideas to life—from advancing space exploration and life-saving medical devices to building autonomous electric vehicles. With 3,000+ experts across North America, we partner with leading companies in aerospace, medical devices, robotics, automotive, commercial vehicles, EVs, rail, and more.As part of the global ALTEN Group—57,000+ engineers in 30 countries—we deliver across the entire product development cycle, from consulting to full project outsourcing.When you join ALTEN Technology USA, you’ll collaborate on some of the world’s toughest engineering challenges, supported by mentorship, career growth opportunities, and comprehensive benefits. We take pride in fostering a culture where employees feel valued, supported, and inspired to grow."
That's the About the role content.
Now responsibilities:
We have headings within responsibilities: "Requirements Capture & Management", "Verification & Validation Support", "Tools & Processes", "Additional Responsibilities". Each with bullet points.
We need to produce a
- list for duties. Should we preserve subheadings? Could embed them as part of list items text. Probably we can include them as part of the list item text.
Let's list each duty:
Under Requirements Capture & Management:
- Collaborate with multidisciplinary engineering teams to define, document, and organize system, software, and hardware requirements
- Maintain full traceability between requirements, design artifacts, implementation, and verification results
- Ensure all requirements comply with aerospace standards and certification guidelines (e.g., DO-178C, DO-254, AS9100, ARP4754A)
- Manage updates to requirements, assess impacts of changes, and maintain thorough documentation for configuration control and audit readiness
Under Verification & Validation Support:
- Assist with verification and validation activities to confirm that all requirements are measurable, testable, and satisfied, in alignment with V-Model practices
- Facilitate clear communication between engineering disciplines to ensure designs meet both project and certification objectives
- Support continuous alignment of requirements with system-level goals and certification expectations
Under Tools & Processes:
- Utilize requirements management software (e.g., IBM DOORS, Windchill RV&S) to maintain traceability, streamline workflows, and track compliance
- Participate in process improvement initiatives to enhance requirements management and documentation practices
Under Additional Responsibilities:
- Occasional domestic and international travel (About the role
- for any list of duties/requirements/benefits, and
for prose. We must not repeat job title as heading. The job title is "Requirements Management Engineer". Not to be used as heading. We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: EEO, drug screening, compliance notice, scam warning, etc. Also remove duplicated lines. We need to keep the substantive content: company description, responsibilities bullet points, education/experience, required skills, preferred qualifications, salary range. We need to ensure we don't lose any details. Let's extract content. Company description paragraph: "We’re ALTEN Technology USA, an engineering company helping clients bring groundbreaking ideas to life—from advancing space exploration and life-saving medical devices to building autonomous electric vehicles. With 3,000+ experts across North America, we partner with leading companies in aerospace, medical devices, robotics, automotive, commercial vehicles, EVs, rail, and more.As part of the global ALTEN Group—57,000+ engineers in 30 countries—we deliver across the entire product development cycle, from consulting to full project outsourcing.When you join ALTEN Technology USA, you’ll collaborate on some of the world’s toughest engineering challenges, supported by mentorship, career growth opportunities, and comprehensive benefits. We take pride in fostering a culture where employees feel valued, supported, and inspired to grow." That's the About the role content. Now responsibilities: We have headings within responsibilities: "Requirements Capture & Management", "Verification & Validation Support", "Tools & Processes", "Additional Responsibilities". Each with bullet points. We need to produce a
- list for duties. Should we preserve subheadings? Could embed them as part of list items text. Probably we can include them as part of the list item text. Let's list each duty: Under Requirements Capture & Management: - Collaborate with multidisciplinary engineering teams to define, document, and organize system, software, and hardware requirements - Maintain full traceability between requirements, design artifacts, implementation, and verification results - Ensure all requirements comply with aerospace standards and certification guidelines (e.g., DO-178C, DO-254, AS9100, ARP4754A) - Manage updates to requirements, assess impacts of changes, and maintain thorough documentation for configuration control and audit readiness Under Verification & Validation Support: - Assist with verification and validation activities to confirm that all requirements are measurable, testable, and satisfied, in alignment with V-Model practices - Facilitate clear communication between engineering disciplines to ensure designs meet both project and certification objectives - Support continuous alignment of requirements with system-level goals and certification expectations Under Tools & Processes: - Utilize requirements management software (e.g., IBM DOORS, Windchill RV&S) to maintain traceability, streamline workflows, and track compliance - Participate in process improvement initiatives to enhance requirements management and documentation practices Under Additional Responsibilities: - Occasional domestic and international travel (About the role
... company description ...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Pay
Salary Range: $120,000- $130,000. The actual salary offered is dependent on various factors including, but not limited to, location, the candidate’s combination of job-related knowledge, qualifications, skills, education, training, and experience.
We need to ensure we don't include any boilerplate like EEO, drug screening, compliance notice, scam warning, etc. Check if any duplicated lines: we have not duplicated. Now ensure we preserve all substantive information: Did we miss any? The intro also mentions "mentorship, career growth opportunities, and comprehensive benefits." We included that in About the role paragraph. Good. Also note: "We take pride in fostering a culture where employees feel valued, supported, and inspired to grow." included. Now check if any other details: "This position requires access to export-controlled information. Applicants must be U.S. Persons, which includes U.S. citizens, U.S. nationals, lawful permanent residents (Green Card holders)." That is a requirement (citizenship). Should we include that under Requirements? It's a substantive requirement. Yes we should include it. It's not boilerplate; it's a specific eligibility requirement. So we need to add a bullet under Requirements: "Must be a U.S. Person (U.S. citizen, U.S. national, or lawful permanent resident) due to access to export-controlled information." We should incorporate that. Also note: "All qualified applicants will receive consideration for employment and will not be discriminated against..." that's EEO boilerplate, remove. "Please beware of job seeker scams..." remove. "Compliance Notice: Alten USA is a federal contractor..." remove. "Drug Screening Requirement..." remove. Thus we need to add citizenship requirement. Now also note: "Minimum of 2 years of experience in aerospace requirements management or related systems engineering functions, with exposure to certification-focused development environments" we have. Now also note: "Bachelor’s degree in Aerospace, Electrical, Mechanical, Computer Engineering, or a related technical discipline" we have. Now also note: "This position requires access to export-controlled information. Applicants must be U.S. Persons, which includes U.S. citizens, U.S. nationals, lawful permanent residents (Green Card holders)." Add. Now also note: "Occasional domestic and international travel (<10%) may be required to support projects and audits" we have under Additional Responsibilities. Now also note: "Follow established safety procedures and actively contribute to the company’s health, safety, and environmental programs" we have. Now also note: "Perform other duties as assigned in support of project and organizational goals" we have. Now also note: "Supported by mentorship, career growth opportunities, and comprehensive benefits." Already in About the role. Now also note: "We take pride in fostering a culture where employees feel valued, supported, and inspired to grow." Already. Now also note: "When you join ALTEN Technology USA, you’ll collaborate on some of the world’s toughest engineering challenges" Already. Now also note: "As part of the global ALTEN Group—57,000+ engineers in 30 countries—we deliver across the entire product development cycle, from consulting to full project outsourcing." Already. Now also note: "With 3,000+ experts across North America, we partner with leading companies in aerospace, medical devices, robotics, automotive, commercial vehicles, EVs, rail, and more." Already. Now also note: "We’re ALTEN Technology USA, an engineering company helping clients bring groundbreaking ideas to life—from advancing space exploration and life-saving medical devices to building autonomous electric vehicles." Already. Now also note: "This position