Intermediate Platform Support Engineer
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:
- Role description: "MITRE Mission Computing is seeking a Platform Support Engineer..." includes responsibilities. So we can have "Responsibilities" section.
- Basic Qualifications: list of qualifications.
- Preferred Qualifications: list.
- Must be eligible to obtain Secret clearance etc.
- Work location: "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. Could be "Schedule" maybe.
- Salary compensation range: "$103,600 - $129,500 - $155,400". That's Pay.
- Benefits: "Benefits information may be found here." Not specific benefits listed, just a link. The instruction: never create Benefits section unless posting actually states them. It only says "Benefits information may be found here." No specifics, so we should not include Benefits section.
- Work Location Type: Onsite. That's schedule? Could be part of Schedule.
- Also there is "Active Secret Clearance" etc.
- There's also "Preferred Qualifications" list.
- There's also "Basic Qualifications".
- There's also "Roles & Responsibilities" heading in original.
Thus we can create sections:
About the role
maybe include introductory paragraph about MITRE Mission Computing and the role purpose.
But we need to avoid repeating job title as heading. The job title is Platform Support Engineer. Not to repeat as heading.
We can put an About the role
with a
summarizing the description: MITRE Mission Computing is a new organization... seeking a Platform Support Engineer to be front line for systems enabling critical national security work... etc. Must preserve all substantive info, not invent or summarize away detail. We need to preserve all substantive information; we can't omit details. But we can paraphrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should not lose any detail; we need to keep the content. However we can rephrase? Summarizing away detail is prohibited. So we need to keep the details, maybe by copying the paragraphs verbatim inside
. That's okay. Thus we can have sections: - About the role: include the introductory paragraphs describing MITRE Mission Computing and the role purpose. - Responsibilities: include the bullet list of duties from "Roles & Responsibilities:" paragraph. - Basic Qualifications: list. - Preferred Qualifications: list. - Pay: include salary range. - Schedule: include onsite requirement (3 days per week on-site) and location list. - Possibly also "Security Clearance" but not a standard heading; we could include under Requirements or Qualifications. Since we have Basic and Preferred qualifications sections, we can include clearance there. We must not include sections like Benefits (no specifics). Also not include EEO etc. We need to output only HTML fragment, no /, no markdown fences. Let's extract exact text. From posting: Intro: "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 "Roles & Responsibilities:" paragraph: "MITRE Mission Computing is seeking a Platform Support Engineer to be the front line for the systems that enable critical national security work across MITRE’s Federally Funded Research and Development Centers. You will 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. You will 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. A core part of the job is guiding those teams on how to use the platform and its tools correctly and securely. You will operate in a high-stakes environment defined by novel problems and real constraints, including CMMC compliance, high availability, and cyber resilience. In this environment you will 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, we would like to hear from you. If you are energized by solving hard problems at scale, prefer deep technical ownership over narrow specialization, and want your engineering decisions to have lasting impact, we would like to hear from you. This an operations role with the primary responsibility being to support our internal customers & interfacing with them directly, triaging issues, solving customer problems, etc." Note: there is a typo "This an operations role". We'll keep as is. Then "Basic Qualifications:" list: - 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 "Preferred Qualifications:" list: - 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 after that: "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 Salary compensation range and midpoint: $103,600 - $129,500 - $155,400 Annual Work Location Type: Onsite" Then legal stuff. We need to include Pay section with salary range. Schedule section: maybe combine onsite requirement and location. We should not repeat the job title as heading. We need to ensure we don't include boilerplate like EEO, legal, copyright, etc. Now produce HTML. Structure:
About the role
...
Responsibilities
- ... ...
but instruction says use
- for any list of duties/requirements/benefits. The responsibilities are a list of duties, so we should use
- . We need to extract each duty. Let's parse responsibilities paragraph into bullet points: - 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. - If 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