Software Engineer - $20K Sign On Bonus - 30124
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. First, there is a paragraph about Enlighten (company description). That could be "About the role"? Actually "About the role" is typical heading for description of role. The company description could be under "About the role" or maybe "About the company". But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "About the role" for the description of the role (job description). The initial paragraph about Enlighten could be part of "About the role" or maybe we could omit? The 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 include company description as part of About the role. We need to include Benefits: they list many benefits: 100% paid employee premium for healthcare, vision and dental plans. 10% 401k benefit. Generous PTO + 10 paid holidays. Education/training allowances. Also mention $20K Sign On Bonus. Also mention Anticipated Salary Range: $115,199.00 - $160,000.00. Also mention salary range details. So we need Benefits and Pay sections. Schedule: mention "Must be able to work on customer site in Fort Meade, MD 4-5 days a week. Flexibility is essential to accommodate any changes in the schedule." That's schedule info. So we can include Schedule section. Responsibilities: list essential job responsibilities bullet points. Requirements/Qualifications/Skills: The posting includes Minimum Qualifications (clearance, experience, education, etc.) and Preferred Requirements. We need to decide how to split into sections: Qualifications, Requirements, Skills. The instruction: Use headings for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where. Typically Requirements = minimum qualifications; Qualifications = maybe preferred? Skills = specific technical skills. But we can combine. We must not create sections with filler like "commensurate with experience". We have real content. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. There's none obvious except maybe the line "We have many more additional great benefits/perks that you can find on our website at www.enlighten.com." That's not boilerplate but maybe we can keep as part of Benefits? It's a reference to website; could be kept. We must not include the "#Mid-Senior Level" maybe as part of About the role? It's a tag; we can keep as plain text. We need to output only HTML fragment, no /, no markdown fences. Let's structure:
About the role
Enlighten, honored as a Top Workplace from USA Today, is a leader in big data solution development and deployment, with expertise in cloud-based services, software and systems engineering, cyber capabilities, and data science. Enlighten provides continued innovation and proactivity in meeting our customers’ greatest challenges. ... (the rest of company description) ... Enlighten is a cutting-edge technology company that is dedicated to developing innovative software solutions for our clients. We are currently seeking a talented and experienced Software Engineer to join our team. As a Software Engineer, you will be responsible for designing, developing, and implementing complex software capabilities for computer-based systems. Will work closely with other talented engineers to create software solutions that meet the needs of our clients. In this role, you will have the opportunity to work with modern tools and technologies, and you will be encouraged to stay up-to-date with the latest developments in the field. You will be part of a dynamic and collaborative team that is committed to delivering high-quality software solutions to our clients. If you are a self-motivated, creative, and detail-oriented software engineer who is passionate about developing innovative software solutions, we would love to hear from you. #Mid-Senior Level
But we need to avoid duplication: The job description paragraph repeats some of that. We'll combine. Better: About the role includes company overview and role description. Then Responsibilities: list essential job responsibilities bullet points. Then Requirements: maybe minimum qualifications (clearance, experience, education, etc.) as- .
Then Qualifications: maybe preferred requirements? Or we could treat Qualifications as the list of specific technical skills (experience with Java, REST, microservices, OOP, agile, Linux, config mgmt, etc.) and Skills as the preferred/extra skills (cloud, NoSQL, scripting, data lakes, etc.). But we need to follow instruction: Use headings for Requirements, Qualifications, Skills. We need to decide distribution.
Let's parse the Minimum Qualifications section:
"Clearance Requirement: Must currently have and maintain an active Secret U.S. Government Security Clearance with the ability to obtain and maintain a TS/SCI; U.S. Citizenship required.
5 years experience in Software Engineering, Modern Java Frameworks and Libraries (e.g. Spring, Guava)
Bachelors in related field; 3 years relevant experience with Masters in related field; or High School Diploma or equivalent and 9 years relevant experience.
Experience in designing enterprise APIs
Experience in RESTful web services
Experience in Microservices architecture
Experience in Object Oriented Programming (OOP) paradigms
Experience with the agile software lifecycle
Has a proven ability to learn quickly and works well both independently as well as in a team setting
Experience with the Linux operating system
Experience with configuration management tools (e.g. Git, Nexus, Maven)
Must be willing/able to help open/close the workspace during regular business hours as needed.
Must be able to work on customer site in Fort Meade, MD 4-5 days a week. Flexibility is essential to accommodate any changes in the schedule."
That's a mix of qualifications and schedule. Schedule we already have separate section.
We could put Minimum Qualifications under Requirements (or Qualifications). Let's assign Requirements = Minimum Qualifications (clearance, experience, education, etc.). Qualifications = maybe the list of specific technical skills (like Experience in designing enterprise APIs, RESTful web services, Microservices, OOP, agile, Linux, config mgmt). But those are already in Minimum Qualifications. Actually the Minimum Qualifications includes those technical skills. So we could treat Requirements as the clearance, citizenship, experience, education; Qualifications as the technical competencies; Skills as the preferred/extra (cloud, NoSQL, scripting, data lakes, etc.) plus maybe agentic coding stuff.
But we also have a section "Essential Job Responsibilities" which we will put under Responsibilities.
Then we have "Next-Gen Coding Agents" etc under Minimum Qualifications? Actually those are under Minimum Qualifications? Let's see: After Minimum Qualifications, there is a block:
"Experience with Next-Gen Coding Agents: Proven track record of integrating advanced AI agents, specifically Claude Code or Google's Antigravity / Gemini agentic workflows, into your daily software engineering routine.
Agentic Feature & Test Development: Experience using autonomous agents to handle multi-file feature implementations, complex codebase refactoring, and the automated generation of robust unit/integration tests.
Context & Workflow Management: Ability to guide AI agents through complex, multi-repository application architectures, managing context efficiently and critically auditing agent-generated code for security, performance, and architectural alignment."
These are under Minimum Qualifications? Actually they appear after "Minimum Qualifications" heading? The text shows:
"Minimum Qualifications Clearance Requirement: Must currently have and maintain an active Secret U.S. Government Security Clearance with the ability to obtain and maintain a TS/SCI; U.S. Citizenship required.
5 years experience in Software Engineering, Modern Java Frameworks and Libraries (e.g. Spring, Guava)
Bachelors in related field; 3 years relevant experience with Masters in related field; or High School Diploma or equivalent and 9 years relevant experience.
Experience in designing enterprise APIs
Experience in RESTful web services
Experience in Microservices architecture
Experience in Object Oriented Programming (OOP) paradigms
Experience with the agile software lifecycle
Has a proven ability to learn quickly and works well both independently as well as in a team setting
Experience with the Linux operating system
Experience with configuration management tools (e.g. Git, Nexus, Maven)
Must be willing/able to help open/close the workspace during regular business hours as needed.
Must be able to work on customer site in Fort Meade, MD 4-5 days a week. Flexibility is essential to accommodate any changes in the schedule.
Preferred Requirements A current TS/SCI level clearance is desired. Next-Gen Coding Agents: Proven use of AI tools (Claude Code, Gemini) in daily engineering workflows.
Agentic Feature Delivery: Using autonomous agents for multi-file implementation, refactoring, and automated testing.
Experience in cloud based technologies (AWS, Azure)
Experience in distributed databases, NoSQL databases, full text-search engines (e.g. Elasticsearch, MongoDB, Solr) Scripting experience is a huge plus.
Prior experience or familiarity with Data Lakes or Warehouses is a huge plus.
Understanding of AGILE software development methodologies and use of standard software development tool suites. (e.g., JIRA, Confluence, Github Enterprise, etc.)"
So there is a "Preferred Requirements" section after Minimum Qualifications.
Thus we can map:
- Requirements: Minimum Qualifications (clearance, citizenship, experience, education, etc.) maybe also include the technical basics (APIs, REST, microservices, OOP, agile, Linux, config mgmt). But those are also technical qualifications. However we can keep them under Requirements.
- Qualifications: maybe the "Preferred Requirements" that are still qualifications but preferred? Or we could treat Qualifications as the list of specific technical skills (like Experience in designing enterprise APIs, RESTful web services, Microservices architecture, OOP, agile, Linux, config mgmt). But those are already in Minimum Qualifications. To avoid duplication, we need to split content without repeating.
We could assign:
Requirements: Clearance, citizenship, experience years, education alternatives.
Qualifications: Technical competencies: Experience designing enterprise APIs, RESTful web services, Microservices architecture, OOP, agile software lifecycle, ability to learn quickly, teamwork, Linux OS, configuration management tools (Git, Nexus, Maven), willingness to open/close workspace, work onsite Fort Meade 4-5 days (but schedule separate). Actually schedule we will separate.
Skills: Preferred requirements: TS/SCI clearance desired, Next-Gen Coding Agents (Claude Code, Gemini), Agentic Feature Delivery, cloud technologies (AWS, Azure), distributed databases/NoSQL/full-text search, scripting experience, data lakes/warehouses, understanding of Agile and tool suites (JIRA, Confluence, Github Enterprise).
But note that some of these overlap with earlier (agile, etc). We'll keep as is.
We also have the "Essential Job Responsibilities" bullet list.
We have Benefits and Pay sections.
We have Schedule section: mention Fort Meade 4-5 days a week, flexibility.
We also have Sign On Bonus and Salary Range under Pay.
We also have benefits list.
Now we need to ensure we don't create sections with filler like "commensurate with experience". We have real content.
Now we need to output HTML.
Let's craft each section.
About the role: combine company description and role overview.
We need to avoid repeating job title (Software Engineer) as heading; we can mention it in paragraph.
Let's write:
About the role
Enlighten, honored as a Top Workplace from USA Today, is a leader in big data solution