812147 Software Engineer $225,000.00
for 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 as heading. Remove boilerplate, navigation, EEO, etc. Preserve all substantive info.
We need to parse the posting.
Key info:
- Labor Category: Software Engineer
- Position Title: Software Developer
- Position Level: Level 2 – Expert
- Salary: Up to $225,000.00 per year
- Core Hours: 9am to 4pm
- Location: Herndon VA
- Description: Position Requires a Top Secret (TS/SCI) Clearance with a Polygraph. In this role, you will contribute directly to innovative projects that support the IC, helping to protect our country from emerging threats. This position offers the chance to grow your expertise alongside talented Software Developers, Data Engineers, and System Engineers while pioneering solutions that make a national impact.
- Responsibilities: list bullet points.
- Details: repeats labor category etc.
- Mandatory Requirements: list of levels and specific experience.
- Optional Requirements: B4CORP Company Information (maybe not needed). Then company info, benefits, compensation details.
We need to produce sections: About the role (description), Responsibilities, Requirements (maybe mandatory), Qualifications (maybe optional?), Skills (maybe list of required tech), Benefits, Pay, Schedule.
We must not create sections with filler like "commensurate with experience". We have actual Pay: Salary up to $225k per year. So we can include Pay section.
Schedule: Core Hours: 9am to 4pm. So we can include Schedule section.
Benefits: we have detailed benefits: Retirement (Vanguard 401k), phantom stock, insurance (medical, dental, vision, disability, life), Employee Referral Bonus, PTO (seven weeks including ten federal holidays), flexible work schedule with comp time.
We need to include Benefits section with those details.
Qualifications: maybe the mandatory requirements (experience levels, years, specific tech). Could be Requirements section. Qualifications could be optional? But we can combine.
We need to avoid duplication. Use - for lists.
We need to preserve all substantive info; not invent.
Let's extract:
About the role: The description paragraph: "Position Requires a Top Secret (TS/SCI) Clearance with a Polygraph. In this role, you will contribute directly to innovative projects that support the IC, helping to protect our country from emerging threats. This position offers the chance to grow your expertise alongside talented Software Developers, Data Engineers, and System Engineers while pioneering solutions that make a national impact."
Also maybe mention Labor Category etc? But those are metadata; we could include in About the role? Probably not needed; but we can include location etc? However location is separate maybe not needed as heading. The instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include location, core hours, etc in a short paragraph maybe under About the role or separate? But we have Schedule and Pay sections for core hours and salary. Location maybe not needed as a section; could be included in About the role paragraph.
We need to preserve all substantive info: location, core hours, salary, clearance requirement, description, responsibilities, mandatory requirements, optional requirements (company info), benefits, compensation details.
We'll create sections:
- About the role: includes clearance requirement, description, location, core hours maybe? But we have separate Schedule and Pay.
Better: About the role: description (including clearance, mission, growth). Then separate sections for Pay, Schedule, Benefits, Responsibilities, Requirements (mandatory), Skills (maybe list of tech), Qualifications (optional? maybe company info). But we need to avoid thin sections.
Let's decide:
Sections:
- About the role (description)
- Responsibilities (list)
- Requirements (mandatory experience and tech)
- Skills (maybe list of specific technologies: Python, Linux, Node.js, SQL/PostgreSQL, API endpoints, Elasticsearch)
- Benefits (list)
- Pay (salary)
- Schedule (core hours)
We could omit Qualifications if we covered requirements.
We must not create sections with filler. Ensure each section has content.
Now extract details:
About the role: "Position Requires a Top Secret (TS/SCI) Clearance with a Polygraph. In this role, you will contribute directly to innovative projects that support the IC, helping to protect our country from emerging threats. This position offers the chance to grow your expertise alongside talented Software Developers, Data Engineers, and System Engineers while pioneering solutions that make a national impact."
Also maybe mention Labor Category etc? Not needed.
Responsibilities list: from "Responsibilities Include, But Are Not Limited To" then bullet points:
- Understand requirements and design and develop software components.
- Research software concepts, develop, and demo proof-of-concepts.
- Collaborate with team members regularly to discuss project status, dependencies, or project blockers so that any issues can be addressed early on
- Test code and write test steps for independent testers
- Participate in code reviews and engage in the project’s agile development process.
- Effectively communicate with fellow developers and occasionally with end-users.
- Develop new features and enhancements to web applications that allow users to enter, search, and retrieve information
- Effectively apply good judgement and leadership within project scope and has experience mentoring two to three more junior developers
- Supply regular reports to stakeholder components
- Accommodate changes in priority as organizational goals change
- Break down requirements into work packages in JIRA
- Assist with tier 3 help desk issues on an as-needed basis
- Manage the development life cycle and deployment schedule and process
- Evaluate and integrate data sources as needed; be able to use various data sources and correlate data to answer specific questions
We need to keep them as list items.
Requirements (mandatory): from "Mandatory Requirements Developmental (0-2 years’ experience) Full Performance (3-5 years’ experience) Senior (6-10 years’ experience) Expert (11-15 years’ experience) SME (16+ years’ experience) At least 3 years of recent experience coding in python, minimum 12 years programming experience overall Experience working in a Linux-based development environment Experience with Node.js Experience with SQL/PostgreSQL databases and writing complex queries Experience creating API endpoints or integrating with other teams’ endpoints to exchange data in a fully authenticated and audited way Experience with Elasticsearch data management"
We need to parse: It lists experience levels but likely the position is Level 2 – Expert, requiring Expert level (11-15 years). But we can just list the requirements as given.
We could format as list:
- Developmental (0-2 years’ experience)
- Full Performance (3-5 years’ experience)
- Senior (6-10 years’ experience)
- Expert (11-15 years’ experience)
- SME (16+ years’ experience)
- At least 3 years of recent experience coding in Python
- Minimum 12 years programming experience overall
- Experience working in a Linux-based development environment
- Experience with Node.js
- Experience with SQL/PostgreSQL databases and writing complex queries
- Experience creating API endpoints or integrating with other teams’ endpoints to exchange data in a fully authenticated and audited way
- Experience with Elasticsearch data management
But the first five are just categories; maybe we should keep them as they are.
Skills: maybe we can extract from requirements: Python, Linux, Node.js, SQL/PostgreSQL, API development, Elasticsearch. Could be a separate Skills section.
But we might combine Requirements and Skills; but instruction: prefer few substantive sections over many thin ones. Could combine Requirements and Skills into one Requirements section that includes both experience and technical skills. However we have separate headings for Requirements and Skills; we could decide to only include Requirements (covering both) and omit Skills to avoid thin section. But we need to include Skills only if posting has real specific content for it. The posting does list specific technologies; we could treat them as skills. But we could also include them under Requirements. Since we have both headings available, we need to decide which to include. The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid creating a Skills section if we can incorporate those details into Requirements. So we will have Requirements section that includes experience levels and technical skills.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule.
Now Benefits: extract details:
- Compensation Outstanding Salaries (but we have Pay separate)
- Retirement: Full Vanguard 401k Plan – Featuring a full scope of investment options – 100% employer matched contribution up to 6% of employee’s salary – Ability to max out 401k savings $57k ($63.5k if over 50)
- Employees receive B4Corp phantom stock each year (2-year vesting period)
- Insurance:
- Medical – United Health Care (UHC) (multiple plan options)
- Dental – United Concordia (UC) Flex Plan
- Vision – Vision Service Plan Insurance Co (VSP) Signature Plans
- Mutual of Omaha short-term disability (60% of salary up to $2,000.00/week)
- Mutual of Omaha long-term disability (60% of salary up to $10,000.00/month)
- Mutual of Omaha life insurance ($200,000.00)
- Employee Referral Bonus: Refer a friend or a coworker and receive $3,000 per year for every year the person works for B4CORP
- Paid Time Off (PTO): Seven weeks of leave per year (including ten federal holidays)
- Flexible work schedule with comp time (with customer approval)
We should include all that.
Pay: Salary: Up to $225,000.00 per year.
Schedule: Core Hours: 9am to 4pm.
Now we need to output HTML fragment only, no markdown.
We'll produce:
About the role
Position requires a Top Secret (TS/SCI) clearance with a polygraph. In this role, you will contribute directly to innovative projects that support the intelligence community, helping to protect the country from emerging threats. This position offers the chance to grow your expertise alongside talented software developers, data engineers, and system engineers while pioneering solutions that make a national impact.
Maybe also mention location? Could add location and core hours? But we have separate sections.
We could add location in About the role: "Located in Herndon, VA." But we already have location info; we could include it there.
But we must not repeat job title. It's fine.
Now Responsibilities:
Responsibilities
- Understand requirements and design and develop software components.
- Research software concepts, develop, and demo proof-of-concepts.
- Collaborate with team members regularly to discuss project status, dependencies, or project blockers so that any issues can be addressed early on.
- Test code and write test steps for independent testers.
- Participate in code reviews and engage in the project’s agile development process.
- Effectively communicate with fellow developers and occasionally with end-users.
- Develop new features and enhancements to web applications that allow users to enter, search, and retrieve information.
- Effectively apply good judgement and leadership within project scope and has experience mentoring two to three more junior developers.
- Supply regular reports to stakeholder components.
- Accommodate changes in priority as organizational goals change.
- Break down requirements into work packages in JIRA.
- Assist with tier 3 help desk issues on an as-needed basis.
- Manage the development life cycle and deployment schedule
or drop it. So we could include location, core hours, etc in a short paragraph maybe under About the role or separate? But we have Schedule and Pay sections for core hours and salary. Location maybe not needed as a section; could be included in About the role paragraph. We need to preserve all substantive info: location, core hours, salary, clearance requirement, description, responsibilities, mandatory requirements, optional requirements (company info), benefits, compensation details. We'll create sections: - About the role: includes clearance requirement, description, location, core hours maybe? But we have separate Schedule and Pay. Better: About the role: description (including clearance, mission, growth). Then separate sections for Pay, Schedule, Benefits, Responsibilities, Requirements (mandatory), Skills (maybe list of tech), Qualifications (optional? maybe company info). But we need to avoid thin sections. Let's decide: Sections: - About the role (description) - Responsibilities (list) - Requirements (mandatory experience and tech) - Skills (maybe list of specific technologies: Python, Linux, Node.js, SQL/PostgreSQL, API endpoints, Elasticsearch) - Benefits (list) - Pay (salary) - Schedule (core hours) We could omit Qualifications if we covered requirements. We must not create sections with filler. Ensure each section has content. Now extract details: About the role: "Position Requires a Top Secret (TS/SCI) Clearance with a Polygraph. In this role, you will contribute directly to innovative projects that support the IC, helping to protect our country from emerging threats. This position offers the chance to grow your expertise alongside talented Software Developers, Data Engineers, and System Engineers while pioneering solutions that make a national impact." Also maybe mention Labor Category etc? Not needed. Responsibilities list: from "Responsibilities Include, But Are Not Limited To" then bullet points: - Understand requirements and design and develop software components. - Research software concepts, develop, and demo proof-of-concepts. - Collaborate with team members regularly to discuss project status, dependencies, or project blockers so that any issues can be addressed early on - Test code and write test steps for independent testers - Participate in code reviews and engage in the project’s agile development process. - Effectively communicate with fellow developers and occasionally with end-users. - Develop new features and enhancements to web applications that allow users to enter, search, and retrieve information - Effectively apply good judgement and leadership within project scope and has experience mentoring two to three more junior developers - Supply regular reports to stakeholder components - Accommodate changes in priority as organizational goals change - Break down requirements into work packages in JIRA - Assist with tier 3 help desk issues on an as-needed basis - Manage the development life cycle and deployment schedule and process - Evaluate and integrate data sources as needed; be able to use various data sources and correlate data to answer specific questions We need to keep them as list items. Requirements (mandatory): from "Mandatory Requirements Developmental (0-2 years’ experience) Full Performance (3-5 years’ experience) Senior (6-10 years’ experience) Expert (11-15 years’ experience) SME (16+ years’ experience) At least 3 years of recent experience coding in python, minimum 12 years programming experience overall Experience working in a Linux-based development environment Experience with Node.js Experience with SQL/PostgreSQL databases and writing complex queries Experience creating API endpoints or integrating with other teams’ endpoints to exchange data in a fully authenticated and audited way Experience with Elasticsearch data management" We need to parse: It lists experience levels but likely the position is Level 2 – Expert, requiring Expert level (11-15 years). But we can just list the requirements as given. We could format as list: - Developmental (0-2 years’ experience) - Full Performance (3-5 years’ experience) - Senior (6-10 years’ experience) - Expert (11-15 years’ experience) - SME (16+ years’ experience) - At least 3 years of recent experience coding in Python - Minimum 12 years programming experience overall - Experience working in a Linux-based development environment - Experience with Node.js - Experience with SQL/PostgreSQL databases and writing complex queries - Experience creating API endpoints or integrating with other teams’ endpoints to exchange data in a fully authenticated and audited way - Experience with Elasticsearch data management But the first five are just categories; maybe we should keep them as they are. Skills: maybe we can extract from requirements: Python, Linux, Node.js, SQL/PostgreSQL, API development, Elasticsearch. Could be a separate Skills section. But we might combine Requirements and Skills; but instruction: prefer few substantive sections over many thin ones. Could combine Requirements and Skills into one Requirements section that includes both experience and technical skills. However we have separate headings for Requirements and Skills; we could decide to only include Requirements (covering both) and omit Skills to avoid thin section. But we need to include Skills only if posting has real specific content for it. The posting does list specific technologies; we could treat them as skills. But we could also include them under Requirements. Since we have both headings available, we need to decide which to include. The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid creating a Skills section if we can incorporate those details into Requirements. So we will have Requirements section that includes experience levels and technical skills. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Now Benefits: extract details: - Compensation Outstanding Salaries (but we have Pay separate) - Retirement: Full Vanguard 401k Plan – Featuring a full scope of investment options – 100% employer matched contribution up to 6% of employee’s salary – Ability to max out 401k savings $57k ($63.5k if over 50) - Employees receive B4Corp phantom stock each year (2-year vesting period) - Insurance: - Medical – United Health Care (UHC) (multiple plan options) - Dental – United Concordia (UC) Flex Plan - Vision – Vision Service Plan Insurance Co (VSP) Signature Plans - Mutual of Omaha short-term disability (60% of salary up to $2,000.00/week) - Mutual of Omaha long-term disability (60% of salary up to $10,000.00/month) - Mutual of Omaha life insurance ($200,000.00) - Employee Referral Bonus: Refer a friend or a coworker and receive $3,000 per year for every year the person works for B4CORP - Paid Time Off (PTO): Seven weeks of leave per year (including ten federal holidays) - Flexible work schedule with comp time (with customer approval) We should include all that. Pay: Salary: Up to $225,000.00 per year. Schedule: Core Hours: 9am to 4pm. Now we need to output HTML fragment only, no markdown. We'll produce:
About the role
Position requires a Top Secret (TS/SCI) clearance with a polygraph. In this role, you will contribute directly to innovative projects that support the intelligence community, helping to protect the country from emerging threats. This position offers the chance to grow your expertise alongside talented software developers, data engineers, and system engineers while pioneering solutions that make a national impact.
Maybe also mention location? Could add location and core hours? But we have separate sections. We could add location in About the role: "Located in Herndon, VA." But we already have location info; we could include it there. But we must not repeat job title. It's fine. Now Responsibilities:Responsibilities
- Understand requirements and design and develop software components.
- Research software concepts, develop, and demo proof-of-concepts.
- Collaborate with team members regularly to discuss project status, dependencies, or project blockers so that any issues can be addressed early on.
- Test code and write test steps for independent testers.
- Participate in code reviews and engage in the project’s agile development process.
- Effectively communicate with fellow developers and occasionally with end-users.
- Develop new features and enhancements to web applications that allow users to enter, search, and retrieve information.
- Effectively apply good judgement and leadership within project scope and has experience mentoring two to three more junior developers.
- Supply regular reports to stakeholder components.
- Accommodate changes in priority as organizational goals change.
- Break down requirements into work packages in JIRA.
- Assist with tier 3 help desk issues on an as-needed basis.
- Manage the development life cycle and deployment schedule