Customer Engineer

## The Role

We're hiring a **Customer Engineer** to be the accountable owner of each customer installation, from the sales conversation through go-live. This is the most technical seat in our go-to-market org. You sit between a county's real operations and our product, scope the work with precision, and then stay on the hook until an assessor's office is running on Just Appraised instead of their old manual process. It is not a pre-sales seat, a program-management role, or a backup engineering chair. When there is no clean path to a working install, you find or build one.

## What You'll Do

- Own each installation end to end: partner with Sales on discovery, architect the right solution from our product suite, write a precise Statement of Work, and carry it through implementation, UAT, and launch
- Do technical discovery before the contract is signed: understand how a county actually works and what their systems will and won't let you do
- Write the Python and SQL customers depend on: analyze county datasets, build and validate ETL, check data mappings against the real tax roll and deed records
- Navigate integration environments where there's no API, the documentation is thin, or the incumbent vendor won't help, and still land the install
- Translate the technical reality to non-technical county officials and elected leaders so everyone trusts what's being built

## What We're Looking For

- A track record of being the last line of defense on a technical delivery to an external customer, not a hand-off-and-advise role
- Hands-on Python and SQL: you reach for both to analyze data, build and validate ETL, and check mappings, not just to read someone else's code
- Comfort in legacy environments with no API and thin docs, where part of the job is figuring out a path that isn't written down
- You can carry a hard launch inside your first quarter and keep a county calm while you do it
- Willingness to travel roughly 10 days a month to county offices across the US

## Strong Advantages

Nice-to-haves, not strict requirements.

- Time spent in or around local government, property tax, assessment, or another heavily regulated public-sector workflow
- Experience standing up data integrations against systems that were never meant to be integrated
- You've owned a Statement of Work that someone then held you to

## Why This Role Is Special

The work is concrete in a way most software jobs aren't. A county's deeds or reappraisal process goes from weeks of manual data entry to software that does it in an afternoon, and you're the person who made that true for them. You own the whole arc, so the win is unambiguous and it's yours.

## Location

Remote in the US, with regular on-site time at county offices (roughly 10 days a month).

## Next Steps

Tell us about one delivery you owned where the path wasn't obvious and you got it to go-live anyway. One real story beats a tidy resume here.