Engineering expertise
built to ship
Anonymous Function Labs is the technical practice of Jonathan Ballard — a software engineer and engineering manager who builds systems that last.
Anonymous Function Labs brings Engineering Management experience grounded in hands-on technical execution. Not a generalist consultant who dabbles — a practitioner who has shipped AI-powered products, led teams through SOC2, and optimized infrastructure at scale across AWS and GCP.
The work sits at the intersection of innovation and operational excellence: the place where startups need to move fast and prove they can be trusted with enterprise data simultaneously. That tension is where the most interesting engineering decisions happen.
Before going independent, I led engineering teams building B2B SaaS products at the Series A/B stage — owning the full stack from infrastructure to product delivery. That meant making hard calls about build vs. buy, managing technical debt strategically, and communicating architecture decisions to non-technical stakeholders who control the budget.
Anonymous Function Labs exists to give startups and scale-ups access to that level of judgment without the full-time hire. Senior technical expertise, brought in for the problems that actually matter, then handed back cleanly.
Depth across the stack
Not a mile wide and an inch deep. These are areas where the reps are real.
How I work
A few non-negotiables that every engagement is built around.
Every architecture decision gets documented. Every trade-off gets explained. When the engagement ends, you own everything — the code, the runbooks, the reasoning.
Perfect is the enemy of deployed. Constraints are creative tools, not excuses. The right solution for a 5-person startup is almost never the same as the right solution for a 200-person org.
Systems that are hard to change were usually designed without enough humility about the future. Every design choice is a bet — make the bets explicit and make them reversible where possible.
If the approach is wrong, you'll hear it early — not in a retrospective. Opinions are offered with evidence, not ego. Disagreement is a signal to dig deeper, not to capitulate.
Observability, alerting, and incident runbooks are part of the feature, not a nice-to-have. Systems that can't be debugged at 2am aren't finished.
Architectural decisions shouldn't handcuff your future team to a specific vendor. Cloud-portable patterns are preferred whenever the trade-off is reasonable.