Hey Bees! 👋

I could have just sent you a normal application. Instead, I made this.

Not because I think a website is necessary to apply for a Support role, but because after reading the job description, it felt like a better way to show you how I think, what I’ve worked on, and why I found the role interesting.

Note: I used AI to generate the draft, but none of it is a cooked-up story aligned with the job description.

I like figuring things out.

I started working while I was still in college. During COVID, college moved online, which gave me an unusual opportunity.

I started working directly with creators and entrepreneurs, including Ankur Warikoo and Akshat Shrivastava, while continuing college at the same time.

Technically, I was still a college student. In reality, I was working close to full-time hours alongside it.

I handled a lot of the technical side of their work — websites, tools, integrations, newsletters, and whatever else needed figuring out.

It was a pretty unusual way to go through college, but it taught me a lot early on: how to work with people who move fast, how to take ownership when there isn't a big team around you, and how to learn something quickly when nobody is going to teach you first.

The feedback I got below. If the image is not loading click here.

Here's what Ankur has to say when I was leaving the team. If the image is not loading, click here.

I’ve been the newsletter guy too.

Working with Ankur and Akshat also meant getting hands-on with newsletters and email platforms.

I worked with ConvertKit for Ankur’s 100K+ subscriber newsletter and MailerLite for Akshat's 35k+ subscribers.

Because these were small teams, when something went wrong, there wasn’t really another department to hand it to.

If emails weren't reaching people properly or started landing in spam, I had to research what was happening and figure out what we could improve.

That’s how I started learning email deliverability.

Then I went down the deliverability rabbit hole.

Later, I applied for a Support Engineer role at Brevo. This is soon after my college.

While preparing, I took a deliverability course and had an interview (it was a learning session for me) with a Brevo deliverability specialist. I went much deeper into SPF, DKIM, DMARC, and sender reputation.

I ultimately received an offer.

I ended up joining Zapier instead, but the experience gave me a much stronger technical understanding of email.

So when I saw a Support role at a newsletter company, the overlap was hard to ignore.

Today, I work in Support at Zapier.

A lot of my job is troubleshooting integrations, tracing errors, investigating APIs and authentication issues, and figuring out what is actually going wrong.

I don't particularly enjoy just passing problems along.

I like understanding the problem first, narrowing down what is happening, and giving the next person something useful to work with.

Basically, technical debugging with a customer-facing layer.

I also like building things with AI.

At Zapier, I’ve been experimenting with AI to solve problems I actually encounter in my work.

One of my projects started as a simple Escalation Readiness Checker.

The idea was straightforward: paste in a Zendesk ticket and have AI figure out whether it had everything needed for an Engineering escalation.

Then I went down the rabbit hole.

I expanded it to handle Legal, Sales, MCP and other specialized escalation types, with different checks depending on the situation.

I also built an App Review skill where I can paste an app’s code and have AI check it against requirements we repeatedly verify during review — things like documentation, public APIs, authentication, and other app requirements.

The first version usually solves the problem I had.

Then I use it, find everything annoying about it, and build the next version.

I tend to go down rabbit holes.

If something doesn't make sense, I want to know why.

I'll read the documentation, search around, reproduce the issue, ask someone who knows more, use AI where it helps, and keep going until I understand what's happening.

Sometimes I find the answer.

Sometimes I find a bug.

Sometimes I discover that the answer is buried in a 14-month-old internal document that absolutely nobody was supposed to find.

But I usually come back with something useful.

I’m probably not the loudest person in the room.

I'm naturally a little quiet.

But I like figuring things out, building things, and getting better at whatever I'm doing.

I’ve worked in tiny teams where I had to figure things out myself, and now I work at Zapier, where I get to do that at a much larger scale.

That combination has probably shaped how I work more than anything else.