Software Engineer
Rapid Cycle Solutions, LLC. · Chantilly, VA · 4 wk ago
On-siteEngineeringFull-time
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 need to parse the posting.
Given text:
Location: Chantilly, VA
Schedule: Full-Time
Work Location: On-Site
Shift: Day Job
Travel: No
Minimum Clearance Required: TS/SCI with FS Poly
Benefits: Click here Rapid Cycle Solutions LLC (RCS) is an innovative small business providing IT and management consulting services to the U.S. Federal Government and commercial clients. We have unique strengths in complex, cross-organizational solution analysis, design, development, implementation, and change management supporting enterprise requirements. Our team of professionals has deep consulting backgrounds supporting the unique needs of our clients. Our team members have proven experience leading strategic initiatives within the civilian Government agencies. Note: Please ensure you meet the Security Clearance obligations before applying to optimize your consideration for this and other employment opportunities with RCS. RCS is seeking a Software Engineer to conduct strategic research and development and require support in the evaluation, system design, and software engineering support to transition, primarily open source, software prototypes and algorithms to a proprietary partner infrastructure for deployment throughout the organization. This position requires the candidate to meet specific Security Clearance obligations to work onsite in Chantilly, VA. What you will do: Install externally developed web applications on cloud environment infrastructure. Ensure the web applications communicate with external and internal databases, using API keys. Modify the web applications as required and be able to work independently on the project as needed. Provide front end development to host models and connect APIs in order to demo and transition tools in software. Utilize AI/ML models to integrate with front-end development. TRAVEL: Local travel/POV will be on an as needed basis, within the local place of performance. Required Qualifications/Education: Clearance: Active TS/SCI clearance with Full Scope Polygraph U.S. Citizenship required (NO EXCEPTIONS) Experience with full stack web development using JavaScript, PHP, R, Python, NodeJS, and/or MongoDB. Experience working with client-side code such as Angular, Bootstrap, Material, jQuery. Experience with REST APIs and data ETL. Experience with Linux System Administration and associated scripting languages (Bash). Experience with NoSQL and MySQL databases. Experience with web app installation and deployment. Experience with web-based software development. Hands-on experience working within cloud platforms such as AWS, Azure, or similar. Experience and knowledge of AI/ML (Artificial Intelligence/Machine Learning) models. Nice to Have Qualifications: Experience with Cloud-based Relational Database Services (RDS). Experience with JIRA and Confluence. RCS is an equal employment opportunity employer... (boilerplate). Our company uses E-Verify... (boilerplate). All RCS work locations are drug-free workplaces. RCS considers several factors which can influence a final salary including but not limited to; skill set relevancy, work experience, geographic location, security clearance, education, certifications, training, and other business and organizational requirements. At RCS we offer competitive compensation packages, benefits, and learning and development opportunities. Individuals are typically not hired at or near the top of the salary range being that compensation decisions are dependent on individual circumstances. The salary range listed for this position is a reasonable estimate taking into consideration the required qualifications. RCS encourages external referrals and offers a referral bonus after a successful hire. This will be paid 90 days after the new hire's start date. Bonus amounts vary based on the skill level and position of the referred candidate and are provided in the form of a gift certificate.
We need to extract sections:
- About the role: description of company and role? The posting includes description of RCS and what they seek. Could be "About the role" or "About the company". Use heading "About the role". Provide prose summarizing the role: RCS is seeking a Software Engineer to conduct strategic research and development and require support in evaluation, system design, and software engineering support to transition primarily open source software prototypes and algorithms to a proprietary partner infrastructure for deployment throughout the organization. This position requires the candidate to meet specific Security Clearance obligations to work onsite in Chantilly, VA.
- Responsibilities: list of duties under "What you will do:" bullet points.
- Requirements: maybe "Required Qualifications/Education" includes clearance, citizenship, experience list. Could be "Requirements" or "Qualifications". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content.
We have:
- Clearance and citizenship: required.
- Experience list: many specific technologies.
We could put those under "Requirements" (or "Qualifications").
"Nice to Have Qualifications" could go under "Skills" maybe? Or "Qualifications" as nice-to-have.
But we need to avoid filler sections like Pay or Schedule unless actual info given. Schedule: we have "Schedule: Full-Time" and "Shift: Day Job". That's specific. So we can include Schedule section with that info.
Pay: The posting mentions salary range not listed, but says "The salary range listed for this position is a reasonable estimate taking into consideration the required qualifications." No actual numbers. So we should NOT include Pay section because no specific salary/range given. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits: we have "Benefits: Click here" then description of benefits? Actually after "Benefits: Click here" there is a paragraph about RCS. Not specific benefits. There's later mention: "At RCS we offer competitive compensation packages, benefits, and learning and development opportunities." That's vague. No specific benefits listed. So we should not include Benefits section because no specific benefits listed. The "Benefits: Click here" is not actual content. So skip Benefits.
Thus sections: About the role, Responsibilities, Requirements (or Qualifications), Skills (nice-to-have), Schedule.
We need to decide naming: Use "Requirements" for mandatory qualifications, and "Skills" for nice-to-have? Or combine. The instruction says prefer a few substantive sections over many thin ones. Could combine Requirements and Qualifications into one section "Requirements". Nice-to-have could be under "Skills". Or we could have "Qualifications" for both required and nice-to-have, but then we would have thin sections. Better: "Requirements" for required, "Preferred Qualifications" maybe but not in list. Since we have "Nice to Have Qualifications", we could put under "Skills". That seems okay.
Thus:
About the role
...
Responsibilities
- ... ...
Requirements
- Active TS/SCI clearance with Full Scope Polygraph
- U.S. Citizenship required
- Experience with full stack web development using JavaScript, PHP, R, Python, NodeJS, and/or MongoDB ... etc.
Skills
- Experience with Cloud-based Relational Database Services (RDS)
- Experience with JIRA and Confluence
Schedule
Full-Time, On‑Site, Day shift
We need to preserve all substantive information. Also include location? Location is Chantilly, VA. Could be included in About the role or maybe as separate? Not required heading. Could embed in About the role paragraph. Also include travel: "TRAVEL: Local travel/POV will be on an as needed basis, within the local place of performance." That's substantive. Should we include under Responsibilities? Or maybe a separate note. Could add a bullet under Responsibilities: "Local travel/POV as needed within the local place of performance." Also note "Shift: Day Job". Already in schedule. Also note "Work Location: On-Site". Already in schedule. Also note "Minimum Clearance Required: TS/SCI with FS Poly" which is same as required clearance. Also note "Benefits: Click here" - ignore. Also note "Note: Please ensure you meet the Security Clearance obligations before applying..." - that's boilerplate/application instruction; we should remove application instructions. So drop that note. Also note "RCS is an equal employment opportunity employer..." boilerplate - remove. Also note "Our company uses E-Verify..." boilerplate - remove. Also note "All RCS work locations are drug-free workplaces." Could be considered a benefit? Not specific; maybe ignore as boilerplate. Also note about salary factors - vague; ignore. Also note about referral bonus - that's a benefit? Could be considered a benefit but it's vague; maybe include under Benefits? But we decided not to include Benefits because no specific benefits. However referral bonus is a specific benefit: referral bonus after successful hire, paid 90 days, gift certificate. That is somewhat specific. Should we include a Benefits section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state referral bonus details. That is a benefit. So we could include a Benefits section with that detail. Also they mention "competitive compensation packages, benefits, and learning and development opportunities." That's vague. But we have specific referral bonus. So we can include Benefits section with that. Thus add:Benefits
- Referral bonus paid 90 days after new hire's start date, amount varies based on skill level and position, provided as a gift certificate.