Principal Software Engineer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: description of role, duties list, requirements (education, experience, certifications), qualifications (maybe same as requirements), skills (list of technologies), benefits? Not mentioned. Pay? Not mentioned. Schedule? It mentions hybrid: 2 days in office, up to 3 days remote. That's schedule info. So we can include Schedule section. Benefits not mentioned, so omit. Pay omitted. About the role? Could be the introductory paragraph about organization? The "About The Organization" section is about the organization, not role. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content. We have: - About the role: maybe we can include a brief description: "Fullsight, LLC is seeking a Principal Software Engineer to work in Warrendale, PA. This is a hybrid position that requires 2 days in the office and allows for the ability to work from home with the appropriate telecommuting systems up to 3 days/week." That's about the role and schedule. But schedule we might separate. Could put schedule in its own section. About the role could be a short paragraph describing the position. - Responsibilities: list of duties (1)-(14). Use

• . - Requirements: education and experience baseline: Bachelor's degree, 10 years experience, AWS cert, etc. Could be separate. - Qualifications: maybe the detailed experience list (2 years team lead, 8 years experience with specific techs). Could be separate. - Skills: list of technologies (microservice, noSQL, containerization, etc). Could be separate. But we must avoid duplication. The posting lumps many items under "Must have..." and "Experience must include at least...". We can split into Requirements (education, years, cert) and Qualifications (specific experience). Skills could be the tech list. We need to preserve all substantive information; not invent or summarize away detail. So we need to include all details. Let's extract: Intro: "SAE Industry Technologies Consortia (ITC), Performance Review Institute (PRI) and SAE International (SAE), deliver shared solutions to industry's common challenges. Join us and create a higher standard for a better world. Fullsight, LLC is seeking a Principal Software Engineer to work in Warrendale, PA. This is a hybrid position that requires 2 days in the office and allows for the ability to work from home with the appropriate telecommuting systems up to 3 days/week." That's about organization and role. Then duties list enumerated (1)-(14). We'll put under Responsibilities. Then "Must have a Bachelor's Degree in Computer Science, Computer Engineering or related major, and 10 years of experience in a hands-on software engineering role using java, including spring. Must have previously earned at least one AWS certification." That's requirements. Then "Experience must include at least 2 years of experience in a Team Lead role and at least 8 years of experience with (1) microservice or distributed computing services; (2) noSQL including MongoDB or DynamoDB; (3) modern development tools and methodologies including Containerization, Unit Testing, Gitlab, and CI/CD; (4) design and implementation of a messaging-based architecture with RabbitMQ or similar tools; (5) automated performance test implementation; (6) design and implementation of software security and authorization tools including OAuth, Spring Security, or OpenID; (7) implementing and using elastic search and the ELK stack; (8) performing code reviews for quality, security, performance, maintainability, and compliance with architectural and coding standards; (9) object-oriented programming and analysis; (10) relational database concepts and SQL; (11) design and implementation multiple programming languages including Java, JavaScript/TypeScript, PL/SQL, and Bash; and (12) Agile development environments." That could be Qualifications or Skills. Since it's a list of specific experience/skills, we could treat as Qualifications (experience) and maybe Skills separate? But we have to avoid thin sections. Could combine Qualifications and Skills into one section? But headings are prescribed; we can choose to include only those with real content. We could put all that under Qualifications (since it's experience/skills). Or we could split: Qualifications for the team lead + years, Skills for the tech list. However the tech list is also experience. Might be better to have Qualifications include the team lead + years, and Skills include the enumerated tech list. That would give two sections with substantive content. But we must not invent headings like "Skills" if we don't have specific skill list separate from qualifications. We do have a list of specific technologies/methodologies; that can be considered Skills. Thus: - About the role: intro paragraph (maybe also include hybrid schedule? but schedule separate). We'll put schedule in its own section. - Responsibilities: duties list. - Requirements: education, 10 years, AWS cert. - Qualifications: team lead 2 years, 8 years experience (maybe we can keep the 8 years experience as part of qualifications, but then skills list separate). Actually the 8 years experience is with specific technologies; that could be qualifications. Then skills could be the list of specific technologies/methodologies. But that duplicates. Better: Qualifications: team lead 2 years; 8 years experience with the listed areas (we can keep the list as part of qualifications). Then Skills could be omitted if we consider the list as qualifications. However we need to avoid thin sections; we could omit Skills if we think qualifications cover it. But the instruction says prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Qualifications, Schedule. That's five sections. That seems reasonable. Schedule: hybrid: 2 days in office, up to 3 days remote. We must not include Benefits, Pay. Now we need to ensure we don't repeat job title as heading. Not include Job ID. We must remove boilerplate: EEO clause, navigation, etc. Also remove "Apply at https://www.fullsight.org/careers." (application instructions). Also remove "About The Organization" section? That's about organization, not role. Could we include it under About the role? The instruction says About the role heading for section headings (e.g. About the role, Responsibilities...). The "About The Organization" is not exactly about the role, but we could incorporate that into About the role? Might be considered boilerplate? It's descriptive of the organization, but it's substantive info about the organization. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that info. Where to put? Could be part of About the role (maybe a paragraph about the organization). Or we could create a separate section like "About the Organization" but not in allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should fit organization info under About the role perhaps. Thus About the role section will contain: description of organization consortium, mission, Fullsight seeking Principal Software Engineer, location, hybrid schedule (maybe schedule separate). But we already have schedule separate; we could still mention hybrid in About the role but then schedule section repeats. Better to keep schedule separate and not duplicate. So About the role: description of consortium and mission, plus that Fullsight is seeking a Principal Software Engineer. Could also mention location Warrendale, PA. That's fine. Schedule section: hybrid position requiring 2 days in office, up to 3 days remote. Now Responsibilities: list of 14 duties. Requirements: Bachelor's degree, 10 years experience hands-on software engineering using java including spring, at least one AWS certification. Qualifications: at least 2 years experience in a Team Lead role and at least 8 years experience with (list). We'll include the list as part of Qualifications. We must not create Skills section. Now ensure we preserve all specifics: the list of 8 years experience includes 12 items enumerated (1)-(12). We'll keep them as
  • . Now check for any other specifics: The duties list includes items like "serving as a technical expert, lead, and architect on large and complex projects;" etc. We'll keep them. Now ensure we remove boilerplate: EEO clause, navigation, legal, etc. Also remove "Apply at https://www.fullsight.org/careers." Also remove "EEO CLAUSE" etc. Also remove "About The Organization" heading (we integrated). Also remove "Fullsight is a shared services group..." paragraph (that's about organization). We'll incorporate that into About the role maybe. Let's craft About the role paragraph: "SAE Industry Technologies Consortia (ITC), Performance Review Institute (PRI) and SAE International (SAE) deliver shared solutions to industry's common challenges. Join us and create a higher standard for a better world. Fullsight, LLC is seeking a Principal Software Engineer to work in Warrendale, PA. Fullsight is a shared services group working across three affiliate organizations, SAE ITC, SAE International, and Performance Review Institute (PRI), uniformly delivering HR, IT, Legal, Customer Success, Finance, and Procurement services, which enables us to distribute resources across all parts of our businesses." That captures organization description and role. Now Schedule section: "This is a hybrid position that requires 2 days in the office and allows for the ability to work from home with the appropriate telecommuting systems up to 3 days/week." Now Responsibilities: list. Now Requirements: "Must have a Bachelor's Degree in Computer Science, Computer Engineering or related major, and 10 years of experience in a hands-on software engineering role using java, including spring. Must have previously earned at least one AWS certification." Now Qualifications: "Experience must include at least 2 years of experience in a Team Lead role and at least 8 years of experience with:" then list. Now ensure we don't repeat "Must have" etc. Now output HTML fragment: use

    for each section heading, then content in

    or

    • . We must not include or . Just the fragment. Let's construct:

      About the role

      SAE Industry Technologies Consortia (ITC), Performance Review Institute (PRI) and SAE International (SAE) deliver shared solutions to industry's common challenges. Join us and create a higher standard for a better world. Fullsight, LLC is seeking a Principal Software Engineer to work in Warrendale, PA. Fullsight is a shared services group working across three affiliate organizations, SAE ITC, SAE International, and Performance Review Institute (PRI), uniformly delivering HR, IT, Legal, Customer Success, Finance, and Procurement services, which enables us to distribute resources across all parts of our businesses.

      Responsibilities

      • serving as a technical expert, lead, and architect on large and complex projects;
      • designing, developing, testing, implementing, and maintaining complex web-based application systems, such as user interface, e-commerce applications, and integrations;
      • troubleshooting and solving complicated software issues;
      • researching technical problems and suggesting improvements for web applications;
      • analyzing and integrating new web products and technologies with existing web applications to improve the application functionality;
      • utilizing a thorough understanding of assigned business applications and system infrastructure;
      • leading the team as a high-level technical expert in design, development, coding, testing, and debugging new software or significant enhancements to existing software;
      • defining system architecture, design and documentation;
      • defining and adhering to SAE International development standards, including naming conventions, source code control processes,