Senior Full Stack Engineer, TS/SCI w/Polygraph

We need to output HTML fragment with sections: About the role? Actually we need to use

for section headings like About the list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Also must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes Salary compensation range and midpoint: $122,400 - $153,000 - $183,600. So we have Pay info. Also includes "Annual Work Location Type: Onsite". That's schedule? Actually schedule maybe not given. There's no explicit schedule like full-time, part-time, hours. So we should not create Schedule section unless there is real specific content. There's no schedule info besides onsite requirement of 5 days a week on-site. That could be considered schedule? It says "This position has an on-site requirement of 5 days a week on-site." That's location requirement, not schedule. Could be considered schedule? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states onsite requirement but not schedule like "Full-time" etc. Might still consider schedule not given. Safer to omit Schedule section. Benefits: The posting mentions "competitive benefits" but not specific benefits. It says "supported by competitive benefits, meaningful career development, and a culture of innovation". Also "Benefits information may be found here." No explicit benefits listed. So we should not create Benefits section unless specific benefits are listed. Since they are not, we omit Benefits. We need sections: About the role (maybe from department summary?), Responsibilities, Requirements, Qualifications, Skills. The posting includes "Roles & Responsibilities:" with bullet list. Also "Basic Qualifications:" and "Preferred Qualifications:" which could be split into Requirements and Qualifications? Usually Requirements = Basic Qualifications, Qualifications = Preferred Qualifications? Or we could combine. The instruction: Use headings for those categories. We'll create sections: About the role (department summary), Responsibilities, Requirements (Basic Qualifications), Qualifications (Preferred Qualifications), Skills (maybe list of skills from responsibilities? Could also include technical proficiencies). But we need to avoid thin sections. Let's see content: About the role: The department summary paragraph: "Do you want to develop software systems that contribute to solving our nation’s most critical problems? ..." plus MITRE description. That's substantive. Responsibilities: bullet list under "Responsibilities include:" plus preceding sentences. Requirements: Basic Qualifications bullet list (though it's paragraph). We'll extract each requirement as list items. Qualifications: Preferred Qualifications list. Skills: Could be derived from responsibilities and qualifications but maybe we can combine into Skills section summarizing technical skills: proficiency in languages, frameworks, etc. However we might avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. Could combine Requirements and Qualifications into one? But they ask to use those headings if content exists. We have both basic and preferred qualifications, so we can have Requirements (basic) and Qualifications (preferred). Skills maybe not needed if we already covered in qualifications. But we could still include Skills if we have specific skill set not covered elsewhere. However the qualifications already list many skills. Might be redundant. Better to omit Skills section to avoid thin. Pay: we have salary range. So we include Pay section. Schedule: we have onsite requirement 5 days a week. That's location not schedule. Could treat as schedule? The instruction says only create Schedule if posting actually states them. It does not state schedule like "Full-time", "Part-time", "Hours". So omit. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay. Now we need to format with

headings,

• for lists,

  for prose. We must preserve all substantive information, not invent or summarize away detail. Must not omit any substantive info. So we need to include all details from the posting that are not boilerplate. Let's extract: About the role: The paragraph starting "At MITRE, your passion fuels work..." includes many sentences. Also Department Summary: "Do you want to develop software systems..." etc. We'll combine into a cohesive prose but must not omit details. We'll need to keep all sentences. Let's copy the relevant text: "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. Department Summary: Do you want to develop software systems that contribute to solving our nation’s most critical problems? Do you want to work alongside engineers and scientists that are experts in their fields? Are you passionate about best practices for delivering the highest quality software solutions? We're making a difference every day—working for a safer, healthier, and more secure nation and world. At MITRE you will leverage your background and experience to make a difference in tangible, impactful problems that face our nation. You’ll work on diverse projects that support our Government sponsors and benefit from numerous learning and growth opportunities. Our workplace reflects our values. We want you to continue to grow your career at MITRE so that you can experience the gratifying work, our competitive benefits, exceptional professional development opportunities, and a culture of innovation that embraces flexibility, collaboration, and career growth." That's the about role. Now Responsibilities: The bullet list after "Responsibilities include:" plus preceding sentences: "MITRE is seeking a Senior Full Stack Engineer to support high-priority Intelligence Community (IC) initiatives requiring secure, scalable, and mission-driven application development. This role requires an active TS/SCI with Polygraph. The selected candidate will serve as a technical subject matter expert responsible for designing, developing, and deploying full stack applications within highly sensitive Intelligence Community environments. This position supports enterprise-level IC challenges related to technology modernization, data integration, analytic enablement, and secure collaboration." Then bullet list: - Collaborate directly with IC sponsors and MITRE technical teams to translate complex mission requirements into scalable application architectures. - Design, develop, and deploy secure front-end and back-end solutions within classified environments. - Deliver modern software capabilities, improving architecture, platforms, and developer workflows with strong engineering practices (secure coding, reviews, testing, maintainable design). - Partner with UX, Architecture, Data, Security, and Operations to define technical strategy and influence roadmaps with a customer-centric mindset. - Lead or support development of enterprise-grade applications addressing cross-IC integration, data visualization, workflow automation, and analytics. - Develop and maintain robust APIs, database schemas, and backend services supporting high-performance, secure applications. - Ensure performance, reliability, and security of deployed systems. - Implement scalable architectures aligned with DevSecOps and Infrastructure-as-Code principles. - Present technical solutions clearly to both technical and non-technical stakeholders. - Mentor junior developers and contribute to department-wide technical standards and tradecraft. - The primary responsibilities of this position must be carried out in person in McLean, Virginia or Bethesda, Maryland. - The successful candidate will establish regular presence at MITRE and IC locations and may be required to travel within the National Capital Region. We need to keep all that. Now Requirements (Basic Qualifications): The paragraph: "Basic Qualifications: Typically requires a minimum of 5 years of related experience with a Bachelor’s degree; or 3 years and a Master’s degree; or a PhD with relevant experience who can immediately contribute. Bachelor’s degree in Computer Science or Software Engineering. Demonstrated experience as a Full Stack Developer or similar engineering role in secure environments. Proficiency in front-end and back-end languages such as JavaScript, TypeScript, Python, or Go. Proficiency writing SQL queries, data transformations, and designing database schemas. Entrepreneurial and innovative spirit and the curiosity to explore and push the boundaries of software development and software solutions.Ability to work in Agile development environments with strong documentation practices.Must have an active Top Secret/SCI with Polygraph U.S Government issued Security Clearance. Per the U.S. Government’s eligibility requirements, you must be a U.S Citizen to be considered for a security clearance. This position has an on-site requirement of 5 days a week on-site ." We need to break into list items. Each sentence could be a list item. Ensure we preserve all details. Now Qualifications (Preferred Qualifications): The list after "Preferred Qualifications:" includes many items. We'll extract each bullet. List: - Advanced degree in a technical discipline (including but not limited to Software Engineering, Computer Science, Computer Engineering, Mathematics, etc.) - Experience with geospatial applications/stacks, preferably with open-source or ESRI geospatial development experience. - Experience with modern JavaScript frameworks such as React, Vue, Angular and HTMx. - Experience developing web applications with different architectures including server-side rendering (SSR), single page applications (SPAs), and hybrid applications (interactive islands pattern). - Experience with UI-first rapid prototyping and development approaches. - Experience with CSS frameworks such as Tailwind or Material Design-based libraries. - Experience with server-side technologies and database systems such as PostgreSQL. - Experience working within Linux-based environments, including command line and shell scripting. - Experience using version control systems (Git) and managing code reviews and releases. - Experience developing applications within Intelligence Community environments. - Expertise in one or more front-end technologies such as HTML, CSS, JavaScript, or TypeScript. - Expertise in one or more back-end languages such as Python, Go, or Full Stack TypeScript/JS. - Experience with AWS-managed services and cloud-native architectures. - Experience producing high-quality software documentation and design artifacts. - Familiarity with alternative JavaScript runtimes such as Bun or Deno. - Experience implementing SecDevOps pipelines in classified environments. Also note: "This requisition requires the candidate to have a minimum of the following clearance(s): Top Secret/SCI/Polygraph" and "This requisition requires the hired candidate to have or obtain, within one year from the date of hire, the following clearance(s): Top Secret/SCI/Polygraph". That's about clearance, but we already have clearance in Requirements. Might be duplicate; we should include it only once? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we need to avoid duplicating the clearance requirement. It appears in Basic Qualifications and again later. We should include it only once. We'll keep it in Requirements (Basic Qualifications) and omit the duplicate later. Also "Salary compensation range and midpoint: $122,400 - $153,000 - $183,600". We'll put in Pay section as a paragraph. Also "Annual Work Location Type: Onsite". That's location info; we might include in About the role or maybe as a note. But we already have onsite requirement in Requirements. Could mention location in About the role? Not needed. We'll keep the onsite requirement in Requirements (already there). The "Annual Work Location Type: Onsite" is redundant; we can drop as duplicate. Now we need to output HTML fragment only. Structure:

  About the role

  ... (the about role paragraph)

  Responsibilities

  • ... each bullet

  Requirements

  • ... each basic