Intermediate Platform Support Engineer

We need to output HTML fragment with sections: About the role? The posting includes description paragraphs. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse content. First, there is an introductory paragraph about MITRE mission etc. That could be "About the role" or maybe "About the role" is generic. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. So we can include "About the role" heading with a paragraph summarizing the role description (the first paragraphs). Then "Responsibilities" heading with bullet list of duties from "Roles & Responsibilities". Then "Requirements" maybe for Basic Qualifications? Or "Qualifications" for Preferred? The instruction says we can have sections like Requirements, Qualifications, Skills. We need to decide based on content. We have Basic Qualifications list (bullet-like sentences). Also Preferred Qualifications list. Also there is a section about clearance, on-site requirement, etc. Also Pay: Salary compensation range and midpoint: $103,600 - $129,500 - $155,400. Also Schedule: "This position requires a minimum of 3 days per week on-site in McLean, VA, Bedford, MA, San Diego, CA or Colorado Springs, CO." That's schedule/location. Also Benefits: "Benefits information may be found here." That's not specific benefit details, just a link. The instruction: never create Benefits section unless posting actually states them. It only says "Benefits information may be found here." That's not specific benefits. So we should NOT include Benefits section because no specific benefits listed. Similarly, Pay: we have salary range, so we can include Pay section. Schedule: we have on-site requirement, so we can include Schedule section. We also have "Clearance" info: Must be eligible to obtain and maintain Secret clearance within one year, must be US Citizen. That could go under Requirements or Qualifications. Probably under Requirements (basic qualifications). Also "Active Secret Clearance" in Preferred Qualifications? Actually they list "Active Secret Clearance" under Preferred Qualifications? Let's see: after Preferred Qualifications list, there is "Active Secret Clearance". Actually the text: "Active Secret Clearance This requisition requires the candidate to have a minimum of the following clearance(s): None This requisition requires the hired candidate to have or obtain, within one year from the date of hire, the following clearance(s): Secret". So clearance is a requirement. We need to preserve all substantive information. So we need to include clearance requirement somewhere, maybe under Requirements. We also have "Work Location Type: Onsite". That's schedule. We need to avoid boilerplate: EEO, legal, etc. Remove those. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

About the role

...

Then

Responsibilities

• ...

Then

Requirements

• ...

(including basic qualifications, clearance, citizenship, on-site? Actually on-site is schedule, but we could include in Schedule section.) Then

Qualifications

• ...

(preferred qualifications) Then

Skills

maybe we could extract skills from responsibilities? But we already have skills in qualifications. Might be redundant. The instruction: prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one? But they said we can use those headings. We need to decide. We have basic qualifications (required) and preferred qualifications (preferred). Could put both under Requirements? But they'd be mixed. Better to have Requirements for basic, Qualifications for preferred. Skills: maybe we can extract specific skills like Linux/Windows admin, AWS, Kubernetes, Jira, etc. But those are already in basic qualifications. Could put them under Skills. However we already have them in Requirements. To avoid duplication, maybe we put them under Skills and keep Requirements for education/experience and clearance. But we need to preserve all info; duplication is okay? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited but might be redundant. Better to avoid duplication but still preserve info. Could split: Requirements: education/experience, clearance, citizenship. Skills: technical skills (Linux/Windows, AWS, Kubernetes, ticketing, etc.). Qualifications: preferred qualifications (degree, certifications, experience with monitoring, CI/CD, IaC, etc.). That seems reasonable. Schedule: on-site requirement. Pay: salary range. We must not include Benefits. Now craft content. About the role: combine the introductory paragraphs about MITRE Mission Computing and the role description. Let's write a concise paragraph preserving all substantive info: mention MITRE Mission Computing bridges mission and technology, enables projects, applies new tech to address government SE problems, opportunity for experienced platform engineers, front line support for systems enabling national security work, help users on Kubernetes/cloud platforms, triage issues, author/follow runbooks, escalate, keep platform teams unblocked, guide teams on platform use, operate in high-stakes environment with CMMC compliance, high availability, cyber resilience, provide platforms for engineering teams to deliver innovative solutions and AI-enabled capabilities, energized by helping users get unblocked, solving hard problems at scale, deep technical ownership, want engineering decisions to have lasting impact, operations role supporting internal customers, triaging issues, solving customer problems. We need to preserve all detail; we can't omit specifics like "Kubernetes and cloud platforms", "runbooks", "CMMC compliance", "high availability", "cyber resilience", "AI-enabled capabilities". We'll include them. Now Responsibilities: list bullet points from the responsibilities paragraph. Let's extract: - Be the front line for the systems that enable critical national security work across MITRE’s Federally Funded Research and Development Centers. - Help users and mission teams get work done on our Kubernetes and cloud platforms. - Triage issues. - Author and follow runbooks. - Escalate when needed. - Keep platform teams unblocked. - Be accountable for clear, timely support of the compute environments that power internal tools and the development and production workloads engineering, research, and mission teams depend on. - Guide those teams on how to use the platform and its tools correctly and securely. - Operate in a high-stakes environment defined by novel problems and real constraints, including CMMC compliance, high availability, and cyber resilience. - Provide the platforms that enable engineering teams of varying skill maturities to deliver innovative solutions and AI-enabled capabilities to MITRE’s U.S. government sponsors. - If you are energized by helping MITRE platform users get unblocked, prefer being the first to pick up a hard production problem over sitting in a narrow specialty, and want your work to keep mission teams moving... (that's more motivational, maybe not a responsibility). But we can include as part of responsibilities? It's more about desired traits. Might be better to keep under Requirements/Skills. We'll keep responsibilities as concrete duties. - This an operations role with the primary responsibility being to support our internal customers & interfacing with them directly, triaging issues, solving customer problems, etc. We'll include that. Now Requirements (basic qualifications): - Typically requires a Bachelor’s degree and a minimum of 2 years of related experience; or an advanced degree with relevant experience who can immediately contribute at this job step; or equivalent combination of related education and work experience. - 2+ years supporting production applications and infrastructure in technical support, systems administration, or operations. - Hands-on administrative experience of Linux and Windows: logs, services, permissions, and troubleshooting, including account lockouts, MFA, and group-membership / login issues. - Familiarity with AWS (or similar): instances, networking, IAM, and use of the console and CLI to investigate issues. - Support-level exposure to containers and Kubernetes: pods, deployments, logs, events, and common failure symptoms. - Customer-facing ticket and chat skills: reproduce issues, use runbooks, distinguish application vs. platform problems, escalate clearly, and close work with a usable resolution summary. - Experience with a service desk or work-management tools (e.g., Jira, ServiceNow, GitHub Issues) and meeting response/resolution expectations. - Participation in incident response and on-call rotations (e.g., PagerDuty), including following escalation paths and documenting what happened. - Ability to follow change-management and security procedures in regulated environments (e.g., CMMC, SOC 2). - Clear written and verbal communication with users, developers, and platform engineers. - Comfort working in a small team with broad ownership, applying documentation and vendor guidance without step-by-step supervision. - Experience working in a Kanban workflow: pulling work from a shared board, limiting work in progress, and keeping ticket status current so handoffs stay visible. - Must be eligible to obtain and maintain a Secret U.S Government issued Security Clearance within one year of hire. - Per the U.S. Government’s eligibility requirements, you must be a U.S Citizen to be considered for a security clearance. - This position requires a minimum of 3 days per week on-site in McLean, VA, Bedford, MA, San Diego, CA or Colorado Springs, CO. (Actually this is schedule; we might move to Schedule section.) We'll keep on-site in Schedule. Now Skills: we could list technical skills from basic qualifications: Linux/Windows admin, AWS, Kubernetes, ticketing, Jira/ServiceNow/GitHub, incident response, change management, communication, Kanban. But many overlap with Requirements. To avoid duplication, maybe we put under Skills the specific technical proficiencies: Linux/Windows administration, AWS, containers/Kubernetes, ticketing/chat, service desk tools, incident response, change-management/security procedures, communication, Kanban workflow. That's still overlapping but okay. Alternatively, we could combine Requirements and Skills into one section called Requirements and include everything. But the instruction says we can use those headings; not required to use all. Prefer few substantive sections. So maybe we just have About the role, Responsibilities, Requirements (including basic quals, preferred quals, skills, clearance, schedule, pay). But then we would have many thin sub-sections inside a list; that's okay. But we need to include Pay and Schedule sections if they have specific content. So we need separate sections for Pay and Schedule. Thus final sections: About the role, Responsibilities, Requirements, Qualifications (preferred), Pay, Schedule. We'll not include Skills separately. Now Qualifications (preferred): - Bachelor’s degree in computer science, information technology, or a related field. - CompTIA Security+ or CISSP. - Hands-on use of monitoring and logging tools (e.g., Grafana, Loki, Prometheus, CloudTrail) to find errors and confirm service health. - Experience building and supporting CI/CD or Git workflows, including diagnosing pipeline failures, rerunning jobs, and verifying deploy status. - Experience supporting and debugging production issues for both Kubernetes users and the platform’s own tool offerings, including collecting logs, events, and workload status. - Experience authoring Infrastructure as Code: Terraform that consumes existing modules, and Ansible or similar that use published collections. - Familiarity with DNS, certificates, load balancers, and remote access (VPN, bastion, SSH, RDP, WinRM), plus basic connectivity checks (ping, curl, traceroute) to separate network problems from application failures. - Experience remediating platform CVEs (e.g., container, EC2, Lambda) and guiding platform users through remediating CVEs in their own workloads. - Experience supporting disaster recovery activities: following DR runbooks, performing backup and recovery, and confirming services are back to a known-good state. - Prior support work in government, DoD, or other regulated environments. - Experience writing platform user guidance, SO