Enterprise Solutions Architect
Reports to: VP of TechnologySupervises: NoneJob Site: Evergreen Goodwill Administration Office, Hybrid 3 days required in officeBand: $145,000 – $155,000
Position Summary
Translates technology strategy into enterprise architecture and technical standards. Accountable for the coherence and long-term consequences of architectural decisions within the direction established with the VP of Technology.
Sets technical planning, architecture review, and release coordination practices across engineering. Advises leadership on sequencing, dependencies, capacity constraints, and technical risk.
Evergreen Goodwill is seeking an Enterprise Solutions Architect. This is an internal-facing, hands-on architecture role — not a pre-sales or customer-facing position.
Technology direction is set with the VP of Technology. Your work is to turn that direction into an architecture the organization can actually build against: the target state, the integration patterns, the standards, and the sequence to get there.
We are in the middle of a substantial platform transformation: automating sort and warehouse operations, migrating identity and productivity platforms, integrating finance systems, and building software in-house where commercial products do not fit how we operate. These initiatives share dependencies. A decision made in identity constrains what is possible in the warehouse; a decision made in finance integration constrains reporting.
You are accountable for making those decisions compose — and for their consequences three years out, not only at deployment. You will write the architecture and the standards down so they outlast any individual, including you. You will be senior enough to say no with a reason, and close enough to the work to be credible when you do.
You will also set how engineering plans and ships: technical planning practice, architecture review, the DevOps pipeline, and release coordination — the air traffic control function for what reaches production and when, across teams running concurrent, interdependent initiatives. Where that work surfaces sequencing conflicts, capacity constraints, or technical risk, you bring it to leadership early enough to act on.
Key Responsibilities
Architecture and technical direction
Rationalize and articulate the target-state architecture across infrastructure, applications, integration, and data — and the sequenced path from current state to it
Develop and document platform selection and exit recommendations against explicit criteria — total cost, integration burden, exit cost, security posture, and organizational fit — and own the resulting architecture once the direction is set
Define integration patterns and interface contracts between systems so teams are not negotiating them case by case
Maintain architectural decision records stating what was decided, what alternatives were considered, and why — with enough reasoning that a future engineer can tell whether the decision still applies
Build security, privacy, and compliance requirements into the architecture — PCI scope, data handling, retention, and the access model — rather than bolting them on after a system is built
Engineering standards and practice
Set and own development, deployment, and lifecycle standards across all three engineering families: source control, environments, release process, configuration management, testing, and operational handoff
Define what "production-ready" means for internally built software, and hold work to it
Build the reusable patterns, templates, and reference implementations that let teams move quickly inside the standards rather than around them
Quality, DevOps, and change management
Own the quality bar for engineering work across the organization: what gets reviewed, what "done" means, and what is allowed to reach production
Own the build and deployment pipeline — source control practice, branching strategy, automated testing, environment promotion, and release…