Interview with Wade Foster, CEO of Zapier

In this 25‑minute remote interview, host Lisette talks with Wade Foster, CEO of Zapier, about how the company built a fully remote organization of 200 employees. Wade explains that Zapier began as a side‑project without an office, and the decision to stay remote was driven by early team geography and cost considerations. He describes the company’s virtual office – a laptop, internet, and a tool stack centered on Slack, Zoom, Google Docs, GitHub, Jira, and Zapier itself – while allowing personal choice for secondary tools. He discusses the discipline required for remote work, especially documentation and proactive communication, and outlines hiring criteria: self‑starter attitude and strong written communication. Wade addresses loneliness, the social strategies employees use, and why distributed talent is the future of work. He warns against common pitfalls when mixing remote and office staff, such as treating remote workers as second‑class citizens and lacking management empathy. Management practices at Zapier focus on clear expectations, artifacts (commits, tickets, designs), OKRs for alignment, and regular one‑ons via Zoom. Conflict is handled with direct, observational feedback, and video is a cultural norm for meetings. Team‑building includes a GIF‑based virtual dance party, random pair‑chats, and twice‑yearly in‑person retreats. Finally, Wade advises newcomers to just start, iterate, and learn by doing, and points listeners to his Twitter and Zapier’s website for more information.
Chapters
We should be live. So welcome everybody to this remote interview. My name is Lisette and I'm interviewing people and companies doing great things remotely. And I am super excited because today on the line, all the way from the Bay Area, California, Wade Foster, the CEO of Zapier. And a lot of my friends are extremely excited that I'm interviewing you because there are some serious Zapier fans out there. And your tagline, Zapier makes you happier. Your guys are a productivity tool that automates repetitive, tedious tasks. Always great. And you have 200 employees, 100% of which are remote. There are no offices. So we're totally diving into that. But Wade, let's start with the first question. What does your virtual office look like? What do you need to get your work done?
You know, the, the only thing I need is my laptop and an internet connection. Uh, the whole company runs off of tools like Slack, like Zoom, uh, and that's how we communicate, that's how we organize work, and that's how we get stuff done. So as long as I have an internet connection, I'm, I'm good to go.
Okay, and, and, uh, you have 200 employees that— and it's 100% remote. That is quite an accomplishment. Why did you make that? Were you always remote?
Zapier started as a side project, and side projects tend to not have offices because side projects tend to not have money to pay for offices. Right. So that's kind of where we got started, and then as we made progress, we had moved— we started in Missouri, and then we moved to the Bay Area when we went through Y Combinator, and we got all the funding, but at the end of that, Mike, one of our co-founders, he moved back to Missouri. Surrey to be with his then-girlfriend, now wife, as she was wrapping up law school. And so we weren't going to like break up the company because he couldn't be in California with us. He was too critical for what we were doing. And so we'd done this, the side project thing remotely, and so why not keep running the company remotely was kind of our line of thinking. And, uh, we hired some other folks. We hired someone in Chicago, then We hired someone else in Missouri, so we were spread across, you know, 3 states at that point in time. And it was working pretty well for us, so we were like, why not just keep doing it? And that led us all the way to 200 people.
Okay, I mean, because I know that in the Bay Area, I've talked to a number of startups there, remote employees, it's not popular amongst sort of startup communities. Do you run into that as well?
You know, in 2012 when we were really getting started, started, that was certainly the case. These days, like, it feels like the sentiment is changing. I think because of the cost of living in the Bay Area, because it's so hard to hire engineering talent in the Bay Area to compete with companies like Google and Facebook and Netflix for great engineering talent, more and more startups are considering what's their non-Bay Area strategy. And some of that's a second office and sometimes that's remote employees. So you're seeing it be a lot more commonly accepted. And I think tools like Zoom and Slack have made it a lot easier to work remotely. So the stigma isn't quite as strong as it was in 2012.
Okay. Good to hear. I was thinking like, how can people afford, I mean, you know, it's a, it's a crazy expensive place to live anyway. And then once the tech boom hit, yeah. So I wanna ask you about some tools. I read on your website that you live your work lives in Slack. Slack, is that still the case or is that a—
That is the case, yeah, we use Slack. We are power users of Slack. In fact, I think we have more channels than we have people when we use Slack.
I can believe it, I can believe it. And what are some of the other tools? You mentioned that there's Zoom, of course, which we're not using 'cause they're having an outage right now and I'm using my least favorite tool in the world, which just happens to be working. But what are the other, so Zoom and Slack, what are some of the other ways you communicate?
Zoom and Slack are really critical for us. We're also big Google Docs users. We use GitHub for the whole app is hosted, all our developers use that. Jira for a lot of project management, some Trello for project management. Because we connect a lot of different tools using Zapier, we use Zapier a lot, but then people use all sorts of other things too. So sometimes it's just down to the individual's personal preference. So there's a lot of folks using tools like Todoist, or some folks might like, you know, Checkist, or some folks might like Things. And because we support all these different apps and we can integrate them, it allows folks to kind of have their choice of tools that they personally like, and we don't have to standardize quite as much as a company, which has been fun.
I can imagine. I was just going to say, most companies standardize their toolset so everybody has to use the same thing. But of course, Zapier specializes in making everything work together and run together. So do you run into problems having everybody using their own tools?
You know, there are certain things, you know, obviously we need to all standardize on Slack. We can't have people using different, you know, chat tools because that wouldn't really work very well. But things like project management tools or like very personal toolkits like your to-do app, whatever you personally use for to-do app, go for it. Like, you know, whatever keeps you productive, makes you happy, there's no problems with that. It's mostly like the main mission-critical ones that we have to standardize on. So things like Slack, things like GitHub are things that everyone does use. But past that, it's kind of whatever gets the job done. As long as you can link to it and someone else can see it pretty easy, we're pretty happy.
Okay. And what are some of the challenges that you guys face with remote working? It can't be all— clearly it works because it's a very successful company, but it can't be all roses. So if you don't mind sharing some of the— what's hard?
I think it requires a certain amount of discipline, particularly around communication and documentation. Not all companies are used to documenting their decisions and documenting their projects works diligently. When you can go tap someone on the shoulder and say, "Hey, remind me what we were talking about yesterday. We signed on X or Y." You kind of have that luxury in an office to kind of do that a little easier. There's not as high a burden or cost to doing that. In a remote company, when you got folks all over the globe, you really need to be diligent about writing down, "Hey, we decided X." You put it in a public place. In the company, transparent, and that keeps everybody on the same page. And then your communication, you have to make sure that you kind of don't retreat into your cave and not communicate with the other 200 people you work with. You need to make sure that you are talking about the work, talking about when you get roadblocks, asking for help when you need help. So you kind of have to break out of your, your shyness shell a little bit to make sure that you're collaborating with your teammates. And so that, again, that requires some discipline. So I think the biggest challenge is that you got to build those good work habits, those habits that help you stay productive. And if you do that, then it works great. You don't have a lot of problems. But if you don't commit to that, then you're going to probably find it a little frustrating.
When you're hiring people, how do you filter for people that will make for good remote workers?
There's two things that we look for in particular amongst a lot of things. So we look for people who are just generally good, uh, because generally people who are talented and can learn can adapt to the situation that they're in. Um, but there's two things in particular. One is you want self-starters, people who just default to getting things done, default to creating. Those types of folks are going to work great in a remote environment because you don't have someone sitting over your shoulder saying, "Hey, do you need help? Are you stuck?" People who are like self-motivated, self-starters, they're going to be the ones that will just leap into action and figure things out. So that's a big pro in a remote environment. And then you're looking for folks who are strong communicators, particularly written communicators. And so You want to pay attention to like how they correspond over email. How are they clear in their communications? If you ask clarifying questions, are they able to articulate what it is that they're trying to communicate to you well? So you're looking for those types of things because in a remote environment, particularly the written side of things, you want those folks who can document the work well and that you can read their documentation and understand what they're trying to share. So those are two skills that I think are, you need to have as a strength as a remote worker. And if you don't have it as a strength coming into a remote job, you'll probably develop it pretty quickly.
Yeah, or fail dramatically. Yeah, I've also seen that.
Most people are able to learn this. It doesn't take, you know, it's not rocket science. This is things that many folks can do quite well. So, you know, you put in an environment where you have to learn, and you typically learn pretty quick.
Yeah, especially if you want to. Do you ever have people where it doesn't work out, where they just say like, oh, this remote thing is not for me, I'm too lonely, or whatever it is?
Yeah, it happens from time to time. Um, you know, the loneliness thing is a, uh, that is something you have to manage as a, as a person because you don't get the, the interaction with your co-workers by default. So People take different approaches to this. Some, they'll, you know, make sure they jump on Zoom calls throughout the day just to catch up with their teammates, and that works. Others make sure that they're involved in their communities, whether that's, you know, volunteering or churches or schools or whatever it is that, you know, sparks their interest. We found also that we have a lot of families that work at Zapier, so a lot of parents come work here because they, you know, for them work isn't their social outlet. They have other things that they rely on for a social community and for that connection. And so that ends up being quite well for parents. But everyone manages it a little differently. And some folks decide at the end of the day, you know what, I do want that more close human connection as part of my work. And so that does occasionally occasionally happen. Not often, but it does happen.
Yeah, I've wondered about that because, you know, when you work on your own, you get to choose who your social connections are, whereas if you go to an office, yeah, you know, you just kind of get thrown in with a group of people, and sometimes it's good and sometimes it's not good. So I was always baffled by the loneliness thing. I thought, like, go out into the world, like, there's a whole coffee shop full of people waiting to hang out with you. Yeah, but okay, we're all different, to each their own. So you've said before in something that I've read, you've said distributed teams are the future of work. And I guess with your experience now that you really believe that, but why do you think that that's the case?
Well, I think it is, I think it's the tool sets are getting better. So it's enabling it to actually be possible for the first time really in modern history can you do it at any sort of scale, which is exciting. And it opens up all sorts of opportunity. There's the phrase that, you know, skills are equally distributed, you know, talent is equally distributed across the world, but opportunity is not. Opportunity has tended to cluster in certain geographic areas. In San Francisco, in New York, in LA, places like that. But what the world is realizing is, wow, if talent is distributed and I can tap into that talent, there's a whole set of talent outside of these major cities that I get to— I could work with if I choose to do that. And so I think more and more people are catching on to that fact that there are really talented, hardworking folks outside of these kind of hubs. And I just think that's one, it's a competitive advantage for the companies that are doing it, but I also think it's just good for society. It's good for society that opportunity becomes more equally distributed. I don't think that it will ever be perfectly distributed, but it should be more so than the way it is today.
Indeed, indeed. Tons of people that are in countries where they're not allowed to leave, for example, but they have great, let's say, computer skills, programming skills, and it's a shame not to be able to use them, especially when there's such a shortage of programmers out in the world. Seems like everybody's looking for programmers. I wish I had programming skills. That would be, yeah, it'd be way easier to make a living that way. That's for sure. That's for sure. So there was also a question when we were deciding to do the interview that you had some of the biggest mistakes that companies make mixing remote and in-office? What are some of those mistakes? Because that is super common, and I think that's probably one of the hardest ways of working remote. When everybody's remote, it's a little bit easier, but when you've got the mixed situation, which is really common, it just starts getting exponentially difficult depending on where people are. So what do you see as the biggest mistakes?
Well, I think the biggest mistakes is that they, they start to that the remote workers are taken for granted and they become this kind of second-class citizen. And it's usually not malicious, you know, no one chooses to make it harder for a teammate to work. That's not what happens. But they don't think about structurally how you set up the work. What happens is management is always centralized, and so management is like, well, I don't see why these people are complaining. Complaining, they just need to be better or whatever. Like, it's, we're not having this problem, so the problem must be the person. Rather than saying, you know what, maybe I should try, as in management, I should try working remotely for a week, for 2 weeks, for a long enough period of time that I have to really understand what are the pros and cons, what are easy for me to do, what are not, what's not easy for me to do. And when you do that, you you start to realize, here's what my remote teammate's challenges actually look like. And then you can start to structurally change your organization to better accommodate remote workers. But too often folks just kind of hire them and then let the remote workers sort of fend for themselves to sort of figure out how to navigate the org, how to get through the sort of structures of the org. And you know, some folks can figure it out and do fine, but without some sort of like management leadership support, it's gonna be hard for the vast majority of folks.
Yeah, you really have to have a really proactive self-starter who's, uh, ready to just go out. And they exist, that's for sure. I hired one woman once and we were— we had, you know, 200 facilitators for this one company, and the very first day she just said, Do you want me to call them all? I can call them all and ask them a few questions. And I thought, whoa, that's something that, uh, not a lot of people would do. But she was like ready to get on the phone with 200 people, no problem at all. Loved it.
Yeah. And of course it's fantastic to work with those types of people. It's energizing to work with those types of people. Um, but not everyone is like that and that's not everyone's strength. And you know, to build a really world-class organization, you you need kind of all types to be successful. Uh, and so I think it's important to kind of build an organization that can be inclusive of all different types of work styles for sure.
And when you get— if you get, you know, 200 people who are super proactive and super energetic working together, that can also be a recipe for disaster. You need a few people who are a little bit more level and, uh, toned down a bit, I would So what other tips though for managing remote teams have you discovered through this journey?
You know, the more and more that I've discovered, I think just good management is the same whether you're in an office or whether you're remotely. Now some of the tactical stuff is different, like, uh, if we were to do a one-on-one together, well, we would get on Zoom and do our one-on-one rather than, you know, sit down for coffee and have a one-on-one. But the conversation you and I would have would still be very similar. It would be like, "Hey, what are your objectives this week? What are you paying attention to? What are you struggling with? What are your blockers?" We would have the same type of conversation. It just would be happening over Zoom. So, and then if I'm a good manager, I'm setting good expectations for you. I'm providing a level of clarity so that you know, hey, these These are the things that I gotta go achieve to meet my goals, to meet the mission of the organization. And if you go do those things, all's good. If you don't, I'm gonna ask, hey, what's going on? What's struggling? And so a lot of that thing, or a lot of those skill sets are things you would do in an office, it's things you should do remotely. I think the power of remote work is that it kind of tears down the facade of what good management might be. A lot of folks think good management is walking in and surveying the people sitting in the chairs across the office and going like, "Haha, I built this and I am a good manager and, you know, I smiled at my people at lunch and so I must be a good manager." But that's not what good management is. Good management is setting clear expectations, coaching and mentoring, It's aligning the organization's goals and then measuring the progress over time. And if you do that in an office, you can do that remotely. It doesn't matter where you do that. And I think remotely it really crystallizes that that's what your job is. And so you have to kind of do that, right?
Being the like go-lucky fun person or fun manager surveying at the office is, uh, it doesn't go very far remote. That's for sure. That's for sure. So how do you know then what people are doing on your team?
The biggest thing is artifacts. You have them report back. So, you know, if it's— if they're in support, I can go look in our reports for productivity. I can see what emails they sent. If they're a developer, I can go look at GitHub commits and I can see what are they committing to the code base. If they're a product manager, I can see the stories that they're creating in JIRA and the specs that they're writing. If they're a designer, you can see the mocks that are being created and the interviews that they're doing with customers. So every role creates these artifacts. They deliver things. They— and if those things don't get created and those artifacts aren't— that don't exist, that's when you start to ask questions and say, hey, you know, I thought Well, what's going on here? You know, we expected that this was to exist and it doesn't exist. Is there a resource you need? How can I help you? What can I do to help us meet this shared goal? So those artifacts are the most important way for knowing what's getting worked on and what's getting done inside the organization.
So the leader, the manager would then set clear expectations for what's expected to get done and then the results I assume that the artifacts, what you've done, proves or shows that you're on the right path, right? And in a way, it seems like a much better productivity measurement than hours spent in a seat at the office. Like, are you there from 9 to 5 or did you get your work done? It seems like a— and the motivation is in a better place. But okay, but I digress and I'm very biased, of course. But what I'm curious about is how do you handle conflict on your team when it comes up? Is there a certain procedure that you guys have in place or what happens?
You know, I think again, conflict management, I think it is very similar as in an office. If you're having a tough time with somebody, you should go talk to them directly. You should say, hey, when you do these things, this makes it tough for me. Or, you know, when you do these types of behaviors, makes it hard for this project to get done in this way. Is there something we could do differently here, right? You like to address this stuff head on. Now the tendency I found in a remote company is culturally, because you can't see the person and you can't— it's harder to read body language sometimes. Sometimes it's— people will have the tendency to sweep stuff under the rug a little. And so you really have to, as an organization, organization practices a little bit. So as part of onboarding, I, I teach a course on how to give feedback to help people get more comfortable. We actually have a, like, a very stylistic way that we give feedback so folks know that it's, hey, oh, this is Zapier style feedback. It's not a scary thing. It's just a normal part of how we run this organization. It's not something to be feared. It's something to be grateful for because feedback helps make us better at our jobs. And so that's one thing we've done to try and help folks bridge conflict, because conflict is gonna come up. It happens in any sort of workplace, and you need tools to help you address it. And unfortunately, most of us— certainly I know myself— we don't get trained in conflict management. There's not a— you know, I didn't have a high school course that was like, "How to deal with conflict." So what ends up happening is you kind of just develop your own tips and tricks based on your interaction with your family or your interaction with a sports team or whatever. And who knows if that's actually a good way to deal with conflict or not. Many of our families don't deal with conflict in very healthy ways. And so I think it's important that organizations help teach folks their style of handling conflict.
And what is your style of feedback?
So we use what's called an observational method. So it's based on what do you— what did you actually see happen? So for example, you know, I was running 5 minutes late for our podcast today, and if I was— if If we were coworkers, you might say to me, if I had a habit of doing that, you might say, "Hey Wade, I noticed that you show up late a couple times to these podcasts. When you show up late, it makes it hard for me to keep on schedule. Can we try and be on time next time?" I might be, "You know what? I can try and do that." Because it's based in fact, because it's observable, I agree. Yes, I did show up late. I was 5 minutes late. I can't debate that. I can't, um, you know, versus if you would say— if you were to say something like, Wade, it doesn't seem like you care about the podcast. I might be like, what? That's crazy. Of course I care about the podcast. Um, and that's not a great way to deal with conflict. But what you really are noticing is that I'm showing up late, and if I were to show up on time, all would be good. So it's really important to focus in on the behavior that you see and observe, and then ask for a change. And that's the model that we have. And you can use this both for positive feedback but also for constructive feedback. It works great for positive feedback because it reinforces the behaviors that you want to see over and over and over again. And turns out humans respond better to positive feedback anyway.
Yeah, constructive is always great rather than like the blame. And it's sort of a, you know, when somebody blames me, I get defensive immediately without, I mean, it's like an instant response of like, oh yeah, well, and then, you know, you don't even take a step back. So yeah, it sounds like the observational, it sounds really similar to nonviolent communication, sort of stating the fact and then saying how that fact makes you feel. Very, yeah, can't argue with that. I mean, if it makes you feel, it makes you feel. So. Exactly.
How—
actually, I'll, uh, oh, one question I wanted to ask. Do you use— I'm assuming since you're using Zoom a lot that, uh, that video is, uh, a big part of the talking to each other. Is that the case?
Yeah, definitely. So I think you want to make sure to have this kind of face time with your teammates. I think it's super critical to just building relationship, building a bond.
Are there people that refuse to turn the video on?
[Speaker:WADE_FOSTER] You know, there's some folks who are a little nervous, but because it's such a cultural norm at Zapier to have video on, it's pretty rare to have it turned off. Maybe in like a really big meeting, like we do our all-hands where it'll have like over 100 people in it, and it's mostly like a presentation by a couple people to everyone else. So the people who are listening might turn their video off and, you know, multitask on a few things while that's happening. But if it's an actual meeting, meeting between me and you, like, of course we have the video on. Or if it's me and the small team, of course we'll have the video on because we want to see each other and talk to each other.
You say of course, but there's a lot of companies out there, a lot of people out there who don't like video. It makes them feel shy, or I'm not sure what. They want to be in their pajamas, and I always just say, like, put on a shirt. Like, stay in your pajamas and put on a shirt. Like, how hard is that? Okay, yeah, I really find the, the seeing people is really important. So it's nice to hear that that's a norm. And then the other question that I wanted to ask was about alignment. How do you guys stay aligned as a company? I mean, 200 people is a lot for any company, and, you know, but alignment is always an issue that people ask about. So what do you guys do to keep that alignment?
You know, we're— I wouldn't say that this is a strength of ours yet. I think we have some improvements to try and make on this. One of the things we started doing last year that's helped us is using OKRs, objectives and key results, as a company across our organization. So we started using as an executive team in the middle of last year, and now we're rolling it out this quarter to the whole company. And we're starting to see teams talking to each other in ways that help build that alignment. They say, hey, I noticed that your goal is this, like, we kind of have a similar goal, uh, how can we merge our efforts? Or, hey, I have this goal and I noticed— and I was counting on your help, but I noticed you have a totally different goal, so what should we do? Like, should we— we need to resolve that conflict there that I have a goal that depends on you, but you're planning to do a totally different thing. So we're hoping that this OKRs, as we scale it out, will help us build more and more alignment, um, between our teams as we grow.
Yeah, it's a, it's a— I can imagine, I mean, it's a hard question for any company, especially as soon as you get after, I don't know, 25 people. I would say even it's a starts to be an issue in terms of keeping track of what everybody's doing.
Yeah, I would absolutely agree with that.
Yeah, I think everybody— if there's a silver bullet out there, let me know. I'm always looking. So now I read this really great article about your company and some team-building activity that you've done, which is this virtual dance party. And so, you know, I work for a team. I'm the remote office manager in my side job for a company called Happy Melly or Management 360. Is what it's called now. And we actually do virtual dance parties in a different way. So I was really interested in seeing what, hearing about what you guys did, which was, I mean, the way that we did it was we all get on Zoom, one person's the DJ, and the rest of us get up and boogie. Like we actually just like all dance together. And you know, I close the curtains so my neighbors don't see me and all of that. But you guys did it differently. You guys recorded, everybody recorded GIFs of each other, and then you sort of made a montage. Who came up with that idea?
This was one of our customer champions. She came up with this idea on a Friday afternoon, and it kind of just took off. Like, people are like, oh, this is fun. Like, this is— I don't know, it was just one of those slow Friday afternoons, and everyone kind of just jumped in and, you know, recorded a little bit about themselves. I think the recording thing worked well for us because of coming back to the video conversation where people are a little shy on video sometimes, you're doubly shy when you're live dancing. Well, when it's recording, you can like take your time to like get exactly the right pose and exactly the right little boogie down. So you're like, "I like this one," and then you can publish that to the team. So you get to showcase your best dance move.
Love it. Yeah, I loved it. I think you've inspired a number of different teams to do the same thing because the live dancing in front of people was just a little bit too intimidating. It takes a special team to be able to pull that off, but the GIFs is really a great idea. What are some of the other team-building activities that you've tried that have worked pretty well?
We do these weekly pair chats where, for the longest time, it was a bot in Slack would randomly pair you with somebody else You would get on Zoom and you would just talk about whatever, super informal. We've now expanded them to 3-people or 4-people chats. So it's a little group chat. You can talk about, again, super informal, you can talk about whatever. It can be work, it can be personal, but it's a way just to build relationships and build bonds between the team. So that one's worked well. And then on the more extreme end, we do big company-wide company retreats as well. So twice a year we fly everyone into a central location, we spend the week working together, uh, we'll often do some, uh, fun group activities a little outside of work as well to kind of explore the city that we travel to. And those really help build a lot of bonds as well too, um, that help in the workplace.
Yeah, I used to be a big fan of doing everything virtual, and then our team got together for the first time after 5 years. And one night out on the town in Lisbon, dancing and drinking together, I mean, it was— we weren't the same team after that night. It was a much more close-knit, like, intense team. It was, uh, I became a fan of meeting in person, I got to say.
Totally. I am a— as big of an advocate for remote distributed work as you all find, but being in in person a little bit at a time is super, super helpful.
Yeah, it's just not the same to share a big plate of nachos and a beer over Zoom as it is in person. It's just you can't replicate it yet, but maybe when holograms become— someday, right? Yeah, holograms are right around the corner. We'll see. So I promised you it'd be 25 minutes and I went over already. Darn. But it's so interesting, of course, to talk to you. But final question, second to final question. Advice for people who are just starting out, what would you tell them if they're just starting out either as a company or as an individual worker? What tip would you give?
You know, I think a lot of folks wait until they feel like they have it all put together and they shouldn't. Nobody has it all put together when they first start out. So just start. Whatever it is that you want to do, just start trying to do that thing. Meet other people who are trying to do that thing and practice it. Work on it. Whether it's as your hobby, whether it's as your job, whether it's a company, do the thing and you'll get better at it over time. You'll start to have better ideas of how to make it better over time. Don't keep reading books or reading— listen to podcasts or Except this one, of course.
Yeah, sorry. I was like, except this one, of course. Yeah. But yeah.
But just start working on the thing.
Right. Right. Just start. Yeah. Because you never know what's going to— you can't anticipate all the weird, weird things that come up.
Yeah. No, that's one of the best ways to learn is to just run into the problem and you go, oh boy, I didn't do that quite right. Next time I'm going to do that a little better.
Right. Yeah, nothing like experience. Okay, and final question, easy one, which is if people want to learn more about you and more about Zapier, where should they go?
You know, I'm somewhat active on Twitter @WadeFoster. You can always follow me there and engage there. And then zapier.com, come check out the app if you want to be a little more productive, if you want to connect your tools. And of course, if any of this remote working or any of what we're doing as a product sounds interesting, we're always hiring folks too. So, uh, if you feel like you're interested to learn more, come check us out.
I've got a bunch of online communities where I'll be posting a link to you guys as soon as we get off this call, that's for sure. Lots of people— I get contacted every day about how to find a remote job, so there are definitely people looking. Wade Foster, thank you so much for your time today. I'm glad we were able to make this work, even if we did have to use Skype to do the recording. Let's just cross our fingers that it's all gonna work out, and I really appreciate you being here. Thank you.
Yeah, thanks for having me. It was a blast.
Alright.
More from Wade

From Workflows to Agent Teams: Wade Foster on How AI Reshapes Enterprise Automation

The Top Scaling Lessons from Zapier's AI Transformation with Wade Foster, Co-Founder & CEO of Zapier

Why Companies Force AI: Zapier’s CEO Wade Foster Explains | Belkins Podcast Episode #21

INSIDE How AI Startups hire, AI Roundtable with Wade Foster, Mikey Schulman, and Ali Ansari | E2225






