Business Process Engineer

We need to output HTML fragment with sections: About the role (maybe Position Summary), Responsibilities, Qualifications, Benefits, Pay, Schedule (if present). Also maybe Preferred Qualifications? The instruction: use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include only sections with real content. The posting includes Position Summary (we can map to About the role). Responsibilities present. Qualifications present (including required and preferred). Benefits present. Pay range present. Working conditions includes schedule (Standard Business hours Monday through Friday, occasional extended or weekend hours). That's schedule info. So we can include Schedule section. We should not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO, E-Verify, mission statement, etc. Also remove "Other Considerations: U.S. Citizen or Permanent Resident (Required)" maybe part of qualifications? It's a requirement; we could incorporate into Qualifications as a bullet? But we should preserve all substantive information. The "Other Considerations" line is a requirement: U.S. Citizen or Permanent Resident (Required). Also "Position is contingent on contract award." That's also substantive. We need to preserve that info. Where to put? Could be part of Qualifications or maybe a separate section like Requirements? But we have no explicit Requirements heading; we could put under Qualifications or maybe a separate "Requirements" section. The instruction says we can use headings like Requirements, Qualifications, Skills. We have Qualifications already; we could add a Requirement bullet for citizenship and contingency. Or we could add a separate "Requirements" section. Since we already have Qualifications, we could include those points there. But the instruction: "Prefer a few substantive sections over many thin ones." So maybe combine citizenship and contract contingency into Qualifications as bullet points. Also "Other Considerations: U.S. Citizen or Permanent Resident (Required)" is a consideration; we can treat as a qualification. Also "Position is contingent on contract award." That's a condition; we can include as a note under Qualifications or maybe under About the role? Probably under Qualifications as a note. We need to preserve all substantive information: So we must include the citizenship requirement and contingency. We also have "Standard Business hours are Monday through Friday. Occasional extended or weekend hours may be required based on operational needs." That's schedule. We have "Must have reliable internet service that allows for effective telecommuting on remote days." That's also working condition; could be part of Schedule or maybe a separate note. Could include in Schedule section. We have "PAY RANGE" details. We have Benefits list. We need to strip boilerplate: EEO STATEMENT, WORK AUTHORIZATION (E-Verify), mission statement paragraphs, etc. Also remove "Other Considerations:" line? We'll incorporate its content. We must not invent or summarize away detail. So we need to keep the exact wording? Not necessarily exact but preserve all substantive information; we can rephrase but must not lose detail. Safer to keep original sentences. We'll produce HTML:

About the role

Position Summary Sprezzatura is seeking an experienced Business Process Engineer / Service Designer to support the implementation of a modernized financial and budget application for a federal client. This hands-on role will work with business stakeholders, Business Analysts, and technical teams to analyze existing business processes and design optimized future-state processes, workflows, and service blueprints that guide platform configuration and development. The ideal candidate combines strong business process engineering and service design skills with the ability to translate complex business operations into clear, structured, implementation-ready process designs. You will help ensure the solution does not simply replicate legacy processes but instead takes advantage of modern workflow capabilities to simplify, standardize, and improve how work is performed.

But note: The Position Summary already includes that text; we can keep it. We should not repeat "Position Title:" etc. Now Responsibilities: we need to list each responsibility as

• . The responsibilities block is a long sentence with many items separated by line breaks? Actually the responsibilities are a paragraph with many sentences separated by line breaks? In the source, each responsibility appears as a separate line but not bullet. We'll split into items based on the sentences that start with verbs. Let's extract: - Lead business process discovery and design activities through stakeholder interviews, workshops, observation, process walkthroughs, and collaborative design sessions - Analyze and document current-state business processes, including activities, roles, handoffs, systems, data interactions, pain points, dependencies, controls, and exceptions - Design optimized future-state processes and workflows that address business needs while reducing unnecessary complexity and improving efficiency - Develop detailed service blueprints and workflow models that serve as implementation guides for platform development teams - Model process activities, decision points, approvals, roles, business rules, handoffs, statuses, triggers, dependencies, exception paths, and escalation scenarios - Apply BPMN and service design techniques to create consistent, understandable, and implementation-ready process artifacts - Map interactions among users, business processes, data, systems, and supporting services across end-to-end workflows - Partner with Business Analysts and subject matter experts to ensure process designs accurately reflect business requirements, Federal financial processes, policies, controls, and operational needs - Challenge unnecessary legacy practices and help stakeholders distinguish between business requirements and legacy-system constraints or behaviors - Identify opportunities for process simplification, standardization, automation, and improved user experience - Collaborate closely with solution architects, platform developers, and integration teams to ensure future-state designs can be effectively implemented within a configurable workflow platform - Refine process designs based on technical feasibility, stakeholder feedback, testing results, and evolving business needs - Support development and testing teams by clarifying process intent, workflow behavior, business rules, exception scenarios, and expected outcomes - Maintain process and service-design artifacts as the solution evolves through implementation We'll put each as
• . Qualifications: we have required qualifications list (bulleted) and preferred qualifications list. We'll combine maybe into two subsections? But we can just list all qualifications as bullets, maybe separate required vs preferred with headings? But we only allowed headings like Qualifications, Skills. Could have Qualifications section with required bullets, and then a Skills section for preferred? But better to keep Qualifications for required, and maybe a separate "Preferred Qualifications" section? The instruction says we can use headings like Qualifications, Skills. So we could have Qualifications for required, and Skills for preferred. However the preferred list includes experience, certifications, etc. Could treat as Skills. But we must not create thin sections; but we have enough content. Let's do:

  Qualifications

  • 7+ years of experience in Business Process Engineering, Service Design, Business Process Management, Process Improvement, or a related discipline supporting complex enterprise transformation or technology initiatives
  • Demonstrated experience designing future-state business processes and workflow-driven solutions, not solely documenting existing processes
  • Strong hands-on experience developing business process models, workflow diagrams, and service blueprints
  • Experience applying Business Process Model and Notation (BPMN) or comparable structured process-modeling methodologies
  • Experience modeling complex workflows involving roles, approvals, decision points, business rules, controls, handoffs, systems, data, exceptions, and alternate process paths
  • Demonstrated ability to translate complex business operations into clear, detailed process designs that can guide technical implementation
  • Experience facilitating process-discovery, process-design, and future-state workshops with business and technical stakeholders
  • Experience identifying opportunities for process improvement, simplification, standardization, and automation
  • Experience supporting Federal Government programs, systems, or modernization initiatives
  • Experience working collaboratively with Business Analysts, product/functional teams, architects, developers, and testers
  • Strong analytical, facilitation, visualization, communication, and problem-solving skills
  • Ability to meet applicable Federal background investigation/security requirements
  • U.S. Citizen or Permanent Resident (Required)
  • Position is contingent on contract award
  Then maybe a Skills section for preferred qualifications:

  Skills

  • Experience designing or modernizing financial management, budgeting, acquisition, planning, accounting, or related business processes
  • Experience with Federal PPBE, budget formulation, budget execution, acquisition planning, or IT investment management processes
  • Experience supporting Department of Veterans Affairs (VA) programs, systems, or business processes
  • Experience designing processes for configurable enterprise, workflow, ERP/EPM, financial, or low-code platforms
  • Experience with OneStream, ServiceNow, Appian, Salesforce, or comparable workflow-driven platforms
  • Experience applying human-centered design or service-design methodologies, including journey mapping and service blueprinting
  • Experience with process modeling/design tools such as Visio, Lucidchart, Signavio, ARIS, or comparable tools
  • Familiarity with Agile delivery and tools such as Jira and Confluence
  • Relevant certification in BPM, Lean Six Sigma, Service Design, Human-Centered Design, or related disciplines
  Benefits: we have list. We'll output:

  Benefits

  • Medical, Dental, and Vision
  • Health Saving Account (when enrolled in eligible plan) with Company contribution
  • Company paid Life, Accidental Death, Short-term & Long-term Disability
  • Voluntary Accident, Hospital Indemnity, & Critical Care Insurance
  • Voluntary Medical & Dependent Care Flexible Spending Accounts
  • Accrued Paid Time Off & Company Paid Holidays
  • 401(k) Retirement Plan with Company match
  Pay: we have a paragraph.

  Pay

  The base salary range for this position is $112,000 to $139,000 annually, depending on geographic work location, relevant experience, skills, education, internal equity, security clearance, and contract requirements. Geographic salary ranges are determined in accordance with the company's compensation practices and represent a good-faith estimate of the compensation for this position at the time of posting.

  Schedule: we have working conditions.

  Schedule

  Standard Business hours are Monday through Friday. Occasional extended or weekend hours may be required based on operational needs. Must have reliable internet service that allows for effective telecommuting on remote days.

  We should not include any extra sections like About the role? Already did. Check for any leftover boilerplate: we removed EEO, E-Verify, mission statement, etc. Also removed "Other Considerations:" line but we incorporated its content. Also removed "Position Title:" line. Also removed "Location: Remote (In the U.S)" maybe we should keep location? The instruction: do not repeat job title as heading; but location is substantive? Could be included in About the role or maybe a separate paragraph. The location is Remote (In the U.S). That's substantive. We should preserve it. Where to put? Could add to About the role paragraph after position summary. Let's incorporate: "Location: Remote (In the U.S)." We'll add a sentence. Thus About the role paragraph: combine position summary and location. Let's craft:

  Sprezzatura is seeking an experienced Business Process Engineer / Service Designer to support the implementation of a modernized financial and budget application for a federal client. This hands-on role will work with business stakeholders, Business Analysts, and technical teams to analyze existing business processes and design optimized future-state processes, workflows, and service blueprints that guide platform configuration and development. The ideal candidate combines strong business process engineering and service design skills with the ability to translate complex business operations into clear, structured, implementation-ready process designs. You will help ensure the solution does not