Software Developer - Multiple Levels (Cleared)
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. We need to extract content.
The posting includes:
- Responsibilities: description and bullet list (Key Responsibilities). So we need a Responsibilities section with Responsibilities
then maybe a
for prose and
- for list.
- Required Qualifications: includes active TS/SCI with Polygraph, US citizenship, travel up to 10%, lift up to 30 lbs, etc. Also education/experience levels for Junior, Mid, Senior with compensation ranges. This seems like qualifications and also compensation. The instructions: Use headings for Qualifications, Skills, Benefits, Pay, Schedule. We need to decide where to put each piece.
We have "Required Qualifications" block: includes clearance, citizenship, travel, lift, education/experience for levels, software dev experience. Also compensation ranges per level.
We have "Desired Qualifications": list of desired skills/experience.
We have "Overview" about company, not needed? Probably not needed as section unless we have About the role. The posting includes "Overview" about Noblis mission. Could be considered "About the role"? Actually "About the role" could be the introductory paragraph: "Noblis is seeking Software Developers...". That is about the role. So we can put that in a section
About the role
with. We have "Why Work at Noblis", "Total Rewards", "Compensation at Noblis", "Posted Salary Range". Those could go under Benefits, Pay, etc. We need to include Pay section only if posting actually states them. It does: compensation ranges for Junior, Mid, Senior, and posted salary range $75,000 - $188,725. So we should include Pay section. Benefits: The posting mentions Total Rewards: health, life, disability, financial, retirement benefits, paid leave, professional development, tuition assistance, work-life programs. Also mention eligibility for full-time/part-time. So we can include Benefits section. Schedule: Not explicitly stated; maybe remote/hybrid status subject to change. Not a specific schedule. So we should not create Schedule section unless there is real content. There's no explicit schedule like "Full-time", but there is mention of full-time/part-time eligibility. Could be considered schedule? The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state benefits, so we can include Benefits. For Schedule, we have no explicit schedule like "Monday-Friday 9-5". There's remote/hybrid status subject to change, but not a schedule. Safer to omit Schedule. Skills: Could be from Desired Qualifications (list of desired skills). So we can have Skills section. Qualifications: Could be Required Qualifications (including clearance, citizenship, travel, lift, education/experience). So we have Qualifications section. Responsibilities: we have. About the role: we have introductory paragraph. We must not repeat job title as heading. Not include Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. Must not include boilerplate like EEO, legal, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to output only HTML fragment. Let's extract substantive content: About the role: "Noblis is seeking Software Developers at all experience levels with an active TS/SCI with a Polygraph to support mission-critical national security initiatives in Reston, Virginia. As a Software Developer on our team, you will collaborate with federal clients to rapidly design, develop, and deliver innovative solutions that address their most pressing mission challenges. You will work alongside a multidisciplinary team of developers, data scientists, subject matter experts, and cyber analysts to design and build new applications, enhance existing systems, and integrate emerging technologies. In this role, you will analyze client challenges, identify opportunities for improvement, and apply modern tools and technologies to develop effective, mission-focused solutions. Your responsibilities will span all phases of the software development lifecycle, including programming, debugging, testing, system integration, and deployment. You will also regularly communicate with teammates, technical leads, and clients to provide project updates, share progress, and ensure alignment with mission objectives." That's a paragraph. Responsibilities: The "Key Responsibilities" bullet list: - Apply state-of-the-art technologies to solve complex technical and mission challenges - Develop cutting-edge solutions that improve system performance, reliability, scalability, and distributed processing capabilities - Design, build, and enhance applications that support evolving client needs - Work in an Agile environment to rapidly iterate, collaborate, and deliver impactful solutions for our clients We could also include the earlier prose as part of responsibilities but we already used that in About the role. Might duplicate. Better to keep About the role as overview, Responsibilities as bullet list. Qualifications (Required): Let's list: - Active Top Secret/SCI (TS/SCI) with Polygraph - U.S. Citizenship is required - Travel up to 10% within US - Lift up to 30 lbs, walk, bend, drive. - Education/experience levels: - Junior level: Bachelor's, Master's, or PhD degree with 0 - 3 years of related experience including exposure or coursework in one or more programming languages; OR Associate's degree with 3 years of related experience; OR High School diploma/GED with 6 years of related experience - Software development experience using one or more programming languages such as Python, Java, or JavaScript, etc - Compensation: $75,000.00 - $117,225.00 - Mid level: Bachelor's degree with 5 years of related experience; OR Master's degree with 3 years of related experience; OR Associate's degree with 8 years of related experience; OR High School diploma/GED with 11 years of related experience - Full-stack software development experience using one or more programming languages such as Python, Java, or JavaScript - Compensation: $90,700.00 - $141,775.00 - Senior level: Bachelor's degree with 8 years of related experience; OR Master's degree with 6 years of related experience; OR Associate's degree with 11 years of related experience; OR High School diploma/GED with 14 years of related experience - Full-stack software development experience using one or more programming languages such as Python, Java, or JavaScript - Compensation: $120,700.00 - $188,725.00 We need to preserve all substantive information; we can keep these as list items under Qualifications. Desired Qualifications (Skills): list: - Hands-on experience with relational and/or NoSQL databases, including schema design, data modeling, and query optimization - Strong understanding of software testing methodologies, including unit testing, integration testing, and automated testing frameworks - Proven experience throughout the full SDLC, from requirements analysis and design through implementation, deployment, and ongoing maintenance - Proficiency with Git-based version control systems, including branching strategies, pull request workflows, and code review practices - Ability to manage and contribute to multiple concurrent projects while maintaining high-quality deliverables and effectively prioritizing competing requirements - Experience with containerization and orchestration technologies, including Docker and Kubernetes - Experience deploying, configuring, and maintaining applications in cloud environments (e.g., AWS, Azure, or GCP) - Knowledge of Python web frameworks such as FastAPI and Flask for developing RESTful APIs, microservices, and scalable backend solutions - Demonstrated ability to work across the full technology stack, with the flexibility and willingness to learn and adopt new technologies as project needs evolve - Experience working in Agile development environments, including sprint planning, daily standups, backlog refinement, and iterative delivery practices - Proficiency in Python 3, including modern language features, type hinting, and package management best practices We can put these under Skills section. Benefits: From Total Rewards: - health, life, disability, financial, and retirement benefits - paid leave - professional development - tuition assistance - work-life programs - award programs acknowledge employees for exceptional performance and superior demonstration of service standards - Full-time and part-time employees working at least 20 hours a week on a regular basis are eligible to participate in our benefit programs. - Other offerings may be provided for employees not within this category. We can include as bullet list. Pay: We have compensation ranges per level and overall posted salary range $75,000 - $188,725. We should include Pay section with that info. Could list the ranges per level and overall. We must not include boilerplate like "Commitment to Non-Discrimination", "EEO is the Law", etc. Remove those. Also remove "Overview" about Noblis (the company overview) maybe not needed; but we already used About the role. The "Overview" about Noblis could be considered boilerplate? It's about the company, not the role. Might be considered not needed. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company overview is not explicitly boilerplate but could be considered not required. However we might keep it as part of About the role? The About the role we already have a paragraph from the beginning. The "Overview" section after responsibilities is about Noblis and subsidiaries. That might be considered extra but not prohibited. However we should avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we could omit the company overview to keep sections thin. Also "Why Work at Noblis" is also promotional; could be considered boilerplate? It's about culture. Might be considered not required. But we already have Benefits section covering some of that. The "Why Work at Noblis" includes passion for excellence, environment, etc. Could be considered fluff. Safer to omit. We must preserve ALL substantive information; does "Why Work at Noblis" count as substantive? It's about culture, maybe considered substantive. But we already have Benefits and maybe we could incorporate some of that into Benefits or About the role? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Why Work at Noblis" is not explicitly listed as boilerplate to remove, but it's promotional. However we need to decide. Given the instruction to prefer few substantive sections, we could keep Benefits and maybe incorporate culture into Benefits? But Benefits already covers health etc. The culture statements might be considered not essential. I'd lean to omit "Why Work at Noblis" to keep sections thin. Similarly "Total Rewards" we already captured benefits. "Compensation at Noblis" paragraph about how compensation determined; we could incorporate into Pay section maybe as a note. But we already have Pay ranges; the paragraph about factors could be considered substantive? It explains how compensation determined. Might be worth including in Pay section as a
. However the instruction: never emit a heading followed by filler/placeholder text. This paragraph is not filler; it's substantive. So we could include in Pay section a
describing compensation determination. But we must not repeat info. We'll include Pay section with: - Posted salary range: USD $75,000.00 - USD $188,725.00 /Yr. - Compensation ranges by level (Junior, Mid, Senior) as listed. - Note: Compensation at Noblis is determined by various factors, including but not limited to, the combination of education, certifications, knowledge, skills, competencies, and experience, internal and external equity, location, clearance level, as well as contract-specific affordability, organizational requirements and applicable employment