Backend services
APIs, auth, background jobs, queues. FastAPI or Django if it's Python, plain net/http if it's Go. The parts that aren't the demo.
Independent engineer
Backends and data pipelines.
One person, not an agency.
I write Python and Go, run Postgres in production, and fix pipelines that quietly stopped working six months ago. Most jobs are four to twelve weeks, part-time, remote.
Taking on one new project this quarter.
What I do
Data pipelines
Ingestion, transforms, scheduling. Airflow or Dagster, dbt, Postgres, a bit of ClickHouse. Built so a schema change doesn't page anyone at 2am.
Inherited systems
The contractor left, deploys are manual, nobody remembers what the cron job does. I've untangled a few of these without rewriting everything.
How it works
-
01
One page of scope
Not a forty-page statement of work. What I'll build, what I won't touch, what it costs, when it's done. You can say no to it.
-
02
Two or three days a week
Part-time keeps the price sane and leaves you room to change your mind. I'm flexible on call times.
-
03
Handover is part of the job
Docs, runbooks, and a walkthrough before I stop. You should be able to get rid of me without losing the system.
Contact
Email me what's broken, or what you're trying to build. A paragraph is enough. If I'm not the right fit I'll say so and point you somewhere better.
hello@alverissystems.com
Usually a reply within a day.