Process Engineer

Process Engineers bring deep expertise that gets called on when an engagement needs tooling, M365, low-code platforms, and rollout craft. They sit between the engagement layer (the VP defining the future state with the business) and the build layer, ensuring that what gets built is right, that the Process Engineering Team consistently chooses the best tool for the job, and that engagements requiring code-based development are cleanly scoped and handed off to Global AI Engineering. What You Own — Core Engagement Work Partner with G&A business teams and IT to analyze, document, and design current-state and future-state processes. Identify process improvement opportunities and quantify business value — hours saved, error reduction, cost avoidance. Translate future-state designs into developer-ready specifications — including process flows, decision logic, integration points, exception handling, evidence trails, and UI concepts where relevant. Design, build, test, and deploy solutions using Power Automate, Copilot Studio, SharePoint, Agent Builder, and other low-code and no-code platforms — selecting the right tool for each part of the work, recognizing that automation is one option but not always the right one. For engagements that require code-based development, partner with Global AI Engineering on the build while retaining ownership of the engagement, the design, the UAT, and the rollout. Integrate solutions with enterprise systems, APIs, and data sources within the Process Engineering Team's in-house build scope. Make informed tooling and architecture recommendations, advocating for simpler, lower-maintenance solutions when appropriate — with final engineering calls on code-based work belonging to Global AI Engineering. Monitor, maintain, and continuously improve deployed solutions. Own UAT, parallel runs, and cutover for assigned engagements — confirming the shipped solution fits the process and coordinating the people side of go-live. Own institutional memory across engagements you have worked on, carrying patterns and lessons forward. What You Own — Named Team-Wide Responsibility Tooling & Pattern Stewardship Maintain the Process Engineering Team's library of architectural patterns and keep a current view of what tools are in use and where. Serve as the named voice on tool selection when the Process Engineering Team is debating how to build something — your recommendation carries weight, with contested calls decided by the Director (with VP input). Lead tool evaluation when new platforms or approaches are being considered within the Process Engineering Team's in-house build scope. Ensure tooling decisions are documented and accessible to the full team and to Global AI Engineering partners. Where Your Expertise Gets Called In Engagements that are tooling-heavy — M365, Power Platform, low-code platforms, or when the question is "what is the right tool for this step." UAT and rollout design. Any engagement where build simplicity and maintainability need an advocate in the room. Decisions on whether work belongs in the Process Engineering Team's in-house low-code scope or whether it should be partnered to Global AI Engineering. What This Role Does Not Include Leading engagements or defining future-state at the function level (owned by the VP). Code-based development — production application code, custom services, AI agent architecture, platform evaluation. These are owned by Global AI Engineering. Final engineering architecture calls on partnered builds (owned by Global AI Engineering, with your input on tooling). Compliance gate review. How You Contribute to the Mission You are the bridge between vision and reality — ensuring the intelligent foundation we build tomorrow is constructed on specifications that are accurate, practical, and grounded in how Wynn's G&A