Enterprise Solutions Engineer

The Enterprise Solutions Engineer is a senior individual contributor responsible for translating enterprise architecture direction into working technical capabilities, reusable engineering patterns, and time-boxed proofs of concept. The position partners across Enterprise Architecture, IT Delivery, Cloud Operations, Data and Enterprise Platforms, Information Security, and business-aligned technology teams to improve how WPCU designs, builds, tests, deploys, integrates, and operates technology solutions.

This position requires broad technical fluency, learning agility, and strong engineering judgment; it does not require deep specialization in every platform, tool, or technology domain referenced in this description. The role works closely with Enterprise Architects to test architectural direction through practical implementation, identify constraints or delivery friction, and turn approved patterns into reusable assets that delivery teams can adopt.

The role does not serve as the long-term product owner, application development team, or operator of infrastructure and technology platforms. It proves feasibility, develops reusable enablement assets, accelerates difficult technical work, and transfers production ownership to the accountable delivery or operations team.

1. Enterprise Engineering Capabilities (30%) a) Design, build, and evolve reusable engineering capabilities that improve software delivery, with an initial emphasis on CI/CD, automated testing, deployment automation, release evidence, secure delivery controls, and environment promotion. b) Create shared templates, scripts, reference implementations, documentation, and adoption guidance that can be used across multiple technology delivery domains. c) Partner with platform owners so enterprise patterns use supported WPCU platforms without assuming ongoing operational ownership of those platforms. d) Measure adoption and outcomes, identify friction, and improve the engineering capabilities based on delivery-team feedback.
2. Technical Prototyping and Proofs of Concept (25%) a) Rapidly assess business and technology opportunities and build time-boxed proofs of concept to determine feasibility, constraints, security considerations, integration requirements, and likely production approach. b) Develop working code, integrations, deployment patterns, or technical demonstrations for use cases involving APIs, workflow automation, vendor platforms, cloud services, data movement, and emerging technologies. c) Document findings, decisions, assumptions, risks, costs, and recommended next steps in a form that enables leadership and delivery teams to make informed decisions. d) Establish explicit entry, exit, and handoff criteria so proofs of concept do not become unsupported production solutions.
3. Architecture Enablement and Reference Implementation (20%) a) Partner with Enterprise Architects to validate target-state patterns through working implementations rather than documentation alone. b) Create reference implementations for integration, API-centered design, application decomposition, telemetry, resiliency, security, and other enterprise standards. c) Provide hands-on technical guidance to delivery teams adopting approved patterns and help resolve difficult implementation issues. d) Identify where architecture standards are impractical, incomplete, or creating unnecessary delivery friction and recommend improvements.
4. Application Modernization and Delivery Acceleration (15%) a) Assess legacy and vendor-constrained deployment patterns and identify opportunities for full or partial automation, repeatability, auditability, and risk reduction. b) Help teams establish practical modernization approaches, including API enablement, modular decomposition, automated deployment, database change automation, and improved testability. c) Facilitate short technical spikes that reduce uncertainty before major investments or implementation commitments are made. d) Support knowledge transfer, pairing, and mentoring so delivery teams can independently sustain the resulting approach.
5. Governance, Risk, and Operational Readiness (10%) a) Embed security, risk, SSDLC, change control, and audit-evidence requirements into reusable engineering patterns wherever practical. b) Ensure experimental work uses appropriate controls, approved environments, representative non-production data, and clearly documented limitations. c) Coordinate with accountable teams to define production support, monitoring, service ownership, recovery, and lifecycle responsibilities before handoff. d) Ensure proper policies, procedures, risk mitigation activities and operating controls are followed. Report gaps in policies, procedures, operating controls and impacts to member experience to leadership to ensure that member impact and risk is mitigated.