To start, share your story with our readers. How did your professional journey begin, what challenges have you faced, and what achievements are you most proud of?
I started as a self-taught developer. I always knew I wanted to do this, I loved coding since I was very young. But I was pretty bad at school so university wasn’t an option – I simply couldn’t get admitted to any. So I spent sleepless nights in my early 20s learning how to code and build frontends, backends and cloud operations for my projects. I was pretty much full-stack from Day 1 and very practical. When I started working in the industry, I was really struggling with the imposter syndrome (and I still do to this day). Everyone around me had a lot of experience, advanced degrees, and knowledge in Computer Science. This always made me feel like I have to go the extra mile, and it’s a sort of culture I’ve developed – to always aim to be the best at whatever I do. At some point, my manager told me – “If you can teach it, you know it”. It sunk really deep, and I decided to start making online courses on Udemy, where I learned everything myself. It was a shot in the dark, but fast forward a few years later, my courses are bestsellers with over 170,000 students worldwide and around 60,000 hours watched per year. It helped quite a bit, but the imposter syndrome never goes away. Maybe it’s a good thing that helps me keep myself in check. I’ve climbed the career ladder pretty quickly. I was always told by my business peers that “it’s so pleasant to work with a developer who understands the business and communicates so well”. I was just lucky to work at amazing companies where culture, communication and diversity were core values. Very early on in my career I prioritized soft skills over hard skills. I found myself in leadership positions at companies many of us know, such as Platform Engineering Manager at Serverless Inc., Head of Engineering at Abcam, and a few others. My greatest challenge was as Head of Engineering at Abcam. It was a very traditional biotech company (25 years old, traded in the NASDAQ) with the goal of doing a complete digital transformation. I was engineer #1 in the transformation process and was tasked with setting up everything engineering-related. I’ve hired 70 engineers in the first year, and the most challenging part was to get the absolute top talent to work at a company that does life sciences. Engineers often look up to companies they can better understand, such as Uber, Amazon, etc. But supporting life scientists in finding a cure to Alzheimer’s disease is much more rewarding. I had to find a way to onboard engineers in a way that bridges the gap between their love for software development and life scientists so we can grow quickly. That was very challenging but super fun. * * P.S. Last year, Abcam was sold to a private equity firm for $6 billion USD. Great success!What pain point(s) do you solve for your customers? What was the “aha Moment” that led to the idea? Can you share that story with us?
I came up with the idea for Pezzo when I built a side project with friends. It was called Resumator, and the idea was to use the first iterations of Generative AI (GPT 3 at the time) to help job seekers maximize their chances by tailoring their resumes and cover letters to specific job descriptions, using AI. We delivered something that worked pretty well in no time. But the process was painful. We were two full-stack developers and a product manager. We were all very experienced, and we immediately noticed some fundamental pains with Generative AI that pretty much all “traditional” developers would face as soon as they start adoption: ReliabilityAs a developer, I am used to having tests in my code. But AI is probabilistic, rather than deterministic. I want to be able to make changes to my prompts with confidence. Maybe I also want to perform some A/B testing to prompts before shipping them to production. Pezzo allows you to test your prompts before publishing them. You just have to click on the Test button and wait. Confidence
What if OpenAI releases a new version of an AI model I use in production? AI could move under me and mess things up for my users. With Pezzo you can fine-tune prompts and commit the new version instantly, and their troubleshooting feature gives you the full context of the stacktrace and user journey. Collaboration
If I want to make a change to an AI prompt, I have to open up a code editor, make the change and test it, then commit and create a pull request, then release. It made no sense to us that AI prompts (pure English) go through the same release cycles as traditional code. This prevents business folks from contributing to AI prompts, which they are pretty good at. You can use Pezzo as a centralized prompt management platform. This lets you collaborate with your team and iterate quickly, while monitoring the costs of your AI operations. Observability and Monitoring
Detecting anomalies in costs, troubleshooting issues users face in production with full context of the stacktrace and user journey, the ability to replay requests and track usage – there was no (and there still isn’t) a built-in solution for this provided by any AI provider. Pezzo provides a historical view of your prompt execution stats and metrics (duration, prompt cost, completion cost, etc.) for better insights. There are two main reasons behind these problems: Firstly, OpenAI just made it possible to use an AI model with just one API call. Developers now have superpowers. Secondly, the fields of Machine Learning and AI have long been dominated by Data Scientists and other professionals who typically don’t ship things to production. Therefore, tooling wasn’t quite there, but the reality was clear: Now that it’s just one API call away, product teams with traditional engineers will be expected to ship it. I had to build the tools to accommodate this paradigm shift, and that’s how Pezzo came to life – to solve my own problems.
What do you think makes your company stand out? What are you most proud of?
I’ve built Pezzo to solve problems for product teams, not for scientists. There are dozens of millions of full stack developers in the world who are expected to ship AI right now or in the near term. But as full stack developers, our needs are different. I’ve spent a decent amount of years working on open-source developer tools – you could call it my bread and butter. I made the decision to build Pezzo as a 100% open-source platform from Day 1. All of it. Not only that, but it’s also fully cloud native, meaning that you could deploy the entire stack and all of its dependencies to any cloud provider or on premises. Of course, making Pezzo open-source brings challenges:- It slows you down because you have to be “presentable”
- Your code must be neat and secure
- Everything must be well documented
- You cannot cut corners as you can do with closed-source software
🚀 Just a year later, the open-source version of Pezzo has been downloaded over 630,000 times, while their SaaS platform has managed millions of production AI requests for over 3,000 users from famous organizations.