System Safety Engineer Stf - E4

We need to produce HTML fragment with sections: About the role? The description includes responsibilities etc. We need to parse the job posting. First, we need to identify sections: The posting includes: - Standard Job Description: description of responsibilities (review product systems, etc). That's the role description. - Basic Qualifications: list. - Desired Skills: list. - Pay Information: salary range. - Benefits: list. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have responsibilities: the first paragraph describing duties. Could be under "Responsibilities". Also "About the role" could be a brief summary. But we must not repeat job title as heading. We can include "About the role" with a short paragraph summarizing the role (maybe the first sentence). But we need to preserve all substantive info; we can't invent filler. We can put the description under "Responsibilities" and maybe not have "About the role". However we need to decide: The instruction: "Prefer a few substantive sections over many thin ones." So we could combine role description and responsibilities into one section "Responsibilities". Or we could have "About the role" with a brief summary and then "Responsibilities" with bullet list. But we have only prose description, not bullet list. We could convert sentences into

• items? The rule: Use
  • for any list of duties/requirements/benefits. The duties are currently in prose sentences separated by periods. Could we treat each sentence as a list item? It says "any list of duties/requirements/benefits". If the posting does not explicitly have a list (bullets), we should not invent list formatting; we should keep as

    . So we keep responsibilities as

    . Thus we may have sections: Responsibilities (p), Basic Qualifications (maybe under Requirements or Qualifications), Desired Skills (Skills), Pay, Benefits. We need to decide headings: "Requirements" vs "Qualifications". The posting has "Basic Qualifications" and "Desired Skills". So we could have a section "Qualifications" containing Basic Qualifications (maybe as

    • ) and another section "Skills" containing Desired Skills (as
      • ). Or we could combine Basic Qualifications under "Requirements". But we have both Basic and Desired; we could have "Requirements" for Basic Qualifications and "Skills" for Desired Skills. That seems appropriate. Thus sections: - Responsibilities (h3) with paragraph(s) describing duties. - Requirements (h3) with ul list of basic qualifications. - Skills (h3) with ul list of desired skills. - Pay (h3) with paragraph about salary range. - Benefits (h3) with ul list of benefits. We should not include Schedule because not mentioned. We need to preserve all substantive information: The responsibilities paragraph includes multiple sentences. We'll keep them as a single

        maybe with line breaks? Could keep as one paragraph. Basic Qualifications list: "Bachelors degree in Aerospace Engineering, Systems Engineering, Computer Science, Electrical Engineering, Mechanical Engineering, Software Engineering or related engineering degree.Excellent written and verbal communication skills, including experience with communicating cross-functionallyExperience with and knowledge of System Safety analyses, standards, and toolsExperience leading projects and teams" Note there is missing punctuation; we need to split into items. The original text seems to have no delimiters; we need to infer separate items. Probably each sentence separated by a period? Actually there are periods missing after some. Let's parse: "Bachelors degree in Aerospace Engineering, Systems Engineering, Computer Science, Electrical Engineering, Mechanical Engineering, Software Engineering or related engineering degree.Excellent written and verbal communication skills, including experience with communicating cross-functionallyExperience with and knowledge of System Safety analyses, standards, and toolsExperience leading projects and teams" We can split by capital letters after a period? There's a period after "degree." then "Excellent". Then after "cross-functionallyExperience" missing space. Then after "toolsExperience". Hard. We could keep as a single paragraph preserving the exact text? But we need to use

        • for any list of duties/requirements/benefits. This is a list of qualifications; we should split into items logically. We can infer items: - Bachelor's degree in Aerospace Engineering, Systems Engineering, Computer Science, Electrical Engineering, Mechanical Engineering, Software Engineering or related engineering degree. - Excellent written and verbal communication skills, including experience with communicating cross-functionally. - Experience with and knowledge of System Safety analyses, standards, and tools. - Experience leading projects and teams. We'll add appropriate punctuation. Desired Skills list: many items separated by line breaks? The text: "Desired Skills Military or civilian flight experienceKnowledge of MIL-STD-882, MIL-HDBK-516, ARP-4761, and/or ARP-4754Knowledge of FAA and military regulations and processesPrevious experience writing technical reports on complex subject matterExperience with military or government programsKnowledge of statistical analysis methodsModel-based system engineering (MBSE) training or experienceExperience working with international customers and suppliersFull life-cycle experience with system safety analyses, standards, and toolsAbility to operate autonomously with minimal direction from managementDemonstrated ability to lead projects and teams in the resolution of highly complex issues, including direct interaction with senior leadership within company and customer organizations and a demonstrated ability to deal with complex and challenging customer and supplier relationshipsExperience with software safety requirements across the full development lifecycle from hazard identification through development to system/software qualification test" Again missing delimiters. We need to split into sensible items. Likely each bullet begins with a capital letter after a lowercase? Hard. We can attempt to split by recognizing keywords: "Military or civilian flight experience", "Knowledge of MIL-STD-882, MIL-HDBK-516, ARP-4761, and/or ARP-4754", "Knowledge of FAA and military regulations and processes", "Previous experience writing technical reports on complex subject matter", "Experience with military or government programs", "Knowledge of statistical analysis methods", "Model-based system engineering (MBSE) training or experience", "Experience working with international customers and suppliers", "Full life-cycle experience with system safety analyses, standards, and tools", "Ability to operate autonomously with minimal direction from management", "Demonstrated ability to lead projects and teams in the resolution of highly complex issues, including direct interaction with senior leadership within company and customer organizations and a demonstrated ability to deal with complex and challenging customer and supplier relationships", "Experience with software safety requirements across the full development lifecycle from hazard identification through development to system/software qualification test". We'll create
          • for each. Pay: "Full-Time Salary Range: $104900.00 - $194700.00 At Lockheed Martin, we know mission success starts with taking care of our people. Our Total Rewards program is designed to attract top talent, support your well-being, and help you grow—both professionally and personally. The salary range for this position is as listed on the requisition. Please note that the salary information listed is a general guideline only. Lockheed Martin considers factors such as (but not limited to) scope and responsibilities of the position, candidate's work experience, education/ training, key skills as well as market(work location) and business considerations when extending an offer." We need to keep all substantive info. We'll put that in a

            under Pay heading. Benefits: list: "Benefits offered: Medical, Dental, Vision, Flexible work arrangements and schedules (e.g., 4x10), 401(k) match, Paid time off, Holidays, Parental Leave, EAP, Flexible Spending Accounts, Education Assistance, Life Insurance, Short-Term Disability, and Long-Term Disability. Annual short-term and/or long-term incentive compensation programs may be offered depending on the position. Payments under these annual programs are not guaranteed and can vary from year to year and are tied to a range of performance metrics.For (Washington state applicants only) Non-represented full-time employees: accrue at least 10 hours per month of Paid Time Off (PTO) to be used for incidental absences and other reasons; receive at least 90 hours for holidays. Represented full time employees accrue 6.67 hours of Vacation per month; accrue up to 52 hours of sick leave annually; receive at least 96 hours for holidays. PTO, Vacation, sick leave, and holiday hours are prorated based on start date during the calendar year." We need to keep all that. We'll put benefits as

            • items? The benefits list includes many items separated by commas. We could split each benefit as separate
            • . Also the extra sentences about incentive compensation and Washington state specifics could be separate
            • or

              . Since it's a list of benefits, we can treat each distinct benefit as

            • . The extra sentences are not benefits per se but details; we could keep them as

              after the list. However instruction: Use

              • for any list of duties/requirements/benefits. So we should put the benefits list as
                • . The additional sentences about incentive compensation and Washington state specifics are not a list but prose; we can keep as

                  after the list. Thus final HTML:

                  Responsibilities

                  Standard Job Description Reviews product systems, associated support equipment and facilities, functional specifications and operations, and establishes safety requirements for assigned systems. Independently analyzes and recommends safety criteria in system design, equipment and procedures to control or eliminate hazards. Develops safety documents as required to support customer and test/operational range requirements. Performs audits of operational areas and reports effectiveness of system safety program. Participates in accident investigations involving damage to products or related facilities and assists in identification of causes and corrective actions. Evaluates the interrelationship of system safety requirements and other aspects of concept design and development requirements to ensure the most cost effective program.

                  Requirements

                  • Bachelor's degree in Aerospace Engineering, Systems Engineering, Computer Science, Electrical Engineering, Mechanical Engineering, Software Engineering or related engineering degree.
                  • Excellent written and verbal communication skills, including experience with communicating cross-functionally.
                  • Experience with and knowledge of System Safety analyses, standards, and tools.
                  • Experience leading projects and teams.

                  Skills

                  • Military or civilian flight experience
                  • Knowledge of MIL-STD-882, MIL-HDBK-516, ARP-4761, and/or ARP-4754
                  • Knowledge of FAA and military regulations and processes
                  • Previous experience writing technical reports on complex subject matter
                  • Experience with military or government programs
                  • Knowledge of statistical analysis methods
                  • Model-based system engineering (MBSE) training or experience
                  • Experience working with international customers and suppliers
                  • Full life-cycle experience with system safety analyses, standards, and tools
                  • Ability to operate autonomously with minimal direction from management
                  • Demonstrated ability to lead projects and teams in the resolution of highly complex issues, including direct interaction with senior leadership within company and customer organizations and a demonstrated ability to deal with complex and challenging customer and supplier relationships
                  • Experience with software safety requirements across the full development lifecycle from hazard identification through development to system/software qualification test

                  Pay

                  Full-Time Salary Range: $104900.00 - $194700.00 At Lockheed Martin, we know mission success starts with taking care of our people. Our Total Rewards program is designed to