Description review
Location: Manteca, CA, USA
Location: Manteca, CA, USA · Remote · back to the listing
HR standards
28/100
poor
Title ↔ description
47/100
poor
Reads as
Backend Engineer
97% confident
What this role officially is
software developer — ESCO, the EU occupation classification
Software developers implement or program all kinds of software systems based on specifications and designs by using programming languages, tools, and platforms.
Also known as: application developer, application programmer, solutions developer, programmer, software specialist, application software developer
How others title the same work
Large employers
- Software Engineer - OpenStack Canonical
- C, Golang Software Engineer working on dqlite, a Raft extension for SQLite Canonical Ltd.
- Containerization & Virtualisation Engineer Canonical Ltd.
- Go (Golang) Software Engineer, Developer Tooling and Containers Canonical Ltd.
- Golang Engineer Canonical Ltd.
Startups
- Anterior (Sequoia-backed, Series B) | Senior Member of Technical Staff | On-Site (New York, NY) | Full Time | $230,000–$300,000 + equity Anterior (Sequoia-backed, Series B)
- BitPay | Senior Backend Software Developer | Atlanta, GA | REMOTE (US) | BitPay
- Distributed Systems Engineer Beam
- Software Engineer, Platform Beam
- Blaine, WA | CaseLight Systems Inc. (CSI) | Solo Founder | Remote (US Only) | Founding Systems Engineer | FULL EQUITY (30% Stake) Blaine, WA
What the listing never says
- No section describes what the person would actually do. Scope clarity
- No pay range published. Candidates cannot tell whether applying is worth their time. Pay transparency
The listing, marked up
Remote: Yes (required)
Willing to relocate: No
Technologies: Python, Java, SQL, AWS, Azure, Kubernetes, Terraform, PostgreSQL, GitHub Actions, Common Lisp
Résumé/CV: https://sinistercode.com/public/donnie/resume
Email: macnod [at] gmail [dot] com
Senior software engineer, 20+ years1 . Available immediately; US Pacific hours. Looking for a full-time remote role designing backend or platform systems.
I write programs that write programs. Data UI is a compiler I'm building in Common Lisp. It already compiles a 57-line model into PostgreSQL, REST, a minimal React UI, row-level RBAC, and Kubernetes+TLS, and deploys it. The same application is roughly 20,000 lines written by hand. In my tests an agent can generate large parts of it, but not the application. It needs a senior directing it the whole way. The 57-line model is what gets reviewed instead. Live demos: https://data-ui.com
Recently, Azure Government (FedRAMP IL5): commercial Elasticsearch was not allowed, so I replaced it with self-hosted Elasticsearch inside the VNet. Subnet and AKS in Terraform; Elasticsearch from Terraform-managed Helm charts.
I run several models from different providers, including local ones, in one Emacs instance. Any of them can enlist another against the same live state. One shape: a model drafts a plan, enlists a second to draft its own, then reconciles the two. They implement against the live Lisp image, and they can patch the Emacs instance they are running in, so a fix to the harness takes effect on the next prompt. In the usual setup the model can't reach the program running it. Only I commit.
Portfolio: https://sinistercode.com/public/donnie
GitHub: https://github.com/macnod
Willing to relocate: No
Technologies: Python, Java, SQL, AWS, Azure, Kubernetes, Terraform, PostgreSQL, GitHub Actions, Common Lisp
Résumé/CV: https://sinistercode.com/public/donnie/resume
Email: macnod [at] gmail [dot] com
Senior software engineer, 20+ years1 . Available immediately; US Pacific hours. Looking for a full-time remote role designing backend or platform systems.
I write programs that write programs. Data UI is a compiler I'm building in Common Lisp. It already compiles a 57-line model into PostgreSQL, REST, a minimal React UI, row-level RBAC, and Kubernetes+TLS, and deploys it. The same application is roughly 20,000 lines written by hand. In my tests an agent can generate large parts of it, but not the application. It needs a senior directing it the whole way. The 57-line model is what gets reviewed instead. Live demos: https://data-ui.com
Recently, Azure Government (FedRAMP IL5): commercial Elasticsearch was not allowed, so I replaced it with self-hosted Elasticsearch inside the VNet. Subnet and AKS in Terraform; Elasticsearch from Terraform-managed Helm charts.
I run several models from different providers, including local ones, in one Emacs instance. Any of them can enlist another against the same live state. One shape: a model drafts a plan, enlists a second to draft its own, then reconciles the two. They implement against the live Lisp image, and they can patch the Emacs instance they are running in, so a fix to the harness takes effect on the next prompt. In the usual setup the model can't reach the program running it. Only I commit.
Portfolio: https://sinistercode.com/public/donnie
GitHub: https://github.com/macnod