Job Opportunities API

The Public Ledger of Openings

← Back to the ledger

Senior Solutions Architect, Government Partnerships

Propel
CompanyPropel
CategorySales
LocationUSA
RemoteRemote
EmploymentNot stated
LevelLead
SalaryUSD 160k–190k
Posted9 Apr 2026
Last verified10 Aug 2026
SourceEmployer ATS (ashby)
Applications are handled by the employer, not by us.Apply on the employer's site →
Description
About Us Propel is on a mission to empower low-income Americans by simplifying access to government benefits with modern technology. We're a passionate team of 100 Propellers - all working to help our users get through the month, every month. About the Role We're looking for a Solutions Architect to bridge Propel's Government Partnerships team and our Product & Engineering organization - translating state partners' needs into product strategy, and then owning the delivery of that work with states. This role has the opportunity to shape the way our product evolves with deeper government partnerships and increase the value we’re able to deliver to both users and government partners. This is a hands-on IC role. You'll be the person writing the scoping doc, building the dashboard, sitting in the state meeting, configuring the campaign, and running the evaluation. You own both strategy and execution end to end. Over time, as this work scales, the role has potential to grow into a leadership position — but today we need someone who is excited about the execution. You'll work across the state partnership funnel, from early relationship-building through campaign delivery. You should be the kind of person who can walk into a meeting with a state SNAP agency, understand their operational pain points around payment error rates or portal access, walk out with a concrete plan that maps to Propel's product roadmap — and then go execute it. The role reports into our Government Partnerships team, with a dotted line to Product. Here's how you'll impact the company: - Be the product voice in state conversations. Prepare materials, present Propel's capabilities, and field technical questions from state partners directly. Translate what you learn into structured requirements and recommendations for product and engineering. - Own state campaign delivery end to end. - Define what Propel will deliver for each state engagement, write the scope-of-work, set up campaign infrastructure, monitor execution, run the evaluation, and fix what breaks. - Lean into AI-enablement to create more leverage for our partnerships work with less engineering support. - Make hands-on tradeoff decisions about when a state's needs warrant new product investment vs. existing capabilities — and when it's configuration work, do it yourself. - Feed the case management product roadmap. Synthesize patterns across engagements to surface common needs and platform gaps. Bring specific, evidence-based recommendations to PMs — not just "states want X," but "here's the pattern across three states, here's what a platform-level solution looks like, and here's the data." You Might Be a Great Fit If You Have - 5+ years bridging product/technical teams and external partners — solutions architecture, implementation/delivery leadership, technical program management, or product management in a B2G context. You should have direct experience working in or selling to state SNAP or Medicaid agencies. - Technical background – you’re comfortable getting in the weeds on how our tech stack operates to tackle questions around how we should integrate with state partners. You are comfortable reading API docs, translating technical documents for non-technical stakeholders and doing a first-draft estimate of complexity and scope for new tasks. - Familiarity with public benefits administration — SNAP, Medicaid, EBT, or adjacent programs. You understand (or can quickly learn) how state agencies work, what their incentives are, and why things like payment error rates and redetermination processes matter - The ability to operate across altitudes — presenting to a state CIO on Monday, speccing a campaign config on Tuesday, analyzing pilot results on Wednesday, drafting a SOW on Thursday - Strong product instincts — you can tell the difference between a state request that should become a platform feature and one that should stay a one-off.