Intermediate Platform Support Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to extract content. The posting includes: - Intro paragraph about MITRE, mission computing, etc. Could be "About the role" or maybe "About MITRE". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections are present. We have: - About the role: description of MITRE Mission Computing, opportunity, etc. Could be considered "About the role". We'll include that. - Responsibilities: "Roles & Responsibilities:" section with bullet points. - Basic Qualifications: list of qualifications. - Preferred Qualifications: list. - Skills: maybe combine qualifications? But we could have a Skills section for technical skills. However we have both Basic and Preferred qualifications; we could treat them as Requirements and Qualifications. The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide mapping. We have Basic Qualifications (requirements) and Preferred Qualifications (preferred). Could map Basic to Requirements, Preferred to Qualifications. Skills maybe not separate; we could embed skills within qualifications. We have Pay: Salary compensation range and midpoint: $103,600 - $129,500 - $155,400. So we have Pay section. We have 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." Also "Annual Work Location Type: Onsite". So schedule info: onsite requirement 3 days/week. We'll include Schedule. Benefits: The posting mentions "competitive benefits" but no specific benefits listed. There's a line: "Benefits information may be found here." No actual benefits detail. According to rule: never create Benefits section unless posting actually states them. Since no specific benefits listed, we should not include Benefits section. We must not include boilerplate like EEO, legal, etc. We need to preserve all substantive information. So we need to include the intro paragraphs about MITRE, mission computing, etc. Possibly under About the role. We need to format responsibilities as

• . Similarly qualifications. We need to avoid repeating job title as heading. No job title given explicitly but we can ignore. We need to output only HTML fragment, no /, no markdown fences. Let's craft:

  About the role

  At MITRE, your passion fuels work that impacts our nation and improves lives. This is where your skills strengthen national security, cybersecurity, health, transportation, and citizen services. We’re a nonprofit engineering, applied research, and advanced technology organization working in the public interest. With objectivity and integrity at our core, we lead federally funded research and development centers for U.S. government agencies – collaborating with industry and academia to deliver integrated, high-impact solutions that advance our nation’s health, security, and prosperity. Our people tackle the toughest technical challenges, supported by competitive benefits, meaningful career development, and a culture of innovation, collaboration, and technical excellence. Choose MITRE for a career with purpose — and help shape the future. MITRE Mission Computing is a new organization that bridges the gap between Mission and Technology and helps enable MTIRE projects to focus on their work, without worrying about compliance and the underlying platform infrastructure. We apply new technologies that can address the Government's most challenging Systems Engineering problems. This is an opportunity for experienced platform engineers who are highly motivated, innovative, and proactive and interested in owning and maintaining their work to enable the rest of MITRE and sponsors.

  Then Responsibilities:

  Responsibilities

  • 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, and 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.
  • Support internal customers directly, triaging issues, solving customer problems, etc.
  Then Requirements (Basic Qualifications):

  Requirements

  • 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.
  Then Qualifications (Preferred):

  Qualifications

  • 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, SOPs, runbooks, knowledge‑base articles, status updates, and post‑mortems.
  • Background or strong interest in platform, SRE, or cloud operations work.
  • Active Secret Clearance.
  Then Pay:

  Pay

  Salary compensation range and midpoint: $103,600 - $129,500 - $155,400

  Then Schedule:

  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. Annual Work Location Type: Onsite.

  We need to ensure we didn't repeat any info unnecessarily. The onsite requirement appears both in Requirements and Schedule; but we can keep both as they are distinct: Requirements includes the onsite requirement as part of eligibility; Schedule repeats it. Might be okay but could be considered duplication. However we must preserve ALL substantive information; we can keep it in both places. Could also move onsite to Schedule only and remove from Requirements. But the requirement includes onsite as part of eligibility; it's substantive. If we remove from Requirements we lose that info from Requirements section. But we could keep it only in Schedule and note that Requirements includes eligibility etc. However the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the onsite requirement somewhere. It's okay to keep it only in Schedule and not duplicate. But we also have the onsite requirement in Requirements as a bullet; if we remove it we lose that detail from Requirements. But we could keep it in Requirements and not duplicate in Schedule (just mention Annual Work Location Type: Onsite). However the Schedule section should reflect the schedule info; we can keep the onsite days there and maybe not duplicate in Requirements. Let's see: The Requirements bullet includes "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 exactly the schedule info. So we could keep that bullet in Requirements and then Schedule could just say "Annual Work Location Type: Onsite." But the schedule info is more specific: 3 days per week on-site. If we only put that in Requirements, we still have the info. The Schedule section could be brief: "Annual Work Location Type: Onsite." That still conveys schedule info but loses the 3 days per week detail. However the schedule detail is substantive; we should keep it. So we could keep the onsite days in Requirements and also include in Schedule but maybe rephrase to avoid exact duplication? The rule didn't forbid duplication, but we should avoid unnecessary duplication? Not explicitly forbidden. It says "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not prohibited. So we can keep both. Now check for any other sections: Benefits we omitted because no specific benefits. Good. Check for any other info like "Annual Work Location Type: Onsite" we included in Schedule. Check for any other info like "This requisition requires the candidate to have a minimum of the following clearance(s): None" and "This requisition requires the hired candidate to have or obtain, within one year from the date of hire, the following clearance(s): Secret