Business Solutions Engineer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Company Summary (maybe About the role?), Position Summary (maybe About the role). Essential Functions & Primary Responsibilities (Responsibilities). Requirements Education & Qualifications (Requirements). Preferred Qualifications (Qualifications). Skills And Abilities (Skills). Core Competencies (maybe also Skills). Physical Demands & Abilities? Actually they have Skills And Abilities and Core Competencies. Could combine into Skills section. Benefits, Pay, Schedule: Not explicitly given. There's "Hours per Week: 40 hrs./week" and "Salary Exempt". That's schedule and pay info? Salary Exempt indicates exempt status, not salary amount. No specific pay amount. So we should not create Pay or Benefits sections unless actual content. Schedule: we have Hours per Week: 40 hrs./week. That's schedule info. So we can include a Schedule section with that detail. Benefits: none mentioned. Pay: none specific. So omit. We need headings:

About the role

,

Responsibilities

,

Requirements

,

Qualifications

,

Skills

,

Schedule

. Possibly also include "Company Summary" as About the role. We must not repeat job title as heading. Use

• for lists. Use

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Must not omit details. Must include all content from sections. We need to extract content: Company Summary: paragraphs about FPCU mission, values, etc. That's About the role. Position Summary: description of role phases etc. Could be part of About the role or Responsibilities? Probably About the role includes position summary. We'll combine. Essential Functions & Primary Responsibilities: list of bullet-like paragraphs each starting with bold headings. We need to turn each into list items. The content includes multiple responsibilities each with sub-bullets? Actually each responsibility is a paragraph with bold heading then description. We'll treat each as a list item. Requirements Education & Qualifications: bullet list of items: Bachelor’s degree..., 5+ years..., Demonstrated ability..., Deep proficiency..., Proven hands-on build experience..., Demonstrated ability to extract..., Working knowledge..., Strong process-analysis skills..., Excellent communication..., Self-directed... Preferred Qualifications: list items: Experience in financial services..., Familiarity with SharePoint..., Experience with conversational AI..., Familiarity with Power BI..., Experience with Jira..., Microsoft certifications..., Exposure to formal change-management... Skills And Abilities: list items: Represents FPCU..., Engages..., Maintains..., Ability to apply..., Adaptable..., Embraces... Core Competencies: list items: Builder's instinct..., Teacher's patience..., Business acumen..., Influence without authority..., Security-first mindset..., Pragmatism... Physical Demands & Work Environment: includes schedule info: Standard business hours with occasional flexibility required for deployment and training windows. Also physical demands etc. We'll extract schedule: Standard business hours with occasional flexibility required for deployment and training windows. Also Hours per Week: 40 hrs./week earlier. So schedule section can include both. We also have "Salary Exempt" maybe under Pay? Not specific amount, so omit. We must not include boilerplate like cookie/navigation/legal/EEO etc. There's none. We must not include duplicated lines. We must not create sections with filler like "commensurate with experience". Not present. Now produce HTML. Structure:

  About the role

  Company Summary text...

  Position Summary text...

  Responsibilities

  • Drive Microsoft 365 & Copilot Adoption – Lead adoption of Microsoft 365 Copilot across departments — running enablement sessions, building practical use cases, and helping staff fold AI into their daily work. Establish the habits and trust that make later automation possible.
  • Build Tool Fluency Across Departments – Teach departments to use SharePoint, Teams, OneDrive, Copilot, and Power BI effectively — file and collaboration hygiene, dashboards people read, and self-service reporting. Meet people where they are and raise the baseline.
  • Own the AI Relationship (as the platform matures) – Become the internal owner and driver for internal AI initiatives — managing the vendor partnership, content/knowledge governance, and alignment between AI capabilities and business needs.
  • Change Management & Champions – Cultivate department-level champions, deliver training, create documentation, and overcome resistance to new ways of working.
  • Process Discovery & Analysis – Embed within departments to observe and document current-state workflows, interview stakeholders to extract requirements, and identify high-value candidates for automation or AI augmentation. Map processes, quantify the cost of inefficiency (hours, error rates, rework), and prioritize by ROI and feasibility.
  • Solution Design, Build & Handoff – Design solutions and make the call on execution: build directly using Power Automate, Power Apps, Copilot Studio (agents), Dataverse, and Microsoft 365 Copilot. For work requiring elevated access or infrastructure-level changes, produce clear, complete specifications and hand off to IT admin resources. Design and build for long term sustainability and maintainability, not just for the demo.
  • Security & Data Governance Alignment – Ensure every solution and adoption effort adheres to least privilege access, data-handling, and the institution's governance standards. Apply Microsoft Purview sensitivity labels and DLP appropriately, account for Copilot oversharing risk, and partner with security and compliance on review and sign-off before anything touches member data or production.
  • Continuous Improvement & Tool Evaluation – Monitor solutions and adoption post-deployment, iterate based on feedback, and evaluate emerging AI and automation tools within the supported stack for fit, security posture, and value.
  • Other – Must be flexible and able to work unusual and variable hours/schedules, without supervision, including but not limited to holidays, evenings or weekends. Enforces compliance with all federal and state laws and regulations, including the Bank Secrecy Act (BSA), Patriot Act, and Office of Foreign Asset Controls (OFAC) requirements, and should request legal interpretation as necessary to identify compliance concerns. Adhere to applicable federal and state laws, regulations, and internal compliance with standard polices relevant to their roles and responsibilities. Perform other duties as assigned.

  Requirements

  • Bachelor’s degree in information technology or related field.
  • 5+ years in a technology role spanning both sides of this job: hands-on delivery of automation/low-code solutions, and user-facing enablement, training, or adoption work.
  • Demonstrated ability to drive tool adoption — running training, building enablement materials, and getting non-technical staff to change how they work.
  • Deep proficiency across the Microsoft 365 suite — Teams, SharePoint Online, Outlook, Power BI, and Microsoft 365 Copilot — sufficient to teach it, not just use it.
  • Proven hands-on build experience with the Power Platform (Power Automate, Power Apps, Copilot Studio).
  • Demonstrated ability to extract and document business requirements and translate them into working technical solutions — including producing implementation-ready specifications for handoff to admin resources when appropriate.
  • Working knowledge of data governance and security fundamentals — least-privilege access, sensitivity labeling, DLP, and the risks of AI oversharing (Microsoft Purview experience preferred).
  • Strong process-analysis skills: process mapping, current-/future-state documentation, and ROI quantification.
  • Excellent communication skills with the ability to translate fluently between business stakeholders and technical teams.
  • Self-directed and able to manage multiple cross-departmental initiatives simultaneously.

  Qualifications

  • Experience in financial services, banking, or a credit union, with awareness of GLBA and applicable regulatory requirements for member/customer data.
  • Familiarity with SharePoint information architecture and governance.
  • Experience with conversational AI / RAG knowledge platforms.
  • Familiarity with Power BI for reporting and lightweight data modeling.
  • Experience with Jira or a comparable work-management platform.
  • Microsoft certifications such as PL-100, PL-200, PL-400, PL-600, or MS-102.
  • Exposure to formal change-management or business-analysis methodology.

  Skills

  • Represents FPCU with professionalism and purpose, communicating with members through respectful and solution-focused verbal and written communications that support a member-focused experience.
  • Engages in effective interpersonal communication, diplomacy, and collaboration skills to develop productive relationships, encourage cooperation, and support positive member and employee experiences.
  • Maintains compliance with all applicable policies, demonstrating integrity, respect, and accountability while handling sensitive information and complying with FPCU policies, regulatory expectations, and confidentiality requirements.
  • Ability to apply logistical reasoning, analytical skills, and professional judgment to define and solve problems with effective and compliant solutions.
  • Adaptable, resilient, and comfortable navigating change in a fast-moving environment.
  • Embraces innovation and continuously seeks better ways to serve members and support teams.
  • Builder's instinct — bias toward shipping working solutions.
  • Teacher's patience — can meet non-technical staff where they are and make tools click.
  • Business acumen — understands the work behind the workflow and where the real cost lives.
  • Influence without authority — drives adoption across departments they don't manage.
  • Security-first mindset — treats governance as integral to the design of the solution.
  • Pragmatism — chooses the simplest tool that solves the problem and survives in production.

  Schedule

  Hours per Week: 40 hrs./week. Standard business hours with occasional flexibility required for deployment and training windows.

  Check we didn't miss any substantive info: Also there is "Physical Demands & Work Environment" includes sedentary work, sitting most of the time, may occasionally exert up to 50+ pounds of force, noise level professional moderate, reasonable accommodation. Should we include that? It's substantive but not under any of the allowed headings. The instruction says use headings for those specific sections only. It didn't say we cannot include other headings; but we should prefer a few substantive sections over many thin ones. Could we add a "Work Environment" section? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't list Work Environment. So we should not create a heading for it; we could fold that info into Schedule or maybe into About the role? But it's not about role. Could we put it under Schedule? Not appropriate. Could we drop it? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep that info. We need to place it somewhere without creating a new heading not in list? The instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive list? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, but likely they want only those headings. However we need to preserve all substantive info; we could incorporate physical demands into Schedule section as additional paragraph. That seems