Jobs · Information Technology · Virginia

Embedded User Experience (UX) Consultant - REMOTE (1062)

Herdt Consulting, Inc. · Alexandria, VA · 3 wk ago
On-siteInformation TechnologyFull-time
We need to produce HTML fragment with sections: About the role? The posting includes Position Overview, Quick Facts, Key Responsibilities, Required Qualifications, Preferred Qualifications, What we can offer you. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. We need to map content to these headings appropriately. We have: - Position Overview: could be "About the role". Use

About the role

with paragraph(s) summarizing overview. - Quick Facts: includes Location, Security Clearance, Citizenship, Education, Experience, Work Schedule, Alignment. Some of these are metadata; we can fold minor metadata into a short

or drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So Quick Facts could be a short paragraph containing location, clearance, citizenship, education, experience, work schedule, alignment. However we also have separate sections for Pay, Schedule, Benefits. The posting includes Work Schedule: Full-time. Also Alignment: W2, 1099, or C2C are acceptable (No 3rd parties). That's not pay but contract type. Pay not mentioned. Benefits are listed under "What we can offer you": includes Time Off, Health Benefits, Financial Security, Insurance. So we can create Benefits section. We need to avoid sections like Pay or Schedule unless posting actually states them. Work Schedule is stated: Full-time. So we could include a Schedule section with that detail. Pay not mentioned, so omit Pay section. We need to include Responsibilities section: Key Responsibilities. Requirements/Qualifications: we have Required Qualifications and Preferred Qualifications. Could combine into Requirements section? The instruction: Use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide to have Requirements (maybe Required Qualifications) and Preferred Qualifications could be under Skills? Or we could have Qualifications section covering both required and preferred. But we need to preserve all substantive info. We could have: -

About the role

(position overview) -

Responsibilities

(key responsibilities) -

Requirements

(required qualifications) -

Skills

(maybe preferred qualifications? Or we could put preferred qualifications under Skills) -

Benefits

(what we can offer) -

Schedule

(work schedule) We must not repeat job title as heading. Ensure we don't include filler like "commensurate with experience". Not present. We need to use
  • for any list of duties/requirements/benefits, and

    for prose. Thus: - About the role: prose paragraph(s) from Position Overview. - Responsibilities: list each responsibility as

  • . - Requirements: list each required qualification as
  • . - Skills: list each preferred qualification as
  • (or maybe combine required and preferred under Requirements? But we need to follow headings; we can put preferred under Skills.) - Benefits: list each benefit as
  • . - Schedule: maybe a

    stating Work Schedule: Full-time. Could also include Alignment info? Alignment is contract type; maybe we could include in Schedule? But better to keep schedule only for work schedule. Alignment could be folded into a short paragraph under About the role or maybe under Requirements? It's not a requirement. Could be minor metadata; we could drop it or include in a short

    under About the role. The instruction: fold minor metadata into a short

    or drop it. So we can include a short paragraph after About the role maybe containing Location, Security Clearance, Citizenship, Education, Experience, Work Schedule, Alignment. But we already have Work Schedule separate; we could still include location etc in About the role paragraph. Better: About the role paragraph includes overview; then we can have a short

    for Quick Facts (location, clearance, citizenship, education, experience, work schedule, alignment). But we must not create a heading for Quick Facts; just a paragraph. Thus structure:

    About the role

    Position Overview Herdt Consulting is seeking an Embedded User Experience (UX) Business Process Analyst to support a large-scale DoD modernization program delivering mission-critical ERP modernization, and optimization services across its supported commands. This position supports the Retail and Food Service (RFS) end-to-end business processes and will work closely with client stakeholders and cross-functional UX, business, technical, and delivery teams to understand operational needs and translate them into actionable user experience, change, adoption, and readiness activities.

    Quick Facts: Location: Remote. Security Clearance: Secret. Citizenship: US Citizenship Required. Education: Bachelor’s degree in a relevant discipline. Experience: Hands-on US Navy Afloat Retail & Food Service experience. Work Schedule: Full-time. Alignment: W2, 1099, or C2C are acceptable (No 3rd parties, please).

    Then Responsibilities list. Then Requirements list (required qualifications). Then Skills list (preferred qualifications). Then Benefits list. Then Schedule? Actually we already included Work Schedule in Quick Facts paragraph. But we might still need a Schedule section if we want to follow instruction to include section only when posting has real specific content. Since we already included schedule in Quick Facts, we could omit separate Schedule section. However the instruction says: Prefer a few substantive sections over many thin ones. So we could keep Schedule section with just the work schedule detail, but that would be thin. Better to incorporate schedule into Quick Facts paragraph and not have a separate Schedule heading. That's fine. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits. Check if we need to include any other headings like Qualifications? We used Requirements for required qualifications, Skills for preferred qualifications. That seems okay. Now ensure we use
    • for lists. Let's extract details. Position Overview text: "Position Overview Herdt Consulting is seeking an Embedded User Experience (UX) Business Process Analyst to support a large-scale DoD modernization program delivering mission-critical ERP modernization, and optimization services across its supported commands. This position supports the Retail and Food Service (RFS) end-to-end business processes and will work closely with client stakeholders and cross-functional UX, business, technical, and delivery teams to understand operational needs and translate them into actionable user experience, change, adoption, and readiness activities." We need to preserve all substantive information; we can keep as is. Quick Facts paragraph: combine all. Location: Remote Security Clearance: Secret Citizenship: US Citizenship Required Education: Bachelor’s degree in a relevant discipline Experience: Hands-on US Navy Afloat Retail & Food Service experience Work Schedule: Full-time Alignment: W2, 1099, or C2C are acceptable (No 3rd parties, please) We'll write as a sentence. Now Responsibilities list (Key Responsibilities): - Engage with Retail and Food Service stakeholders to gather, analyze, document, and communicate user and business needs. - Translate operational requirements and user perspectives into journey maps, process flows, change impact assessments, adoption recommendations, readiness communications, and related UX artifacts. - Apply practical knowledge of afloat Retail and Food Service operations to help ensure future-state processes reflect the needs of users and operational environments. - Collaborate across UX, business, functional, technical, change management, and delivery teams to coordinate activities and maintain alignment across the program. - Facilitate and provide administrative support for workshops, working sessions, stakeholder discussions, and other collaborative activities. - Support project-wide coordination and track multiple concurrent, time-sensitive deliverables and dependencies. - Identify and communicate potential impacts of future-state processes and technology changes on users, roles, workflows, and operational activities. - Contribute to user adoption and organizational readiness activities associated with the modernization effort. - Develop clear, concise communications and supporting materials for stakeholders across varying functional and technical backgrounds. - Participate in Agile delivery activities, as applicable, including backlog refinement, sprint planning, and development of user stories. Now Required Qualifications list: - Demonstrated hands-on experience supporting Navy ERP in a functional capacity, with the ability to operate effectively within the Navy environment from the outset. - Experience or practical knowledge of afloat Retail operations and afloat Food Service operations. - Experience in one or more of the following areas: Business analysis, User experience (UX), Organizational change management (OCM), Business process improvement. - Demonstrated ability to gather, analyze, synthesize, and communicate user and business needs. - Ability to manage competing priorities and coordinate activities across business, UX, technology, and delivery teams. - Strong written and verbal communication skills. - Strong facilitation, collaboration, and stakeholder management skills. - Ability to manage multiple deliverables and deadlines in a complex program environment. Now Preferred Qualifications list (Skills): - Experience developing process flows, journey maps, user journeys, or similar business/UX artifacts. - Experience supporting Navy financial management and/or supply chain operations. - Prior Navy service as a Food Service Officer, Supply Officer, or Galley/Supply Leading Chief Petty Officer (LCPO). - Prior Navy ERP experience. - Experience with or knowledge of SAP S/4HANA. - Familiarity with Agile delivery practices, including backlogs, sprint planning, and user stories. - Experience supporting large-scale ERP modernization, digital transformation, or organizational change initiatives. Now Benefits list (What we can offer you): - Excellence: The chance to be part of a company with a reputation for excellence in task execution. - Time Off: 3 weeks of paid vacation each year plus 11 federal holidays. - Health Benefits: Competitive Medical (Blue Cross Blue Shield), Dental, and Vision insurance. - Financial Security: 401K program with Fidelity (including company match) and Flexible Spending Account (FSA). - Insurance: Short-term and Long-term Disability provided at no cost, plus voluntary Life and AD&D options. We need to ensure we preserve all substantive info; we kept the bullet points as given. Now produce HTML fragment. We must not include markdown code fences. Just raw HTML. Let's craft:

      About the role

      Position Overview Herdt Consulting is seeking an Embedded User Experience (UX) Business Process Analyst to support a large-scale DoD modernization program delivering mission-critical ERP modernization, and optimization services across its supported commands. This position supports the Retail and Food Service (RFS) end-to-end business processes and will work closely with client stakeholders and cross-functional UX, business, technical, and delivery teams to understand operational needs and translate them into actionable user experience, change, adoption, and readiness activities.

      Quick Facts: Location: Remote. Security Clearance: Secret. Citizenship: US Citizenship Required. Education: Bachelor’s degree in a relevant discipline. Experience: Hands-on US Navy Afloat Retail & Food Service experience. Work Schedule: Full-time. Alignment: W2, 1099, or C2C are acceptable (No 3rd parties, please).

      Responsibilities

      • Engage with Retail and Food Service stakeholders to gather, analyze, document, and communicate user and business needs.
      • Translate operational requirements and user perspectives into journey maps, process flows, change impact assessments, adoption recommendations, readiness communications, and related UX artifacts.
      • Apply practical knowledge of afloat Retail and Food Service operations to help ensure future-state processes reflect the needs of users and operational environments.
      • Collaborate across UX, business, functional, technical, change management, and delivery teams to coordinate activities and maintain alignment across the program.
      • Facilitate and provide administrative support for workshops, working sessions, stakeholder discussions, and other collaborative activities.
      • Support project-wide coordination and track multiple concurrent, time-sensitive deliverables and dependencies.
      • Identify and communicate

Similar jobs