• The Warren County PVA's Office is looking for a builder.
• Not a typical government job. Not a cog in a machine.
• We’re looking for one or two high-agency individuals who want to use modern tools—especially AI-assisted development—to automate real-world work, eliminate inefficiency, and build systems that make people’s jobs dramatically easier.
• This role is focused on a simple but powerful idea:
• If something takes 20–30 minutes today, we should be able to make it take 30 seconds.
• Our office still relies heavily on paper systems, manual data entry, and repetitive workflows. Your job will be to learn how things are currently done, then redesign and rebuild those processes using modern tools.
• This is hands-on, practical, real-world problem solving.
• Over time, this role will expand into deeper work involving:
• Property data systems
• Valuation processes
• GIS and mapping tools
• Analytical and decision-support systems
• Why This Role Matters
• Property valuation affects every taxpayer in the county.
• By improving systems and reducing inefficiencies, this role directly impacts:
• Fairness in taxation
• Speed and quality of public service
• Efficiency of government operations
• This is an opportunity to modernize how a local government office actually works.

• Learn existing workflows involving forms, property data, and office processes
• Identify repetitive, time-consuming tasks and inefficiencies
• Build tools and automations to streamline or eliminate those tasks
• Use AI-assisted development tools (such as Codex, Cursor, Replit, Lovable, etc.) to rapidly prototype and deploy solutions
• Create simple, practical systems that staff can actually use
• Iterate quickly—test, improve, and refine your tools based on real feedback

Work directly with the PVA to turn ideas into working systems

• We are not focused on credentials.
• We are looking for builders, tinkerers, and problem solvers.
• You might be a great fit if you:
• Have experimented with AI tools to solve real problems
• Like figuring things out without being told exactly how to do it
• Get satisfaction from making something faster, simpler, or better
• Are curious to the point that it’s hard to turn it off
• Backgrounds that might fit:
• Self-taught developers
• Early-career or junior engineers
• People exploring AI automation tools
• Technical hobbyists or “tinkerers”
• Math, engineering, or systems-minded thinkers
• The kind of person we’re looking for is:
• High agency
• Practical
• Resourceful
• Willing to get their hands dirty

The type who can figure out how to fix something, not just talk about it (If you know how to troubleshoot your own problems—whether that’s code, systems, or even changing your own oil—you’re probably the kind of person we’re looking for.)

• Use AI-assisted development tools (such as Codex, Cursor, Replit, Lovable, etc.)
• Required Experience:
• Have built things on your own (automation scripts, tools, apps, workflows, etc.)
• Have experimented with AI tools to solve real problems
• Required Education:
• You don’t need a degree.
• GED minimum. Higher education is welcome but not required.

• Health insurance
• Dental insurance
• Vision insurance
• Paid time off
• Flexible schedule
• Working Style
• Highly independent
• In-person collaboration when needed
• Focus on outcomes, not busywork
• You will be trusted to:
• Own problems
• Follow through
• Build real solutions
• Job Types: Full-time, Contract
• Pay: $38,963.00 - $40,911.00 per year
• Life insurance
• Professional development assistance
• Retirement plan
• Work Location: In person
• A Note to Applicants:
• If this role sounds exciting—even if you’re not sure you’re fully qualified—you should apply.
• We are not looking for perfect résumés.
• We are looking for people with drive, curiosity, and the ability to figure things out.
• Please include:
• Examples of anything you’ve built (projects, automations, experiments, etc.)
• Or describe something you’ve created and how you approached it
• If you don’t have much to show yet, write a few paragraphs about:
• Why this role interests you
• How you would start approaching the work
• What you think you could build or improve
• Application Question
• Describe a system, tool, or project you built (or would build) to solve a problem. What problem were you solving, and how did you approach it?