What you'll own

• Delivery from scoping through go-live. You are the accountable owner for each installation from the Sales process through launch. You scope it, you see it live. Scope creep, new requests, and mid-implementation risk are yours to manage.
• Pre-sales technical discovery and scoping. Engage prospective customers during the Sales process to understand their operations, technical environment, and vendor landscape. Ask the questions that prevent surprises after signature. Own the Statement of Work with enough precision that engineering can build against it without rework.
• Kickoff and technical foundation. Run the initial customer kickoff and stand up access, network paths, and data flow before implementation begins: system credentials, VPN and firewall coordination, SSO configuration, and third-party vendor connectivity.
• Driving blocked integrations. When a vendor is uncooperative or absent, documentation is thin, or no clean path exists, you find or build the path. You read the code and the data well enough to diagnose where and why an integration failed, inspect a county's data before building against it, and validate assumptions against the customer's actual systems rather than their description of them.
• Stakeholder translation. Hold a technical line with county IT or a CISO and explain a timeline to a non-technical assessor or elected official in the same meeting.
• Expectation and risk management. Set clear expectations on time, effort, and cost for custom requests. Surface technical risk early, especially where a customer's existing systems or vendor relationships affect the integration path.
• Launch coordination. Run kickoff, training, testing, and go-live with the customer. You are the single point of contact for third-party vendors on each engagement.
• Product feedback. Maintain expert knowledge of the product suite and feed pre-sales and implementation insight back as concrete enhancement proposals and new product opportunities.

What we need to see

• Delivery ownership through ambiguity. A demonstrated track record of being the last line of defense on a technical delivery with an external customer: no PM, no QA, no DevOps net, an uncooperative or absent vendor, thin documentation, and you still drove the technical path to resolution yourself. We will ask you to walk through one in detail. Scoping-only, pre-sales-only, coordinator, and handoff-and-advise backgrounds do not clear this bar.
• Pre-sales scoping ownership. You have been in the room before a contract signed, run discovery, and owned scope that got committed. Answering an account manager's questions case by case does not clear this bar.
• Python and SQL you can read and write. You use both to analyze datasets, build and validate ETL, check data mappings, and sanity-check integration assumptions. You reason about ETL, APIs, SFTP and file-based exchange, data mapping, and on-prem versus cloud environments well enough to scope accurately and earn a county's trust. You do not need to deploy code, own CI, or run infrastructure; Implementation Engineering owns that.
• Legacy and on-premise fluency. Working experience with environments where there is no API, documentation is thin, access is negotiated with a vendor who didn't design for you, and the data arrives as a nightly file. Cloud-to-cloud API integration is a real skill, but it isn't this one.
• AI as leverage, not as a crutch. You use AI tools daily and can point to workflows you've rebuilt with them. You also understand the logic of what you ship and can reason about it without a model in the loop. We will ask you to.
• Fast ramp. You can carry a hard launch within your first quarter. We work with you, but there is no six-month runway.
• Earn-it-here temperament. High ownership, low scaffolding, figure it out with support. Seniority earned elsewhere is real growth signal, but it doesn't pre-place anyone here. The right person is hungry to earn the seat and allergic to being handed a playbook.
• Travel. Roughly 10 days per month on-site at county offices across the United States. Core to the job, not occasional.

Preferred

• Experience delivering technology to local government, property tax administration, or other public-sector customers.
• Familiarity with CAMA systems, county recorder systems, large ERP platforms, or other domain-specific government software.
• Experience on the implementation or conversion side of a government software vendor.
• A software engineering background with production experience shipping application code.

Not a fit

To save everyone time, this role is likely not right if your primary current work is:

• Pre-sales or solutions engineering where another team owns delivery after signature.
• Integration work that has only ever been REST APIs, OAuth, and cloud-to-cloud connectors.
• Platform configuration or low-code tooling without underlying code.
• Scripting-only work (PowerShell or bash without application development).
• Coordinating engineers rather than building alongside them (Technical Program Manager, Technical Product Manager, or similar).

This applies even when the domain and titles look adjacent. We judge on what you've actually done, not on the label.