Platform Engineer (DevOps / Full-Stack Hybrid) [Up to 2 days/week telework]
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate.
We need to parse the posting.
Key info:
- Type Of Requisition Regular (maybe ignore)
- Clearance Level Must Currently Possess Top Secret SCI + Polygraph
- Clearance Level Must Be Able To Obtain Top Secret SCI + Polygraph
- Public Trust/Other Required None
- Job Family IT Infrastructure and Operations
- Skills (maybe not needed)
- Job Qualifications: Collaboration, GitLab CI/CD, Web Applications
- Certifications None
- Experience 5 + years of related experience (but later says 8+ years required)
- US Citizenship Required Yes
- Job Description: Platform Engineer (DevOps / Full-Stack Hybrid) Up to 2 days/week telework**
- Then paragraphs about meaningful work.
- What You’ll Need To Succeed: Education: Bachelor of Arts/Bachelor of Science; Experience: 8+ years of related experience; US citizenship required; Security clearance level: TOP SECRET//SCI W/ Polygraph
- Responsibilities: list bullet points (Multi-Network Deployment, Deployment Process Engineering, Application Modification, Environment Troubleshooting, Collaboration)
- Required Technical Skills: list bullet points (Hands-on experience deploying and managing containerized applications with Kubernetes; Experience developing or modifying applications built with Java / Spring (Spring Boot); Experience developing or modifying front-end applications built with Vue.js (or strong experience with a comparable framework such as React or Angular); Thorough understanding of Docker and container technology; Experience with CI/CD pipelines and deployments of distributed web applications (e.g., GitLab CI/CD); Linux administration experience; Experience with Git)
- Desired Technical skills: list bullet points (Experience deploying applications across multiple isolated or classified network environments; AWS experience, including cloud-native architecture and deployment; Terraform scripting and VM provisioning; Ansible scripting and development; Python scripting and development; Familiarity with Elasticsearch, NiFi, or MongoDB; Familiarity with domain knowledge surrounding government agency reporting and dissemination policies)
- GDIT IS YOUR PLACE: paragraphs about Growth, Support, Rewards, Community.
- OWN YOUR OPPORTUNITY: paragraph.
- The likely salary range for this position is $153,000 - $207,000. This is not, however, a guarantee...
- Scheduled Weekly Hours 40
- Travel Required None
- Telecommuting Options Hybrid Work Location: USA MD Annapolis Junction Additional Work Locations:
- Total Rewards At GDIT: benefits description.
- Our Identity Verification Process: paragraph.
- About Our Work: paragraph.
- Equal Opportunity Employer etc: boilerplate to remove.
We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We must include only sections with real specific content.
Let's map:
- About the role: could be the introductory paragraphs after job description: "Advance how our customers operate while you advance your career..." etc. That's substantive.
- Responsibilities: we have list.
- Requirements: could include education, experience, citizenship, clearance. Might be separate from Qualifications? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide what goes where.
We have "Job Qualifications: Collaboration, GitLab CI/CD, Web Applications" (maybe that's Qualifications). Also "Required Technical Skills" and "Desired Technical skills" could be Skills.
We have "Education: Bachelor..." etc could be Requirements.
We have "Experience: 8+ years..." also Requirements.
We have "US citizenship required" and "Security clearance level: TOP SECRET//SCI W/ Polygraph" also Requirements.
We have "Job Family IT Infrastructure and Operations" maybe not needed.
We have "Skills" maybe combine required and desired technical skills.
We have "Benefits": from Total Rewards At GDIT paragraph.
We have "Pay": salary range.
We have "Schedule": Scheduled Weekly Hours 40, Telecommuting Options Hybrid Work Location..., Travel Required None.
We must not include sections with filler like "not specified". We have actual data.
Now produce HTML.
We must not include markdown fences. Just raw HTML.
Structure:
About the role
... paragraphs ...
Responsibilities
- ... ...
Requirements
- maybe list items: Education, Experience, US citizenship, Security clearance. Could also include "5+ years of related experience" but we have 8+ required; we should preserve both? The posting says Experience 5 + years of related experience (maybe a generic) and later What You’ll Need To Succeed: Experience: 8+ years of related experience. We should preserve both? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to include both statements. Could combine as separate list items.
Thus Requirements list:
- Education: Bachelor of Arts/Bachelor of Science
- Experience: 5+ years of related experience (also note: 8+ years of related experience required for success)
- US citizenship required
- Security clearance: Must currently possess Top Secret SCI + Polygraph; Must be able to obtain Top Secret SCI + Polygraph (maybe combine)
But we have two clearance statements: Must Currently Possess Top Secret SCI + Polygraph; Clearance Level Must Be Able To Obtain Top Secret SCI + Polygraph. So we need to include both.
We could list as separate items.
- Job Family: IT Infrastructure and Operations (maybe include but not required). It's substantive.
We'll include.
- for any list of duties/requirements/benefits. It doesn't forbid multiple lists under same heading. So we can have
Skills
thenRequired Technical Skills:
- ...
Desired Technical Skills:
- ...
Benefits
... the Total Rewards paragraph ...
Pay
The likely salary range for this position is $153,000 - $207,000. This is not, however, a guarantee of compensation or salary. Rather, salary will be set based on experience, geographic location and possibly contractual requirements and could fall outside of this range.
Schedule
Scheduled Weekly Hours 40; Travel Required None; Telecommuting Options Hybrid Work Location: USA MD Annapolis Junction Additional Work Locations: (maybe none specified). Up to 2 days/week telework** mentioned earlier. Also "Up to 2 days/week telework**" from job description. We need to include that. Thus schedule paragraph could combine: Up to 2 days/week telework; Scheduled Weekly Hours 40; Travel Required None; Telecommuting Options Hybrid Work Location: USA MD Annapolis Junction. We should preserve "Additional Work Locations:" but no specifics; maybe it's empty; we could omit as it's just label with no detail. Might be considered filler? Safer to omit if no location given. Thus schedule paragraph: Up to 2 days/week telework; Scheduled Weekly Hours 40; Travel Required None; Telecommuting Options Hybrid Work Location: USA MD Annapolis Junction. Now ensure we removed boilerplate: EEO, equal opportunity, scam warning, identity verification? Actually identity verification is substantive? It's about process; maybe we could include under About the role? But it's not under allowed headings. Could we include it under About the role? It's about hiring process; maybe not needed. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Identity verification is not exactly those but could be considered legal/process. Might be considered boilerplate? It's about hiring process; but it's not a standard EEO. Might be okay to keep? However, the allowed sections are limited; we could not add a new heading for it. Could we fold into About the role? It's not really about the role. Might be considered extraneous. Safer to omit. Similarly "About Our Work" paragraph about GDIT could be considered boilerplate? It's descriptive of company; maybe could be part of About the role? But we already have About the role paragraphs; we could incorporate that as part of About the role? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to keep that info somewhere. Could we put it under About the role as additional paragraphs? That seems reasonable: About the role can include description of the role and company. So we can merge the "About Our Work" paragraph into About the role. Similarly "GDIT IS YOUR PLACE" paragraphs about Growth, Support, Rewards, Community could be considered Benefits? Actually they talk about benefits and culture; we already have Benefits section for total rewards. Could incorporate those paragraphs into Benefits section as well. But we must not lose info. We'll incorporate them into Benefits paragraph. Thus Benefits paragraph will include the Total Rewards description plus the GDIT IS YOUR PLACE bullet points. Now we need to ensure we don't duplicate. Let's craft About the role paragraph(s): From job description: "Advance how our customers operate while you advance your career. Join GDIT as a Platform Engineer Principal and build an impactful career in IT, collaborating with people who are driven and resourceful like you. MEANINGFUL WORK AND PERSONAL IMPACT As a Platform Engineer Principal, the work you’ll do at GDIT will be impactful to the mission of a mission- critical customer. You will play a crucial role in leading the deployment of a production system across three network environments. This is a hybrid role for a versatile, jack-of-all-trades engineer who is equally comfortable deploying and operating containerized systems via Kubernetes and diving into application code to modify system components. The ideal candidate thrives on ownership, working across the full stack and the full deployment lifecycle to stand up new production environments." Then maybe add "About Our Work" paragraph: "We are GDIT. A global technology and professional services company that delivers technology solutions and mission services to every major agency across the U.S. government, defense and intelligence community. Our 26,000 experts extract the power of technology to create immediate value and deliver solutions at the edge of innovation. We operate across 50+ countries worldwide, offering leading mission-ready capabilities in AI, cloud, cyber and software development." We could also include "Up to 2 days/week telework**" maybe belongs to Schedule but we already have. Now Responsibilities list as given. Requirements list: Education, Experience (5+ years, 8+ years),
Qualifications
The posting says "Job Qualifications: Collaboration, GitLab CI/CD, Web Applications". Also maybe "Collaboration" appears in responsibilities. We'll list those. Thus Qualifications list: - Collaboration - GitLab CI/CD - Web Applications Also maybe "Certifications None" but that's not substantive; we can omit as it's just "None". The instruction: do not emit heading followed by filler/placeholder text like "not specified", "N/A", "varies", "TBD". "None" could be considered placeholder? It's a statement that there are none. Might be considered filler? Safer to omit.Skills
We need to include Required Technical Skills and Desired Technical skills. We could combine into one list with subheadings? But we cannot add extra headings besides the allowed ones. Could embed within- with notes? Probably okay to list all skills as items, marking required vs desired? But we must preserve all substantive info; we could separate into two
- under same heading? The instruction only says use