Software engineering and AI consulting
I'm Adam Voliva, a full-stack engineer with 14+ years of experience building APIs, web apps, cloud infrastructure and AI features for government agencies, startups and media companies. Infinite Iterations is how I take on client work, so the person you hire is the person who writes your code.
~/infinite-iterations $ git log --oneline
a02be59 Ship AI services to AWS GovCloud
3f9c1e2 Port .NET traffic APIs to FastAPI
b81d07a Tune National Archives search
7ce4410 Cut Lambda cold starts
e5d2c90 First U.S. hire, to acquisition
0000000 Your projectRecent work includes
Services
From a first version to a system that has been running for years, the work below is what I've done for clients and employers, and what I'd do for you.
LLM features that hold up with real users: retrieval (RAG), agents and model calls through AWS Bedrock or the vendor APIs, with tests and logging so you can see what they actually do. I've shipped ML and AI services into AWS GovCloud, including air-gapped networks.
Python (FastAPI, Django) and Node.js/TypeScript services, REST or GraphQL, on PostgreSQL, MongoDB, OpenSearch or DynamoDB. Written so the next engineer can read them, with types, tests and docs.
React or Angular front ends on top of the API, from a first version you can put in front of customers to the admin and back-office tools your team uses every day.
AWS, GCP and Azure, Docker and Kubernetes, Terraform and Helm, and CI/CD in GitHub Actions or GitLab. Deploys you can repeat and environments you can rebuild from code.
Moving old systems forward while the business keeps running. I've rewritten C#/.NET APIs in FastAPI and moved sign-in to OAuth 2 with Azure SSO.
A fixed-length review of your codebase, cloud setup or AI features, ending in a written list ranked by what to fix first. Typical finds are missing tests, unpinned dependencies and tokens leaking into logs.
Selected work
A few projects from the last decade, in public services, government, media and startups.
Led backend and API engineering for catalog.archives.gov, the public search for the records of the U.S. National Archives. Node.js and Python services, OpenSearch query tuning, Airflow ingestion and Terraform on AWS. I also wrote down the team's code review standards and mentored engineers.
FastAPI services for real-time traffic monitoring, CCTV analytics and data ingestion, with GraphQL over MongoDB and React dashboards. Rewrote legacy C#/.NET APIs in FastAPI and moved sign-in to OAuth 2 with Azure MSAL single sign-on.
For a government-affiliated enterprise client: Python/FastAPI services, a React operator console and ML models that filter alert noise. I adapted the services, Helm charts and GitLab CI/CD for GovCloud and air-gapped environments, and added linting, typing, unit and integration tests.
The React overlay for the live interactive series, built on the MILE SDK and backed by serverless Node.js/TypeScript on Lambda, API Gateway, SQS and DynamoDB. Reduced Lambda cold starts and added LocalStack integration tests to CI.
First U.S. engineer at the startup, through its acquisition by Invoca. Led the core platform service (authentication, billing and developer onboarding) and worked on the Python and web SDKs and real-time audio streaming APIs over WebRTC and WebSockets.
The only full-stack engineer for more than five years: the POS backend in Python Pyramid and PostgreSQL, an Angular/TypeScript back office for menus, pricing, payroll and integrations, and online ordering.
How a project runs
The name comes from how I like to work: get a real version in front of people early, then improve it in short iterations, each one something you can try.
A short call about what you need, what's already there and what's in the way. If I'm not the right fit, I'll tell you.
A written plan with the scope, milestones and a price or estimate, so you know what you're paying for before work starts.
Work arrives in small releases you can use, usually every week, with a short note on what changed and what comes next.
You own the code, the repositories and the accounts. Tests, docs and a deploy your team can run without me come with it.
About
I've been building software professionally since 2012, mostly remote, for teams on Pacific, Central and Eastern time. I've been the only engineer at a restaurant software company, the first U.S. hire at a startup, and the backend lead on public systems like the National Archives Catalog.
Lately most of my work pairs backend engineering with AI: putting LLM features into production, and using AI coding tools with careful review so the extra speed doesn't cost you quality.
Python, TypeScript, JavaScript, SQL, C#, PHP, Java
FastAPI, Django, Node.js, Express, GraphQL, SQLAlchemy
React, Angular, Material UI, HTML and CSS
LLM APIs, RAG, agents, AWS Bedrock, SageMaker
AWS (incl. GovCloud), GCP, Azure, Docker, Kubernetes, Terraform, Helm
PostgreSQL, MongoDB, MySQL, OpenSearch, DynamoDB, BigQuery, Airflow
OAuth 2.0, SSO with Azure MSAL, JWT
GitHub Actions, GitLab CI/CD, LocalStack, TDD
Ways to work together
A defined build with a written plan and scope. Good for a first version, a new feature or a rewrite.
A set number of hours each month as your senior or lead engineer, building features and helping your team.
One to two weeks reading your code, cloud setup or AI features, then a written report you can act on.
FAQ
Yes. Infinite Iterations is me, so the person you talk to is the person who writes and reviews your code. If a project needs more people than that, I'll say so before we start.
Often that's the best setup. I can join your repositories, follow your process and review your team's pull requests, or own one part of the system end to end.
Yes, carefully. I use tools like Claude Code, Cursor and Codex to move faster, and every change is reviewed and tested before it reaches you. If your company doesn't allow them, I won't use them on your code.
I'm a U.S. citizen and have worked on federal and state systems, including services running in AWS GovCloud and delivery into air-gapped environments.
I'm in California and have worked on Pacific, Central and Eastern hours for remote teams.
Send me a few lines about the project and your timeline. I'll reply to set up a call, and we'll go from there.
Contact
Send a few lines about what you're building and when you need it. I'll get back to you to set up a call.