Bakersfield, California · Software architect

Software for work that has to be done carefully.

I'm Nathan Mayer, a software architect and independent builder. My work has included artificial-lift analytics at Theta, payment systems at Amazon, and grant and healthcare claims workflows through Linean.

Today I run KitFox Labs, my independent software practice.

A working perspective

Understand the process.
Respect the records.
Make the next step clear.

I'm interested in useful Central Valley projects, especially where people work around disconnected data, old software or rules that are hard to get right.

Let's connect

01 / Selected experience

A body of practical work.

Equipment, payments, applications and claims. Different domains, with a shared need for careful software and understandable records.

Past employment

Theta Oilfield Services, Inc.

Industrial & artificial-lift analytics

I built pump-analysis and telemetry software at Theta, progressing from Full Stack Software Developer to lead development roles in Artificial Lift, XSPOC and Data Science.

My starting question: how can data help someone understand what needs attention?

Past employment

Amazon

Payment systems

As a Software Development Engineer, I worked on payment systems at Amazon in August 2020–May 2021 and February 2022–September 2025.

My starting question: what happens to the record when a process fails or needs a person to intervene?

Completed engagement

California state agency · through Linean

Public-agency grant workflows

I contributed to grant-management software for a California state agency through Linean.

My starting question: can people see what needs a decision and what happened to an application?

Grant workflow notes
Completed engagement

School-agency work · through Linean

Healthcare claims workflows

I worked on school-agency healthcare claims workflows through Linean.

My starting question: who can act on a record, and how will someone explain a change later?

Claims workflow notes

02 / Career

How I got here.

Software engineering since 2016. KitFox is my current practice; the roles below are my professional history.

  1. Aug 2025–presentCurrent

    KitFox Labs

    Principal Engineer

    Self-employed · Bakersfield

    I run my independent software practice: operational software, existing-system reviews and bounded experiments.

  2. Oct 2025–Sep 2026

    Linean

    Principal Engineer / Managing Consultant

    Bakersfield

    I worked on public-agency grant software and school-agency healthcare claims workflows. My engagement is complete.

  3. Feb 2022–Sep 2025

    Amazon

    Software Development Engineer

    Bakersfield

    I worked on connecting legacy payment workflows to a payables platform and designed approval workflows for manual transactions.

  4. Jun 2021–Feb 2022

    Pumpoff Software

    Owner

    I integrated legacy artificial-lift software with an optimization platform.

  5. Aug 2020–May 2021

    Amazon

    Software Development Engineer

    Bakersfield

    I worked on accounts-payable software and redesigned a reporting service.

  6. Jan 2016–Aug 2020

    Theta Oilfield Services, Inc.

    Bakersfield

    1. Jan–Oct 2016

      Full Stack Software Developer

      I built multiphase-flow analysis for electric submersible pumps.

    2. Oct 2016–Sep 2017

      Lead Software Developer – Artificial Lift

      I led development of gas-lift and electric-submersible-pump analysis software.

    3. Sep 2017–Oct 2018

      Lead Software Developer – XSPOC

      I led development of XSPOC well-monitoring software and designed tools to analyze artificial-lift equipment failures.

    4. Nov 2018–Aug 2020

      Lead Software Developer – Data Science

      I developed anomaly-detection and classification software for pump telemetry and worked on exception-based monitoring in XSPOC.

03 / Exploring

Questions I'm working on.

Research and experiments, alongside my established software work.

Research / prototype

Water records that people can reconcile.

I've explored double-entry water-accounting prototypes. I'm interested in water records, reconciliation and reporting, and in understanding the accounting work with the people responsible for it.

Where do records disagree, and what does it take to resolve the difference?

Talk water workflows
Exploration

Testing AI on one workflow task.

I want to test whether AI can help people gather evidence or explain an exception. A useful test has authorized examples, a comparison with the current process and human review.

Does it help someone make a better decision, and can they check its work?

Compare notes on AI

04 / Working together

Where a conversation can start.

A software problem, a local project, a technical review or an opportunity to contribute. For paid work through KitFox, these are three bounded starting points.

These are proposed first scopes. We agree scope, access, acceptance criteria and schedule before starting. Larger implementations are scoped separately.

Review an existing system

For a business owner, operations director or technical lead.

A rewrite, migration or hosting decision is unclear because the system is expensive, fragile or hard to understand.

What you get
A short decision memo: current risks, options, tradeoffs and a phased next step.
First scope
One application or hosting stack, reviewed with read-only access.
Timeframe
One working week from agreed kickoff and access.
Describe the system and your decision

Improve one workflow

For an agency or program manager, billing lead or operations team.

People re-enter information, approvals stall or ownership of the next step is unclear.

What you get
A working first increment, a process map, acceptance checks and handoff notes.
First scope
One workflow and one first increment, with roles and acceptance criteria agreed before implementation.
Timeframe
Three working weeks from agreed kickoff and access.
Share the steps and where work gets stuck

Test one useful AI feature

For an operations or technical lead with an existing task or exception queue.

People spend time gathering evidence or explaining exceptions; the value of AI is uncertain.

What you get
A small prototype, test findings and a continue/change/stop recommendation.
First scope
One feature tested on authorized examples, with human review and comparison to the current process.
Timeframe
Two working weeks from agreed kickoff and authorized examples.
Share the task, process and permitted examples

05 / Connect

What's the work in front of you?

Have a software problem, a local project or a place where a technical perspective would help? Email me.

[email protected]

A useful introduction

Tell me what you're trying to do, how the work happens today and which decision or change you need help with. A few sentences are enough to start.

Open the 30-minute Calendly link

Prefer email? The address above is a direct alternative.

Nathan on LinkedIn