Digital Experience Lead

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. No Job ID. Remove boilerplate. We need to extract content. Let's parse posting. First paragraph: At MITRE, your passion fuels work... This is about organization. Could be "About the role"? Actually "About the role" maybe description of role. The posting includes description of CXA organization and role. So we can put that under "About the role". Use

About the role

then

with that prose. Then "Roles & Responsibilities:" list. We'll put under

Responsibilities

with

• each bullet. Then "Basic Qualifications:" and "Preferred Qualifications:" maybe combine into Requirements and Qualifications? The instruction: sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. "Basic Qualifications:" likely Requirements. "Preferred Qualifications:" maybe Qualifications? Or Skills? There's also skills mentioned: "Ability to communicate well..." etc. Could be Skills. We need to preserve all substantive info. Let's extract: Basic Qualifications bullet list: - Typically requires a minimum of 8 years of related experience with a Bachelor’s degree; or 6 years and a Master’s degree; or a PhD with 3 years’ experience; or equivalent combination of related education and work experience. - 5 year’s experience improving websites, internal digital services, external platforms, or similar digital experiences. - Experience managing a roadmap, backlog, or comparable portfolio of work across more than one digital property. - Ability to turn user and stakeholder needs into well-defined, prioritized work. - Strong understanding of UX, information architecture, content structure, inclusive design, and responsive digital experiences. - Good visual and design judgment, including the ability to give useful feedback on page layout, hierarchy, and user flow. - Hands-on experience with Drupal, WordPress, and SharePoint, as well as working knowledge of HTML, CSS, and JSON. - Demonstrated fluency with generative AI and AI-enabled digital tools, including experience designing, testing, and improving reusable AI skills or workflows; evaluating outputs; and knowing when human review or escalation is needed. - Experience using web analytics, user feedback, and digital measurement to inform decisions. - Experience supporting an email-marketing and marketing-automation platform. - This position requires a minimum of 3 days a week on-site. Preferred Qualifications: - Ability to communicate well with both technical and nontechnical audiences and work effectively across teams without direct authority. - Experience in a large, matrixed, regulated, or mission-focused organization. - Knowledge of Section 508, WCAG, privacy, and digital-security practices. - Familiarity with the technical foundations of design systems, including design tokens, component structures, APIs, and basic JavaScript or XML concepts. - Experience working with agencies, contractors, or other outside delivery partners. Also note: "This requisition requires the candidate to have a minimum of the following clearance(s): None" and similar lines - we can drop as boilerplate. Salary compensation range and midpoint: $127,200 - $159,000 - $190,800 Annual Work Location Type: Onsite We need Pay section if posting actually states them. Yes salary range given. So Pay section. Schedule: maybe "This position requires a minimum of 3 days a week on-site." That's schedule info. Also "Annual Work Location Type: Onsite". So schedule could be about onsite requirement. We'll include Schedule section with that info. Benefits: posting mentions "competitive benefits" earlier but no specific benefits listed. There's a line "Benefits information may be found here." No specifics. So we should NOT create Benefits section because no specific content. According to rule: never create Benefits unless posting actually states them. So omit Benefits. Skills: we could extract skills from qualifications: e.g., UX, IA, design judgment, HTML/CSS/JSON, Drupal/WordPress/SharePoint, generative AI, analytics, email marketing, communication, etc. But we already have many in qualifications. Perhaps we can put skills section summarizing skill-based items. However we must not invent or summarize away detail. We could keep skills as a separate section listing skill-based items from qualifications that are skill-oriented. But we need to preserve all substantive info; we can keep them in Requirements and Qualifications sections. The instruction says we can have sections: Requirements, Qualifications, Skills. It's okay to have some overlap? Probably better to put skill-based items under Skills, and experience/education under Requirements/Qualifications. But we must not lose info. Let's decide: Use Requirements for education/experience minimums (the first bullet about degrees/years). Use Qualifications for the list of experience items (5 years improving websites, managing roadmap, etc). Use Skills for abilities like UX understanding, visual design judgment, hands-on experience with tools, generative AI fluency, analytics, email marketing, communication ability, etc. However some of those also appear in qualifications. To avoid duplication, we could split. But the instruction: "Prefer a few substantive sections over many thin ones." So maybe we just have Requirements (combining basic qualifications) and Qualifications (preferred). And maybe Skills not needed. But we have a Skills section in list; we can omit if no specific skill content beyond what's already covered. However there are skill statements like "Strong understanding of UX, information architecture..." which are skills. Could be placed under Skills. Let's think: The posting includes both basic and preferred qualifications; we could treat basic as Requirements, preferred as Qualifications. Then we could have Skills for the skill-based items like "Ability to turn user and stakeholder needs into well-defined, prioritized work." etc. But many of those are also in basic. Given the instruction to prefer few sections, maybe we just have About the role, Responsibilities, Requirements (combining basic and preferred), Pay, Schedule. And omit Qualifications and Skills. But the instruction list includes those headings; we can omit if no real specific content. However we do have specific content for Qualifications (preferred) and Skills (various). Might be better to include them. Let's produce sections: - About the role: description of MITRE, CXA organization, role summary. - Responsibilities: the bullet list under "Roles & Responsibilities:" (two sub-sections: Digital Product and Experience Delivery, Platform and Publishing Support, Measurement and Continuous Improvement). We'll flatten into list items. - Requirements: Basic Qualifications bullets. - Qualifications: Preferred Qualifications bullets. - Skills: maybe we can extract skill-specific items that are not covered elsewhere: e.g., "Ability to communicate well with both technical and nontechnical audiences and work effectively across teams without direct authority." (already in preferred). "Knowledge of Section 508, WCAG, privacy, and digital-security practices." (preferred). "Familiarity with the technical foundations of design systems..." (preferred). "Experience working with agencies, contractors, or other outside delivery partners." (preferred). Also "Strong understanding of UX, information architecture, content structure, inclusive design, and responsive digital experiences." (basic). "Good visual and design judgment..." (basic). "Hands-on experience with Drupal, WordPress, and SharePoint, as well as working knowledge of HTML, CSS, and JSON." (basic). "Demonstrated fluency with generative AI and AI-enabled digital tools..." (basic). "Experience using web analytics, user feedback, and digital measurement to inform decisions." (basic). "Experience supporting an email-marketing and marketing-automation platform." (basic). "Ability to turn user and stakeholder needs into well-defined, prioritized work." (basic). So many skill items are already in basic/preferred. If we create Skills section, we would duplicate. To avoid duplication, maybe we omit Skills section and keep skill details within Requirements and Qualifications. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule. Check if we have Benefits: no specific, omit. Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now craft HTML. We'll wrap each section in

  heading then content. For lists:

  • ...

  For prose:

  ... We need to preserve all substantive information; ensure we don't lose any. Let's extract About the role prose: "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. The Communications and External Affairs (CXA) organization helps MITRE communicate with clarity, consistency, and impact across the audiences that matter most to our mission. The organization leads mission and enterprise communications, external affairs, executive communications, public affairs, stakeholder engagement, events, digital channels, and reputation management in support of MITRE’s public-interest mission. The Digital Experience Lead is a strategic, hands-on individual contributor who strengthens how people experience MITRE across a defined portfolio of public-facing, internal, and external digital properties. The role combines digital experience strategy, strong visual and interface-design judgment, UX fundamentals, AI fluency, and day-to-day ownership of assigned web and digital channels. The ideal candidate draws on data, user insight, design systems, generative AI, and sound product and design judgment to create more useful, consistent, and effective experiences while improving the speed and quality of digital delivery. Working with content, design, technology, research, and communications colleagues, the Lead translates audience and stakeholder needs into accessible, well-maintained digital properties; identifies practical opportunities for AI-enabled improvement; and helps establish reusable, human-centered ways of working." That's a big paragraph. We'll put as

  ...

  . Now Responsibilities: need to capture all bullet points under Roles & Responsibilities. Let's list them: Digital Product and Experience Delivery - Maintain the roadmap and backlog for assigned websites, internal web experiences, and external platforms. - Partner with enterprise technology teams to deliver a new workforce communications platform. - Turn stakeholder and user needs into clear requirements, user stories, acceptance criteria, and delivery plans. - Improve user journeys, navigation, search, page layouts, reusable components, and content findability. - Use generative AI and AI-enabled tools to improve research, prototyping, content development, analysis, testing, documentation, and routine work. - Test outputs for accuracy, accessibility, brand, and quality; apply human review. - Use AI-enabled tools to rapidly prototype, produce, and optimize distinctive web experiences while meeting brand and quality standards. - Apply design-system principles to AI-enabled experiences, workflows, and reusable components so they are consistent, accessible, on-brand, and useful. - Design, build, test, and improve reusable AI skills and workflows that enhance digital operations. - Evaluate them for usability, accuracy, usefulness, and operational value, using feedback and human review to refine them. - Work with designers, writers, developers, accessibility specialists, and business partners to plan, test, launch, and improve digital experiences. - Provide clear feedback on design concepts and completed work, with attention to usability, visual hierarchy, accessibility, consistency, and brand alignment. - Coordinate with outside partners, review deliverables, raise issues early, and keep work on track. Platform and Publishing Support - Help diagnose website and platform issues. - Distinguish among content, UX, CMS, platform, and basic front-end issues, then connect the