Sr. Solutions Engineer

Sr. Solutions EngineerReports to: Director, TechnologySupervises: NoneLocation: Evergreen Goodwill Administration Office, Hybrid 3 days required in officeSalary Range: $90,000 - $100,000Position SummaryEvergreen Goodwill is seeking a Sr. Solutions Engineer to own a domain of the systems our organization runs on - the platforms, integrations, and automations that keep a 2,000-person nonprofit operating across 26 locations.This is an internal-facing engineering role, not a pre-sales position. You will take ownership of a set of business-critical systems: how they are designed, how they connect to everything else, and how they behave when something breaks.We are modernizing much of our technology estate. You will be designing and building replacements, not maintaining a finished stack - and you will own the standards for how that work gets done in your domain.This is a senior individual contributor role with real decision authority. You will work directly with the business areas you support, and you will be the person who decides how the systems in your domain fit together.Where your authority sits. You decide within the systems you own. Standards that span domains - how your systems talk to everyone else's, how things get deployed and changed - sit with our Enterprise Solutions Architect, and you help shape them. Inside your domain, the calls are yours.Key ResponsibilitiesDomain ownership

Own the architecture and forward plan for a domain of business-critical systemsOwn the integrations between your domain and the rest of the enterprise estate - finance, workforce, inventory, and reportingOwn configuration standards, release practice, and operational handoff for your domain, working within enterprise architecture standards

Build and integration

Design, build, and deploy integrations, automations, and configuration across the domainOwn production codebases where the domain includes internally built softwareBuild AI into the systems you own where it earns its place - classification, extraction, retrieval, and language-model services wired into real workflows, with evaluation against the task rather than adoption by defaultTier 3 diagnosis for the systems you own - the escalation point, not an escalation path

Reliability and operations

Own reliability and service levels for the systems in your domain, including monitoring, alerting, and incident responseDesign the operational handoff so systems support teams can run what you buildParticipate in change and maintenance windows, including business-sensitive timing

Stakeholder partnership

Partner directly with the business areas you support. Translate operational need into system capability without a translator in betweenSay no with a reason and an alternative when a request would compromise reliability or integrityManage vendor relationships for platforms in the domain, including evaluation and selection input

Multiplication

Raise the capability of the solution engineering team through review, standards, and teachingMentor less experienced engineers, including on the domain you ownDocument your work so someone else can carry it

Job-Specific Qualifications

8+ years in solution engineering, systems integration, business systems, or software engineeringDemonstrated ownership of a platform or system domain - the architecture, the standards, and the consequences when it breaks. Not contribution to someone else's domain. This is the threshold requirement and we will probe it directly: what you owned, what you decided, what you were accountable forEvidence you set technical practice that other engineers followed - configuration standards, integration patterns, release discipline, or review practice adopted by people who did not report to youCurrent hands-on development. You should be able to read a codebase, write production code, and be credible in a technical design review. Configuration-only backgrounds will not clear this barOwnership of a production codebase or internally built service, including what happened when it failedProduction experience building with AI, not just using it. Large language models or classification models integrated into a working system - prompt and context design, retrieval patterns, structured output, and evaluation. You should be able to explain how you measured whether the model was actually right, and where the approach broke downJudgment about when AI is the wrong tool. We are looking for someone who has shipped it and also killed itDeep systems integration experience: API design, interface contracts, message and event patterns, and the failure modes of eachExperience delivering work that required another department to change how it operatesExperience owning reliability for an operationally critical system, including on-call and incident responseClear written communication, and the ability to explain a technical constraint to a non-technical audience without hand-wavingExperience in an environment where systems are being replaced rather than maintained

Other / Preferred Qualifications

Experience in an environment with physical operations and frontline staff - retail, logistics, warehousing, manufacturing, or similarERP, finance, workforce management, or point-of-sale system experiencePayment processing or PCI-scoped system experienceOperational or industrial automation experienceExperience with internally built software alongside commercial platformsAgentic or tool-using AI systems in production - orchestration, guardrails, human-in-the-loop designModel selection and cost/performance tradeoff analysis across providersComputer vision or automated classification applied to physical operationsNonprofit, public sector, or mission-driven experienceExperience mentoring less experienced engineers

What we are deliberately not asking for

People management experience. No direct reports. This is a senior individual contributor seat on a technical ladder that continues above itSpecific vendor certifications. Platforms in our current environment are examples, not requirementsPre-sales or customer-facing solutions engineering. Different discipline; this role is entirely internal

Minimum EducationBachelor's degree in computer science, information systems, engineering, or a related field - or equivalent professional experience.Minimum Years of Relevant Experience8+ years.