---
title: "Welcoming Matt Gilbert, our new Data Analyst"
slug: welcoming-matt-gilbert
description: "We're thrilled to share the news that Matt Gilbert is joining Resend."
created_at: "2026-07-09"
updated_at: "2026-07-09"
image: https://cdn.resend.com/posts/welcoming-matt-gilbert.jpg
humans: ["bu-kinoshita", "matt-gilbert"]
category: "company"
---

Today, we're excited to share that <Human id="matt-gilbert"/> is joining the team as a Data Analyst on our Trust & Safety team.

He comes to us after 10 years as a Deliverability Engineer at Mailchimp, where he handled data for the Delivery team, all while managing and maintaining sending infrastructure that pushed around a billion emails a day. Before that, he worked on the Mandrill transactional mail service.

We're thrilled to have Matt bring his experience sending trusted email at scale to help make Resend the safest and most reliable place for developers to send with confidence.

## More about Matt

**How did you get into software?**

My first introduction to computers was through my grandfather and uncle, both of whom worked at IBM while I was a kid in the 1980s. I didn't really get into computers myself though until after high school. I went to **college for Computer Science**, with a specialization in Computer Graphics. I ended up in more of an IT role though, as I got hired upon graduation by my college to run their computer graphics labs for their campus in New York City. 

I've drifted around in tech ever since then, but really **found my niche** as a software engineer in **deliverability for email**. I love the multifaceted nature of engineering for email delivery and deliverability.

When you work in delivery and deliverability, **you get to wear a lot of hats.** You have infra-ops work managing the MTAs, you have data engineering and analytics work managing the mail queues and how they are performing. And you have work that is more irregular that involves troubleshooting delivery issues sending mail or deliverability issues getting to recipient inboxes. For someone working in email, every day is unique, and monotony or tedium are very rare.

That led me to data engineering and analytics as a "specialty" within the larger scope of managing email at scale. Anyone can send an email programmatically, but **sending at scale takes a lot of work**. And you can't work well sending email without data. Every organization that sends and receives email gets to set their own rules about what email they will accept, who they will accept mail from, and where they will place that mail once they accept it. Building data that lets senders see how they are doing and where they are having problems is a challenge that never gets boring.

**What does your desktop/home screen look like?**

![Matt's desktop](https://cdn.resend.com/posts/matt-gilbert_desktop.jpg)

What can I say, **I like dark minimal aesthetics**. Resend fits my tastes well.

**Why are you at Resend?**

You would think that email was a solved problem, and there was no room for innovation. I think Resend proves that wrong. Even in the world we live in with AI agentic development all over the place, Email still has its place in the world.

If you have any sort of a service with customers, you need to communicate with them, and email remains the universal, globally-available, open standard to do that (owned by no one). 

When I came across Resend and saw what they were building, I knew I had to be a part of that. Providing an email service that is designed for developers, and can integrate with minimal friction into any environment is a challenge. I think Resend has figured out the secret to make that a great experience. I'm looking forward to taking my years of experience with email and helping Resend build awesome **new data-driven capabilities and intelligence** that will empower our customers to send better, and reach their customers' inboxes as quickly as possible.

**Where do you find #inspiration?**

* For being a better human: My wife.
* For being a better engineer: The people I work with.
* For taking it easy: My cats.
* For everything else: Calvin and Hobbes. :)

More generally, I find people who are really good at something I'm also interested in, and I learn by their example.

**If you weren't programming, what would you be doing?**

Scuba diving, exploring nature, visiting a park, or building yet another custom keyboard.

![Matt underwater](https://cdn.resend.com/posts/mattg_scuba1.jpg)

**Favorite tool?**

Overall: My custom keyboard. I designed it from scratch and programmed it myself to perfectly suit my needs. It's wireless, split, ergonomic, and ultra low-profile. I can barely use a standard keyboard any more.

![Matt's weird keyboard](https://cdn.resend.com/posts/mattg_keyboard.jpg)

+For software, can I just say the terminal? I am an aficionado of a well-crafted [CLI tool](/docs/cli). My editor of choice is Neovim, which I currently configure with the LazyVim setup. I use starship for my custom prompt, and I spent a full day writing my own config for it. I have a curated library of aliases and shell functions / scripts that I use regularly to make my life in the terminal easier.

**Favorite hotkey?**

I'm not much of a hotkey guy. I use homerow mods on my keyboard, so all of the standard key-combos are quick and comfortable. I do have 12 keymaps that I've set up to work with the built-in window tiling in macOS that I use all day, every day. I don't think I could function without those, so I'll say those are my favorites.

**Favorite place to visit?**

Anywhere tropical! Access to scuba diving is a plus.

**Advice for ambitious software engineers?**

Software engineering is a big, huge, field of options. Don't follow trends, or constantly jump around to the "hot new language of the day". **Find a niche that makes you happy** and become very good at it. Whether that is building mobile apps, full-stack engineering, front-end web development, SRE, QA, data-engineering, or anything else; if it makes you happy doing it, then become the best you can on that thing. You'll always find work if you are good at what you do.
