Principal - Software Engineer

We need to output HTML fragment with sections: About the role? The posting includes a summary and responsibilities etc. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job description. First, "Job Description Summary" paragraph: "The Commercial Engine Services (CES) Business Intelligence (BI) team is building the next generation of analytics and AI-powered applications for supply chain and operations. We are looking for a Principal Software Engineer to design and build full-stack applications to turn operational data into AI-driven decision tools that predict, recommend, and act to drive business outcomes. This is a hands-on, senior individual-contributor role: you'll shape our AI application strategy, build front-end and back-end services, embed AI features into production products, and create new products to solve our hardest problems. You'll partner with our BI developers and platform architect, and lead our junior software engineers to deliver high-quality solutions our business stakeholders can count on." That could be "About the role". So we can have

About the role

then

with that paragraph. Next "Job Description Roles and Responsibilities:" then bullet list (though not bullet but colon separated). It includes multiple responsibilities: Application Development & Delivery, AI-Powered Features, Technical Standards & Code Quality, Technical Leadership & Mentorship. Each has subpoints. We need to output a

• for any list of duties/requirements/benefits. So we need to list each responsibility as
• . Possibly we can include subpoints as nested
  but not required. We'll just list each bullet as
  • with the text. We need to preserve all substantive info. So we need to include each subpoint within the li maybe as sentences. We'll extract: Application Development & Delivery: - Design, build, and maintain full-stack applications and services across the full software lifecycle: requirements, implementation, testing, documentation, and production support - Build responsive front ends and back-end services deployed to the cloud - Optimize application performance so applications and monitor applications for errors, latency, and usage; own alerting, incident response, and root-cause analysis AI-Powered Features: - Embed AI into applications with natural-language queries, predictive insights, recommendations, and conversational interfaces - Ground AI features in knowledge graphs and ontologies that model the domain and enable semantic search and reasoning over operational data - Build and expose reusable AI capabilities via MCP servers that applications and agents can call - Integrate machine-learning models and LLM APIs into production applications to enhance insights and decision-making - Build agentic workflows that trigger actions and update records, with human approval and audit logging - Partner with junior engineers to move models from experiment to reliable, production-grade features Technical Standards & Code Quality: - Set and enforce application coding standards, design patterns, and engineering best practices across the team - Serve as senior reviewer for application code correctness, performance, security, and maintainability - Establish CI/CD, automated testing, and version-control workflows for application development - Build reusable components, templates, and utilities that accelerate development across the team Technical Leadership & Mentorship: - Mentor and coach junior software engineers and BI developers - Translate ambiguous business problems into project plans and application work - Partner with BI leadership on the application roadmap and with stakeholders on requirements and priorities - Lead application projects of moderate to high complexity, guiding others and influencing technical direction Now Required Qualifications: Bachelor's degree in Computer Science, Software Engineering, or a related technical field from an accredited university or college; Minimum of 8 years of hands-on experience building and shipping full-stack applications to production. Desired Characteristics: Master's degree in a related field from an accredited university or college; Technical Expertise list: Full-Stack Development, AI Integration, MCP & Tool Interfaces, Knowledge Graphs & Ontologies, Cloud & Data Platforms, Engineering Fundamentals; Domain & Problem-Solving; Collaboration & Communication; Personal Attributes. We need sections: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. Typically "Required Qualifications" could go under Requirements or Qualifications. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). So we need to map. We have Required Qualifications (Bachelor's + 8 years). Desired Characteristics includes Master's degree, technical expertise, domain, collaboration, personal attributes. We could put "Requirements" for required qualifications (Bachelor's + 8 years). "Qualifications" for desired characteristics (Master's, etc). "Skills" for technical expertise list (Full-Stack Development, AI Integration, etc). Or we could combine. But we must not create sections with filler. So we need actual content. Let's propose:

    About the role

    ...summary...

    Responsibilities

    • ... each responsibility as li ...

    Requirements

    • Bachelor's degree in Computer Science, Software Engineering, or a related technical field from an accredited university or college
    • Minimum of 8 years of hands-on experience building and shipping full-stack applications to production

    Qualifications

    • Master's degree in a related field from an accredited university or college (desired)
    • Technical Expertise: Full-Stack Development, AI Integration, MCP & Tool Interfaces, Knowledge Graphs & Ontologies, Cloud & Data Platforms, Engineering Fundamentals
    • Domain & Problem-Solving: Breaks ambiguous business problems into clear, shippable increments and validates assumptions with users; debugs across the stack; weighs trade-offs; experience in supply chain, manufacturing, maintenance, or similar operational domains is a strong plus
    • Collaboration & Communication: Strong communication skills; effective collaborator; leads by influence
    • Personal Attributes: Player-coach; Quality-focused; Ownership
    But we also have a separate Skills section maybe for technical expertise. However we already included technical expertise inside Qualifications. Could also create Skills section for those technical expertise items. But we need to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine technical expertise into Qualifications. Now Benefits: The posting mentions: "GE Aerospace offers comprehensive benefits and programs to support your health and, along with programs like HealthAhead, your physical, emotional, financial and social wellbeing. Healthcare benefits include medical, dental, vision, and prescription drug coverage; access to a Health Coach from GE Aerospace; and the Employee Assistance Program, which provides 24/7 confidential assessment, counseling and referral services. Retirement benefits include the GE Aerospace Retirement Savings Plan, a 401(k) savings plan with company matching contributions and company retirement contributions, as well as access to Fidelity resources and planning consultants. Other benefits include tuition assistance, adoption assistance, paid parental leave, disability insurance, life insurance, and paid time-off for vacation or illness." We need to include Benefits section with that content. Also note: "Relocation Assistance Provided: No" and "This is a remote position". Those could be under Benefits or maybe Schedule? Actually remote is about work location, not schedule. Could be under Benefits? Might be better to include as a short paragraph under Benefits or maybe under a separate section like "Work Arrangement". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could put remote info under Benefits or maybe Schedule? Schedule is about work hours; remote is location. Could put under Benefits as "Work Arrangement: Remote position; no relocation assistance." Or we could put under Schedule? Not ideal. Probably include in Benefits as additional note. Pay: The posting includes: "The base pay range for this position is $152,000-202,000. The specific pay offered may be influenced by a variety of factors, including the candidate’s experience, education, and skill set. This position is also eligible for an annual discretionary bonus based on a percentage of your base salary/ commission based on the plan." Also "This posting is expected to close on October 2nd, 2026." That's not pay but could be included in Pay? Probably not. Could be a separate note but we don't have a heading for posting date. Could include in Pay section as a note? Might be better to include in a short paragraph under Pay: base pay range, bonus eligibility, and note about closing date? The closing date is not pay; but we could include it in a separate short paragraph maybe under About the role? But we should not invent sections. Could add a

    after Pay section about posting expected to close date. However instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." So we can fold minor metadata like posting close date into a short

    . Where? Could be after Pay section as a

    (not under a heading). That is allowed: we can have paragraphs outside headings? The instruction says use

    for section headings,

    • for any list,

      for prose. It doesn't forbid having

      outside sections. So we can include a

      for the closing date after the sections. Similarly, "This role will require in-person attendance for New Hire Orientation on Day 1." That's minor metadata; could be a

      somewhere. Also "Additional Information GE Aerospace offers a great work environment, professional development, challenging careers, and competitive compensation." That's fluff; could be dropped? It's somewhat boilerplate but maybe keep as prose? It's not specific benefit; could be omitted as boilerplate? It's somewhat generic; but it's not EEO etc. Might keep as a short paragraph under Benefits? Might be considered boilerplate. Safer to drop. EEO etc we must remove. Now Benefits section: we need to list benefits as

      • items. Let's extract benefits: - Healthcare benefits: medical, dental, vision, prescription drug coverage; access to a Health Coach from GE Aerospace; Employee Assistance Program (24/7 confidential assessment, counseling and referral services). - Retirement benefits: GE Aerospace Retirement Savings Plan, a 401(k) savings plan with company matching contributions and company retirement contributions; access to Fidelity resources and planning consultants. - Other benefits: tuition assistance, adoption assistance, paid parental leave, disability insurance, life insurance, paid time-off for vacation or illness. Also mention programs like HealthAhead supporting physical, emotional, financial, social wellbeing. We'll put these as list items. Now Pay section: base pay range, discretionary bonus. We'll put as

        maybe? But instruction: Use

        for prose. For Pay we could have

        Pay

        then

        with the pay details. Similarly Schedule: The posting does not mention schedule (hours, shift). No schedule info. So we should NOT create a Schedule section. Now we need to ensure we don't include filler like "commensurate with experience", "not specified", etc. We have specific pay range, so okay. Now we need to output only HTML fragment, no markdown fences. Let's construct:

        About the role

        The Commercial Engine Services (CES) Business Intelligence (BI) team is building the next generation of analytics and AI-powered applications for supply chain and operations. We are looking for a Principal Software Engineer to design and build full-stack applications to turn operational data into AI-driven decision tools that predict, recommend, and act to drive business outcomes. This is a hands-on, senior individual-contributor role: you'll shape our AI application strategy, build front-end and back-end services, embed AI features into production products, and create new products to solve our hardest problems.