Enterprise Solutions Engineer

Wright-Patt Credit Union•Beavercreek, OH
•$123,510 - $185,349

About The Position

The Enterprise Solutions Engineer is a senior individual contributor who translates enterprise architecture direction into working technical capabilities, reusable engineering patterns, and time-boxed proofs of concept. The role 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. It requires broad technical fluency, learning agility, and sound engineering judgment, but not deep specialization in every referenced platform, tool, or technology domain. Working closely with Enterprise Architects, the engineer tests architectural direction through practical implementation, identifies constraints and delivery friction, and turns approved patterns into reusable assets for delivery teams. The role proves feasibility, develops reusable enablement assets, accelerates difficult technical work, and transfers production ownership to accountable delivery or operations teams. It does not serve as the long-term product owner, application development team, or operator of infrastructure and technology platforms. The position’s work includes developing shared engineering capabilities; building time-boxed proofs of concept; validating architecture patterns through reference implementations; accelerating application modernization and delivery; and embedding governance, risk, security, and operational-readiness practices. It also includes documenting findings and handoff criteria, supporting teams adopting approved patterns, and coordinating production support and ownership responsibilities before handoff.

Responsibilities

  • Design, build, and evolve reusable engineering capabilities, initially emphasizing CI/CD, automated testing, deployment automation, release evidence, secure delivery controls, and environment promotion.
  • Create shared templates, scripts, reference implementations, documentation, and adoption guidance for use across technology delivery domains.
  • Partner with platform owners to use supported WPCU platforms without assuming ongoing operational ownership.
  • Measure adoption and outcomes, identify delivery friction, and improve engineering capabilities based on delivery-team feedback.
  • Assess business and technology opportunities and build time-boxed proofs of concept to evaluate feasibility, constraints, security considerations, integration requirements, and likely production approaches.
  • Develop working code, integrations, deployment patterns, and technical demonstrations for use cases involving APIs, workflow automation, vendor platforms, cloud services, data movement, and emerging technologies.
  • Document proof-of-concept findings, decisions, assumptions, risks, costs, and recommended next steps for leadership and delivery teams.
  • Establish explicit entry, exit, and handoff criteria to prevent proofs of concept from becoming unsupported production solutions.
  • Partner with Enterprise Architects to validate target-state patterns through working implementations.
  • Create reference implementations for integration, API-centered design, application decomposition, telemetry, resiliency, security, and other enterprise standards.
  • Provide hands-on technical guidance to delivery teams adopting approved patterns and help resolve difficult implementation issues.
  • Identify impractical or incomplete architecture standards and standards that create unnecessary delivery friction; recommend improvements.
  • Assess legacy and vendor-constrained deployment patterns and identify opportunities for automation, repeatability, auditability, and risk reduction.
  • Help teams establish modernization approaches, including API enablement, modular decomposition, automated deployment, database change automation, and improved testability.
  • Facilitate short technical spikes to reduce uncertainty before major investments or implementation commitments.
  • Support knowledge transfer, pairing, and mentoring so delivery teams can sustain resulting approaches independently.
  • Embed security, risk, SSDLC, change control, and audit-evidence requirements into reusable engineering patterns where practical.
  • Ensure experimental work uses appropriate controls, approved environments, representative non-production data, and clearly documented limitations.
  • Coordinate with accountable teams to define production support, monitoring, service ownership, recovery, and lifecycle responsibilities before handoff.
  • Ensure applicable policies, procedures, risk mitigation activities, and operating controls are followed.
  • Report gaps in policies, procedures, and operating controls, as well as impacts to member experience, to leadership so member impact and risk can be mitigated.
© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service