Frederick Fox

<h1>Forward Deployed Software Engineer</h1>
<p>County assessors lose time and revenue to homestead paperwork that should already be settled. You will sit with those teams, turn messy exemption workflows into working software, and leave them with faster decisions, cleaner records, and fewer missed exemptions. This role exists to make the product true in the field—not just plausible in a demo.</p>
<h2>Performance Objectives</h2>
<ul>
<li>Embed with assessment offices and ship production changes that cut homestead application and removal cycle time within the first two quarters.</li>
<li>Diagnose where compliance breaks—unclaimed exemptions, stale records, manual handoffs—and close those gaps with measurable lifts in accuracy and recovered revenue.</li>
<li>Translate assessor workflows into scoped product work, then deliver the features, integrations, and data fixes that make those workflows run end to end.</li>
<li>Stand up reliable data pipelines and validations so exemption status is auditable from application through removal.</li>
<li>Own customer deployments: configure, integrate, train power users, and leave a stable operating rhythm rather than a pile of open tickets.</li>
<li>Feed field evidence back into the roadmap so the next release prevents the problems you just solved.</li>
<li>Keep sensitive property and exemption data handled with the care public records demand—correct, traceable, and minimally exposed.</li>
</ul>
<h2>Environment &amp; Resources</h2>
<p>You will work inside a small early-stage product team, reporting to engineering leadership and paired daily with product and customer success. Expect direct access to assessor users, a modern web stack, and the authority to change both code and process. Travel to customer sites is part of the job; between visits you build, review, and support what you deployed. Budget is lean and decisions are fast—scope is set by outcomes, not ceremony.</p>
<h2>Essential Qualifications</h2>
<ul>
<li>Shipped production software used by non-engineers, including at least one system that replaced a manual operational workflow.</li>
<li>Comfort debugging data, APIs, and UI in the same week, and writing clear fixes under real deadlines.</li>
<li>Proven ability to sit with domain experts, map their process, and turn that map into a working release.</li>
<li>Experience integrating with existing systems of record and leaving an audit trail others can trust.</li>
<li>Judgment with sensitive data: you default to least access, explainability, and reversible changes.</li>
<li>Clear writing and calm presence with public-sector stakeholders who are busy and skeptical of software promises.</li>
</ul>
<h2>Role Selling Points</h2>
<ul>
<li>Your code changes how a county protects revenue and treats homeowners—impact you can see in their backlog, not a vanity metric.</li>
<li>Forward-deployed means you own the problem from the counter to production, not a ticket queue one step removed.</li>
<li>Early team: your field notes become the product, and your name is on the systems assessors actually run.</li>
<li>GovTech with a narrow, serious mission—homestead administration done accurately, efficiently, and transparently.</li>
</ul>
<h2>Call to Action</h2>
<p>If you want to build software beside the people who use it, and you can show work that made an operation faster and more correct, apply with a short note on a system you deployed and the outcome it changed.</p>

**********************************
Forward Deployed Software Engineer
**********************************

County assessors lose time and revenue to homestead paperwork
that should already be settled. You will sit with those teams,
turn messy exemption workflows into working software, and leave
them with faster decisions, cleaner records, and fewer missed
exemptions. This role exists to make the product true in the
field—not just plausible in a demo.

----------------------
Performance Objectives
----------------------

* Embed with assessment offices and ship production changes that
cut homestead application and removal cycle time within the first
two quarters.
* Diagnose where compliance breaks—unclaimed exemptions, stale
records, manual handoffs—and close those gaps with measurable
lifts in accuracy and recovered revenue.
* Translate assessor workflows into scoped product work, then
deliver the features, integrations, and data fixes that make
those workflows run end to end.
* Stand up reliable data pipelines and validations so exemption
status is auditable from application through removal.
* Own customer deployments: configure, integrate, train power
users, and leave a stable operating rhythm rather than a pile of
open tickets.
* Feed field evidence back into the roadmap so the next release
prevents the problems you just solved.
* Keep sensitive property and exemption data handled with the
care public records demand—correct, traceable, and minimally
exposed.

---------------------------
Environment & Resources
---------------------------

You will work inside a small early-stage product team, reporting
to engineering leadership and paired daily with product and
customer success. Expect direct access to assessor users, a
modern web stack, and the authority to change both code and
process. Travel to customer sites is part of the job; between
visits you build, review, and support what you deployed. Budget
is lean and decisions are fast—scope is set by outcomes, not
ceremony.

------------------------
Essential Qualifications
------------------------

* Shipped production software used by non-engineers, including at
least one system that replaced a manual operational workflow.
* Comfort debugging data, APIs, and UI in the same week, and
writing clear fixes under real deadlines.
* Proven ability to sit with domain experts, map their process,
and turn that map into a working release.
* Experience integrating with existing systems of record and
leaving an audit trail others can trust.
* Judgment with sensitive data: you default to least access,
explainability, and reversible changes.
* Clear writing and calm presence with public-sector stakeholders
who are busy and skeptical of software promises.

-------------------
Role Selling Points
-------------------

* Your code changes how a county protects revenue and treats
homeowners—impact you can see in their backlog, not a vanity
metric.
* Forward-deployed means you own the problem from the counter to
production, not a ticket queue one step removed.
* Early team: your field notes become the product, and your name
is on the systems assessors actually run.
* GovTech with a narrow, serious mission—homestead administration
done accurately, efficiently, and transparently.

--------------
Call to Action
--------------

If you want to build software beside the people who use it, and
you can show work that made an operation faster and more correct,
apply with a short note on a system you deployed and the outcome
it changed.

Data Implementation Manager

About the role

Not the right role?