Prin Member Engineering Stf

We need to output HTML fragment with sections: About the role? Actually we need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to parse the job description. Content: - Intro: "Standard Job Description What We’re Doing Here at Lockheed Martin Rotary and Mission Systems (RMS) ..." This is about the company and role. Could be "About the role" or "About the team". We'll treat as "About the role". - "The Work In your role as a Principal Sensor Systems Architect, you will:" then bullet list of duties. That's responsibilities. - "Who We Are" description of team. Could be part of About the role or separate. Might be "About the team". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put team description under About the role. - "Radar at Lockheed Martin" maybe not needed. - "Who You Are" describes desired candidate traits. Could be Requirements or Qualifications or Skills. We'll map to Requirements (maybe "Who You Are"). - "Why Join Lockheed Martin" describes benefits and perks. Could be Benefits. - "Basic Qualifications" list: degree + years, demonstrated success, expert knowledge, proficiency, security clearance. That's Qualifications. - "Desired Skills": list of desired experience etc. That's Skills. - "Pay Information": salary range. That's Pay. - "Benefits offered:" list of benefits. That's Benefits (but we already have Benefits from Why Join Lockheed Martin; we can combine or keep one Benefits section with all benefits). We need to avoid duplication. We'll combine benefits info into Benefits section. - Also schedule info: "The promotion of Work Life Balance with every Friday off (Flex 4/10 Schedule) or every other Friday off (Flex 9/80) or a 5/8 schedule." That's schedule info. So we need a Schedule section. - Also mention "Pay Information" includes salary range. - Also note "Additional specific benefits are dependent upon the business unit and the collective-bargaining agreement." etc. That's still benefits. - Also mention "For (Washington state applicants only) Represented full time employees accrue..." That's benefits detail but location-specific; we can include in Benefits. We must not include boilerplate like EEO, legal, etc. The text includes some like "At Lockheed Martin, we know mission success starts with taking care of our people." That's not boilerplate; it's part of benefits description. Keep. We must not repeat job title as heading. Not include Job ID. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep specifics like salary numbers, benefits list, schedule options, qualifications details. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not emit a heading followed by filler/placeholder text. So only include sections where we have real content. Thus sections: - About the role (intro + team description + maybe "Radar at Lockheed Martin"? We'll include the introductory paragraphs about what they do, mission, team description.) - Responsibilities (the bullet list under "The Work In your role as a Principal Sensor Systems Architect, you will:") - Qualifications (Basic Qualifications) - Skills (Desired Skills) maybe also include "Who You Are" as Requirements? Actually we have Requirements heading allowed. Could treat "Who You Are" as Requirements. But we also have Qualifications and Skills. The posting has Basic Qualifications and Desired Skills. Also "Who You Are" is more like desired attributes. Could map to Requirements. But we already have Qualifications and Skills; we could treat "Who You Are" as Requirements (soft skills). However we must not create thin sections. Let's see content: "Who You Are If you enjoy a technical challenge that will get you thinking outside the box. If you seek a collaborative environment working with motivated engineers with a diverse range of experiences and backgrounds. If you’re a lifelong learner with a passion for driving technology forward. If you’re an expert in your field looking to apply your skill to advancing sensor architectures to stay ahead of ever-evolving customer needs across a broad array of environments and threat spaces, then this is the place for you." That's more like personal traits, could be considered Requirements or Skills. Since we already have Skills for desired technical experience, we could put this under Requirements (or maybe under Skills as soft skills). But we have a Skills section for desired technical experience; we could add soft skills there as well. However the instruction: Use

  • for any list of duties/requirements/benefits. So if we have a list of requirements, we should use list. The "Who You Are" is a series of sentences, not a list. Could be prose

    . So we could put that under Requirements as prose. Thus we have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to ensure we don't create empty sections. Now extract content for each. About the role: Combine introductory paragraphs: "Standard Job Description What We’re Doing Here at Lockheed Martin Rotary and Mission Systems (RMS) we take on the most demanding challenges in the world. We seek out innovative ideas and creative solutions to seemingly impossible problems facing our customers in the Sensors, Effectors & Mission Systems (SEMS) organization. We collaborate with the best Radar engineers in the business across the Moorestown, NJ and Syracuse, NY sites to invent solutions where they don’t exist yet. If you’re looking for the challenge of a lifetime on a team of the brightest minds in the world, then Rotary Mission Systems and the Sensor Architectures team is the place for you. If you’re looking for life-long learning and a career where the hard work is the fun part, then you’re in the right place. Lockheed Martin. Your Mission is Ours." Then "Who We Are Our team of Radar Systems Engineers and Sensor Architects come from diverse backgrounds and experience levels, all working together to deliver quality designs and cutting-edge capabilities to our customers. We support a broad array of Radar products and customers including the Missile Defense Agency, US Navy, Air Force, US Army, Space Force, and foreign partners including Japan, Canada, Spain, Norway, Australia, UK and more. Radar at Lockheed Martin" We could keep "Radar at Lockheed Martin" as a sentence but it's vague; maybe we keep it. Thus About the role will have two paragraphs. Responsibilities: bullet list from "The Work In your role as a Principal Sensor Systems Architect, you will:" then items: - Provide guidance and leadership for program execution across sensor products. - Shape system architectures to strategically drive future capabilities and incorporate emergent technologies. - Provide significant value to the business by engaging with programs, captures, projects and/or research and development initiatives. - Actively enhance the expertise of others through mentoring, on the job coaching and knowledge continuity. - Remain current, continue, and expand expertise in state-of-the-art technologies, including engagements in external engineering communities. - Successfully collaborate with teams across product lines and organizations to foster cross-pollination of ideas. We'll make

    • . Requirements: "Who You Are" paragraph(s). Could be one

      containing the four sentences. Qualifications: Basic Qualifications list: - Bachelor’s degree in an engineering/technical discipline from an accredited college with 14 years of professional experience, a master’s degree with 12 years of experience, or a PhD with 9 years of experience. - Demonstrated success in leading execution of sensor system projects and teams. - Expert knowledge in one or more of the following areas: system analysis, system architecture, requirements development, trade studies, modeling and simulation, integration and test, data analysis, and AI/ML techniques. - High proficiency in C++, Matlab, or Python. - Qualified candidate must be able to obtain & maintain a secret security clearance. - Obtaining a security clearance requires US citizenship. We'll make

      • . Skills: Desired Skills list: - 14 or more years of experience in radar or sensor systems development across design, modeling and simulation, software and/or hardware implementation, and integration and test phases. - Exceptional record of sustained technical achievement, job performance, and continued technical growth. - Demonstrated technical mentorship at all career levels. - Strong interpersonal and soft skills that allow for coaching and the ability to state clear convictions and influence outcomes. - Demonstrated ability to provide advice/guidance during intense technical efforts and difficult situations that may require re-direction to achieve mission success. We'll make
        • . Benefits: Combine from "Why Join Lockheed Martin" and "Benefits offered:" plus Washington state specifics. Why Join Lockheed Martin paragraph: "At Lockheed Martin we value your unique skills and expertise, and we aim to give back continuously by offering a wide variety of benefits and amenities to help our employees live flexible, healthy, and fulfilling lives at and outside of work. Some of our favorite perks include: The promotion of Work Life Balance with every Friday off (Flex 4/10 Schedule) or every other Friday off (Flex 9/80) or a 5/8 schedule. A competitive 401k match and bonus. Comprehensive Benefits including Medical/Dental/Life Insurance." Then Benefits offered list: "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. Additional specific benefits are dependent upon the business unit and the collective-bargaining agreement.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) 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 output as list items. Could combine all benefits into a
          • . Ensure we keep all specifics. Pay: salary range: "$130000.00 - $256896.00". Also note that it's a guideline etc. We'll include that prose maybe as

            . The instruction: include Pay section only if posting has real specific content. It does. We'll output heading

            Pay

            then

            with the salary range and note. Schedule: we have schedule info from Work Life Balance: "The promotion of Work Life Balance with every Friday off (Flex 4/10 Schedule) or every other Friday off (Flex 9/80) or a 5/8 schedule." That's schedule. We'll put under Schedule heading. We must not duplicate schedule info also in Benefits; but we already have schedule in Benefits list as "Flexible work arrangements and schedules (e.g., 4x10)". However we can keep schedule section separate focusing on schedule options. The Benefits section already includes flexible work arrangements; but we can still have Schedule section with specifics. It's okay as long as not duplicate exactly same content. We'll keep schedule section with the specific options. Now ensure we don't include boilerplate like "At Lockheed Martin, we know mission success starts with taking care of our people." That's part of Benefits description; we keep. We must not include EEO/equal-opportunity/scam-warning boilerplate. Not present. Now produce HTML fragment. Structure:

            About the role

            ...first paragraph...

            ...second paragraph...

            Responsibilities

            • ...
            ...