Senior Software Engineer/Architect

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Must not include placeholder text like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes pay range: Minimum Rate $105,000 Annually Maximum Rate $290,000 Annually. Also mentions benefits: "Our employees enjoy generous benefits, including a robust education assistance program, unparalleled retirement contributions, and a healthy work/life balance." Also later: "APL provides eligible staff with a comprehensive benefits package including retirement plans, paid time off, medical, dental, vision, life insurance, short-term disability, long-term disability, flexible spending accounts, education assistance, and training and development." So we have benefits content. Schedule? Not mentioned explicitly. No schedule info. So we should not include Schedule section. Pay section we have specific numbers, so include Pay. We need sections: About the role (maybe from description intro), Responsibilities (the bullet list after "As a member of our team, you will…"), Qualifications (the "You’ll meet our minimum requirements if you have…" and "You’ll go above and beyond our minimum requirements if you have…" maybe combine into Requirements/Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which headings to use. Likely we have About the role (intro paragraph), Responsibilities (list of duties), Requirements (maybe the minimum requirements), Qualifications (maybe the "go above and beyond" or skills?), Skills (maybe list of specific technical skills), Benefits, Pay. We must not create sections with filler. We need to ensure we preserve all substantive info. Let's parse the posting: Description paragraph: "Are you passionate about building solutions for our greatest national security challenges? Are you searching for engaging work with an employer that prioritizes impact, innovation, and professional development? Do you value working in a results-oriented and collaborative environment? If so, we're looking for someone like you to join our team at APL. The Threat Analytic Systems (QAI) Group wants talented staff who can work as part of a team to design, implement, test, document, and maintain software applications that provide highly impactful capabilities. You will combine software engineering best practices with the latest software research to build rapid prototypes and then turn them into mature product solutions." That's about the role. Then "As a member of our team, you will…" followed by a list: - Lead teams to design, implement, test, and deploy software applications in a dynamic, fast-paced environment. - Interact with users to understand their operations and gather requirements. - Lead design reviews to gather feedback on system design, integration, and testing. - Document and present work on current research and development activities. - Seek new and innovative ways to improve task efficiency and document software approaches. - Engage staff across organizational boundaries to increase collaboration. That's responsibilities. Then "Qualifications You’ll meet our minimum requirements if you have…" list: - B.S. in Computer Science or Computer Engineering or a related technical field - Seven (7) or more years of software development experience with a high level language, including significant experience with Java. - Experience with Python. - Demonstrated experience as a technical lead of a software project. - Experience with web development using modern JavaScript frameworks (Vue.js, ReactJS, Angular etc.), web services, software architecture design and development, and software test and deployment. - Comfort working with loosely defined or high-level requirements (as opposed to a fully defined project schedule). - Ability to creatively contribute towards developing new requirements by identifying customer needs and applying knowledge of available methods, tools, and concepts to those needs. This experience should include setting requirements, defining architecture, scoping work for and tasking team members. - Experience with non-relational databases (MongoDB, CouchDB, HBase etc.) in the areas of query optimization, database design, and scalability. - Experience working successfully within a team environment. - Excellent written and verbal communication skills. - Are able to obtain a TS/SCI level security clearance. If selected, you will be subject to a government security clearance investigation and must meet the requirements for access to classified information. Eligibility requirements include U.S. citizenship. Then "You’ll go above and beyond our minimum requirements if you have…" list: - A PhD or Masters degree in Computer Science or Computer Engineering. - Experience in Agile software development. - Experience with information retrieval techniques. - Experience with relational databases (Microsoft SQL Server, MySQL, Postgres, SQL etc.). - Experience with DoW and/or IC customers. Then "About Us Why Work at APL?" paragraph: description of APL culture, benefits, location, link. Then EEO boilerplate etc. Must remove. Then "The referenced pay range is based on JHU APL’s good faith belief at the time of posting. Actual compensation may vary based on factors such as geographic location, work experience, market conditions, education/training and skill level with consideration for internal parity. For salaried employees scheduled to work less than 40 hours per week, annual salary will be prorated based on the number of hours worked. APL may offer bonuses or other forms of compensation per internal policy and/or contractual designation. Additional compensation may be provided in the form of a sign-on bonus, relocation benefits, locality allowance or discretionary payments for exceptional performance. APL provides eligible staff with a comprehensive benefits package including retirement plans, paid time off, medical, dental, vision, life insurance, short-term disability, long-term disability, flexible spending accounts, education assistance, and training and development. Applications are accepted on a rolling basis. Minimum Rate $105,000 Annually Maximum Rate $290,000 Annually" We need to extract benefits: robust education assistance program, unparalleled retirement contributions, healthy work/life balance; also comprehensive benefits package list. We need to output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly Skills could be derived from the qualifications lists (technical skills). But we must not create thin sections. We could combine Requirements and Qualifications? But the instruction says use those headings if we have content. We have both minimum requirements and preferred qualifications. Could treat "Requirements" as minimum requirements, "Qualifications" as preferred qualifications (or "Skills"). However we also have a separate "Skills" heading. Might be redundant. Let's think: The posting includes qualifications (both minimum and preferred). Could map: - About the role: intro paragraph. - Responsibilities: the list after "As a member of our team, you will…" - Requirements: the minimum requirements list (B.S., 7+ years, etc.) - Qualifications: the "go above and beyond" list (PhD/Masters, Agile, etc.) - Skills: maybe we could extract specific technical skills like Java, Python, JavaScript frameworks, web services, etc. But those are already in requirements. Could create Skills section summarizing technical skills: Java, Python, JavaScript frameworks (Vue.js, ReactJS, Angular), web services, software architecture, software test/deployment, non-relational databases (MongoDB, CouchDB, HBase), relational databases (SQL Server, MySQL, Postgres), information retrieval techniques, Agile, etc. However that might be duplicative. But we need to preserve all substantive info; we can keep them in Requirements and Qualifications sections; we may not need a separate Skills section if it would be thin. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit Skills if it would be thin. However we have a lot of technical skill details; we could put them under Requirements (minimum) and Qualifications (preferred). That seems fine. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We must not include Schedule. Now we need to format: Use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive info, not invent or summarize away detail. So we must keep the exact wording? Not necessarily exact but preserve info. We can rephrase slightly but must not lose detail. Probably safe to copy the sentences as given. We need to remove boilerplate: EEO, accommodation, etc. Also remove duplicated lines, application instructions (like "Applications are accepted on a rolling basis.") That's not boilerplate but maybe considered application instruction? It says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So "Applications are accepted on a rolling basis." is an application instruction, should be removed. Also "Learn more about our career opportunities at https://www.jhuapl.edu/careers." maybe considered navigation? Might be considered a link; but it's part of About Us. Might be okay to keep? It's not boilerplate but it's a link. The instruction says remove application instructions; that line is about applications, so remove. Also "All qualified applicants will receive consideration for employment without regard to ..." is EEO boilerplate, remove. Also "APL is committed to providing reasonable accommodation..." remove. Also "The referenced pay range is based on JHU APL’s good faith belief..." maybe keep as part of Pay section? It's explanatory about pay range; we can keep as prose in Pay section. We need to include Pay section with the pay range details and maybe the explanatory text. The Pay section heading

  Pay

  . Then we can have a

  containing the pay range description and the actual numbers. We need Benefits section:

  Benefits

  . Then we can have a
  • list of benefits: robust education assistance program, unparalleled retirement contributions, healthy work/life balance, retirement plans, paid time off, medical, dental, vision, life insurance, short-term disability, long-term disability, flexible spending accounts, education assistance, training and development. Also maybe sign-on bonus, relocation benefits, locality allowance, discretionary payments for exceptional performance? Those are mentioned under compensation, not benefits exactly but could be considered benefits. However they are under compensation. Might be better to keep them under Pay? The instruction says Benefits section only if posting actually states them. The posting does state benefits: "Our employees enjoy generous benefits, including a robust education assistance program, unparalleled retirement contributions, and a healthy work/life balance." and later "APL provides eligible staff with a comprehensive benefits package including retirement plans, paid time off, medical, dental, vision, life insurance, short-term disability, long-term disability, flexible spending accounts, education assistance, and training and development." Also mentions "APL may offer bonuses or other forms of compensation per internal policy and/or contractual designation. Additional compensation may be provided in the form of a sign-on bonus, relocation benefits, locality allowance or discretionary payments for exceptional performance." That's compensation, not benefits. But we could include them under Benefits or Pay. Safer to include them under Benefits as they are benefits-like. However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states benefits explicitly, so we can include Benefits section. We'll include the list of benefits as described. We must not include placeholder text like "commensurate with experience". Not present. Now we need to ensure we don't repeat the job title as a heading. Not needed. Now produce HTML fragment. Let's craft:

    About the role

    Are you passionate about building solutions for our greatest national security challenges? Are you searching for engaging work with an employer that prioritizes impact, innovation, and professional development? Do you value