Basecamp is hiring Customer Support Representatives

Basecamp is looking for two Support Representatives to join our team in providing the best customer support around. 

About the Job
You’ll be responsible for providing tremendous customer service and support via email for all versions of Basecamp and our other apps. You’ll help us answer questions via Twitter, make some customer calls, create and edit help documentation, run personalized demos, and teach some online classes. You’ll also have ample opportunities to carve out your own passion projects related to supporting our customers.

Deep technical knowledge of computer programming is not a prerequisite, however you should be well-versed in basic troubleshooting techniques to solve issues caused by most Internet Gremlins. The ability to think beyond clearing cache and cookies in order to troubleshoot the specific issue that’s reported is essential.

During training, you’ll be expected to be proactive in your process and learn quickly. Once fully up-to-speed (2-3 months), you’ll write about 100 emails per day. This is a significant volume, so be sure that you’re ready and able to deal with that kind of daily load — you’ll get all the support and guidance you need along the way!

About You
We’re looking for some great writers who love helping people, so you should enjoy making complicated situations simple and painless. This means being a great problem-solver with the ability to process and resolve issues quickly. You should be a stellar communicator, even when you have to communicate less-than-stellar news. You should have highly tuned senses of compassion and empathy and a drive to constantly help others.

We have a rhythm to our work and a low turnover rate — more than half of the team has been at Basecamp for over five years. But, your voice matters to us. We make change from fresh perspectives and appreciate new viewpoints, so you should feel comfortable speaking up about your values.

You love supporting people. This isn’t a springboard into another area at Basecamp. You want to be part of our support team for a while, and you’re excited to contribute to making Basecamp the best product for our customers.

A big part of the role itself is supporting each other, so you should understand the value in prioritizing relationships with your colleagues.

We strongly encourage candidates of all different backgrounds and identities to apply. Each new hire is an opportunity for us to bring in a different perspective, and we are always eager to further diversify our company. Basecamp is committed to building an inclusive, supportive place for you to do the best and most rewarding work of your career.


About Our Pay and Benefits
Our pay is within the top 10% of the industry, for the matched role and experience, based on San Francisco rates. We also believe in fair, living wages at Basecamp no matter where you live. For a Junior Customer Support Representative, this starts at $70,000.

Our benefits are all aimed at supporting a life well lived away from work. None are about trapping people at the office or cajoling them into endless overtime. Just the opposite. We’re all about reasonable working hours, ample vacation time, summer hours, fitness, wellness, food, education, and charity. See the full list.

If you want to join Ashley, Chase, Chris, Elizabeth, Jabari, James, Jayne, Jim, Joan, Kristin, Lexi, Merissa, Shanae, Sylvia, and Tony in making our customers happy, please apply!

How to Apply
Introduce yourself to us as a colleague. Show us your future here! We value great writers, so be yourself, be creative, and take your time with the application. There’s no prize for being the first to submit! Stock cover letters won’t do. Tell us why you want this job. Tell us about:

  • why you want to work in customer support.
  • why you want to work at Basecamp and not somewhere else.
  • a description of a great customer service/support experience you had recently, and what made it great.
  • a time you taught yourself a new skill to complete a job or project.
  • a guide to making your favorite meal.

Then, pick three of the customer questions below and answer them like you would if you worked here (hint: at this point, we value tone and style over correctness):

  • Does Basecamp 3 offer time tracking?
  • Can I create recurring events in the Basecamp calendar? What about recurring todo items?
  • Do you offer 2fa for signing in?
  • How do I work with clients in Basecamp 3?

Click here to apply. We’re accepting applications for this position until July 5. We’ll let you know that we’ve received your application. After that, you probably shouldn’t expect to hear back from us until after the application deadline has passed. We want to give everyone a fair chance to apply and be evaluated.

We’re seeking fluent English speakers/writers to work with us to answer customer inquiries via email and phone during these hours:

  1. Monday through Friday 9am-6pm CST
  2. Tuesday-Saturday 10am-7pm CST


We’re a remote company, so your location isn’t as important as your fit to the role. That said, we do prefer that your daytime hours coincide with your working hours so as to avoid night shift burnout. Don’t forget to tell us where you’re located!

We look forward to hearing from you!

The Support Side of Downtime

There used to be a panicked feeling that would set in when we’d have any sort of outage or issue in Basecamp past — that stomach-dropping, heart-palpitating, sweaty-palmed feeling. But on November 8th when I awoke to a 6am text spelling out Basecamp’s downtime, I wasn’t worried. Before I finished reading the full text, I remember thinking, “Oh, they’ll have it sorted out before I can finish making coffee.” But as I continued reading and began to understand the estimated downtime to be at least two hours, my adrenaline hit.

The first thing I wanted to do was check on the support team. Were they in panic-mode? How sweaty were their palms? How many customers had they talked to already today? How close to capacity were they?

And by the time I received the alert and logged on (coffee brewing while I said Good Morning, thank glob for remote work), Basecamp had been in read-only for about 30 minutes, three times my prediction. Despite the stress of a lengthy downtime, knowing that we’d have a few hours of this status allowed us to settle in and accept our predicament. We had time to get into a flow and trust ourselves to talk our customers through this.

Really, what I realized when I logged on was that everything was absolutely under control on the support team. And of course it was: for the past two years, our team has been conducting crisis drills with each other. Once a month, we rotate responsibility for these drills and each person is responsible for coming up with their own style of drill. They’ve become quite the gif-filled, fun time! We work from a playbook (hosted on GitHub in case Basecamp is down) that acts as a living document we can update as-needed. We’re currently in the process of using our experience from the read-only outage to revamp and reassess the playbook to make it even more accessible, comprehensive, and succinct — no small task, mind you!

Keep reading “The Support Side of Downtime”

People, Not Robots: Bringing the Humanity Back to Customer Support

(Adapted from a keynote I gave at Lean Digital Summit in Lisbon this month.)

Good help is hard to find. I dread calling the credit card company, the phone company, any service provider, including and maybe especially SaaS companies. I anticipate talking to someone who is poorly trained, under-paid, powerless, and miserable. I anticipate their frustration rubbing off on me. I anticipate arguing to get my needs met. And that’s if I can even get a real human to talk to me. The people standing in the way of good help aren’t the customer support representatives themselves, though. Corporate culture, the bottom line, and rotten support for service roles has ruined how folks get the help they need.

I’m not alone in this. I’m not the only consumer who approaches support defensively, with their hackles up. Before we dig in, I want to tell you about a customer of ours — let’s call her Nancy — who, like me, had low expectations. She wrote to us asking for a lower price (which we didn’t have).

One of our reps, who has been at Basecamp for almost five years, wrote her back to politely tell her that we don’t have any lower plans to offer her.

Here’s what they wrote to Nancy:


Her response back was a little bewildering:


Three words! A sentence fragment! End of transmission. I saw this and recognized something interesting. Nancy was replying as if she were on hold with an automated service: Say ‘Account and billing’ for our accounting department. Say ‘Technical support’ for our technical department. I’ve been greeted by too many of those automated services and have more than once simply repeated the word “Human” until a person got on the phone with me. I swear, it works more quickly! Anyway, I recognized this in Nancy, so I jumped on a call with her. She immediately confirmed my suspicions and told me that she thought that the person who originally responded to her was a robot — and she then read the whole email to me in a robot voice to further her point. She also told me that because she thought she was speaking with a robot, that her three-word response was an attempt to get the robot to understand her. In short, she was speaking the robot’s language. To her, Basecamp was nothing more than beeps, algorithms, and machinery. We were no longer a group of humans with families and hobbies and struggles — we were machines that didn’t deserve even a full thought.

So how did we get here, to this point where our customers assume we are not even human? This was Nancy’s first interaction with us, so she had no context or history with us that would have lead her down this inhuman path — something else, outside of Basecamp, made her believe robots are the general first responders. We all know that capitalism has made the bottom line more important than the people. We need to reject these late capitalist temptations in order to protect our customers, our people. The people are why we’re here, the people pay our salaries, the people use our products. Don’t be fooled into thinking that anything other than people can support your customers.

Nancy, like myself and so many of you, drew from her previous experiences with customer support. So many companies put up some automation, a chatbot, some AI that ends up standing in the way of customer service and support. Nancy, by the time she emailed us, was already fed up with this culture, this treatment. Frankly, I’m fed up with it too. I never want to sit on hold listening to shitty music, pressing menu buttons, entering my account ID. Like Nancy, I want to talk to a human. I want us to get to a place in our industry where I know that when I contact a company, I’ll speak with a well-trained, cared-for human.

Because I live by the Golden Rule, to treat others as I want to be treated, I need to formalize how I want to be treated in order to better help our customers. What do I want? I want to talk to a well-trained, compassionate, and intelligent person when I have an issue. I have never in my life wanted to work out a problem with an ill-informed person. I never want our customers to feel that way about us: either that they cannot get a human to speak with them or that the humans who are speaking to them are simply unhelpful. Place yourself in a compassionate position — how do you want to be treated when you need to contact a company with an issue? What’s your ideal scenario? Start compiling your values so that you know what’s important to you.

Once you’ve figured out how you want a company to treat you, it’s time to look in the mirror. Are you treating your customers the way you want to be treated? Would your friends and family receive decent help from a decent human? Would you rest assured knowing your neighbor would be treated compassionately and timely if they needed help from your company? To put it shortly, are you proud of how your customers are treated? Does your company stand up to your own expectations?

If not, that’s ok. I want to help.

Now that you’re coming to grips with your own values and expectations, it’s time to open up a direct line of communication with your customers. Not an answering service, not an auto-reply, not an automated recording or menu, no bots, no AI. Figure out what you can manage. Email is the best way to gauge this.

Here’s what our support page looks like. It takes one click to get here from our homepage. We’re not hiding behind a “contact us” link at the very bottom of a page.


If you scroll down, there’s a text box below this that you can fill out to send us an email that goes directly to support@basecamp.com. We also show you roughly how long it’ll take for us to respond to you. On a normal day, we answer 100% of emails within an hour of receiving them. 90% of those, however, are answered within 30 minutes.

That quickness, that attention, didn’t happen overnight. It was an iterative process that took about a year or two. We kept adjusting our methodology, each time failing a little better. When I started at Basecamp, we had four people answering emails. We all lived in the same timezone and worked roughly the same hours. At 8am on a Monday morning in Chicago, we’d have 600+ emails waiting for us. We rarely answered an email on the day it was received. Now, we have fifteen people stationed from West Coast US to East Coast Australia. We answer emails 24/7, save holidays and company meetups, with folks working roughly 9am-5pm five days per week. No one works in a call center. We train and support our own employees. We are connected to each other through Basecamp. Our team is the face of Basecamp.

I’m showing you this so that you can see how easy it is to talk to someone at Basecamp. We’re not hiding behind a device or a bot that’s trying to convince you that we care. We actually do care. We really do care. We know that our customers want to talk to us. They don’t want to wait on hold or have some AI device convince them that their problem is simpler than it really is. They want our expertise, our consult. When I call our customers, they aren’t asking me Yes Or No questions — they are giving me their stories, their narratives. They want me to understand their daily workflows and needs so that I can consult and problem-solve with them. I want to help our customers succeed — hell, it’s in my own best interest that our customers succeed not just at using our product but at their business so that they can continue to pay us to use our product. Part of helping them succeed is hearing their stories. When people can speak their truths aloud, then they are better able to process those truths. That means that when we give our customers the opportunity to speak to us, to tell us their stories, then they understand their workflows better. If you understand your truths and workflows better, then you can do better work. When you employ a bot or use an automated service, you’re sending the message that you’re too good to talk to your customers yourself, that they don’t deserve your time or patience or thoughts. Your customers want to talk to you, and you should want to talk to them.

Let me show you just a glimpse of the feedback we get at Basecamp after we have conversations with our customers.


So, you see that our customers (who aren’t different than yours) want to talk to a real human. A real human! They want to have a real conversation with another person. It’s not just that they are happy that they got to talk to another human — it’s that they are surprised that they did. Like Nancy, they assumed we were robots. Why? Because so many companies have failed them, treated them like a burden so that they learned robots are now being employed to help customers. This happy surprise that our customers get after realizing our humanity isn’t exactly a good thing, it’s not exactly flattering. The bar is so low that all we have to do is be a real human. What we’re doing at Basecamp isn’t ingenious. We’re simply understanding our own capacity for answering emails (60–75 per person per day) and doing that in our own voices. We’re simply allowing a team of people to have human conversations with our customers. It’s sad to me that our fellow humans expect so little from us. We only have ourselves to blame!

Check out this hilarious clip from the latest season of Bojack Horseman, in which one character is struggling through her day and needs help from a customer support rep. Diane is carrying a lot of emotional baggage with her and needs a human touch, someone who can empathize and alleviate some of that burden. She’s instead met with a robot.

It’s funny and we laugh (it’s dystopian but honestly not all that absurd), but this is a daily reality for so many people who simply need a human conversation, someone to guide them through a difficulty (even if that difficulty seems frivolous to us). A harsh reality played out here is that, too often, service providers like this are not trained to actually help a person in need.

It’s not just that a human conversation is what our customers want and deserve. Our relationship to our customers should be more symbiotic — we need just as much from them as they need from us. Sure, our needs are different, but think about how we know to grow our product, where the holes are. At Basecamp, we talk to our customers. We interview them. We listen to their feature requests, their rants, their raves. We don’t simply look at data and clicks (we do that, too!), but we also have real conversations with real people. Real humans!

It may seem cheaper to employ chatbots and automation, and that’s because it is. It’s not a good thing when cheap is synonymous with flimsy. You’re sacrificing intel, product knowledge, connection, and culture. It’s not worth the sacrifice. Your human support team connects daily with your customers, your customers who not only carry with them the money you need to stay in business but also the knowledge of how to improve your product.

So if customers want to talk to humans and if customers have product knowledge to glean, why are we seeing so many companies employ these automations and bots? One of the reasons is simply that we’re a society that’s obsessed with technology and profit and the intersections therein. Maybe we should all reread Frankenstein?! But I also think that a more compelling reason is that support teams, in general, are not treated with the dignity and respect that they deserve. That creates a culture of apathy and causes high turnover rates. Turnover frustrates managers and hiring committees: Why won’t people stay? This job is too draining. Let’s get bots who don’t complain and can’t leave. Apathy frustrates your customers who will find another service provider who can support them genuinely. I can tell you from experience that it’s not the work itself that makes people leave; it’s not the work itself that creates apathy — it’s the culture.

I’ve been supporting Basecamp customers for over seven years. Three others on my team have been supporting Basecamp customers for over seven years. Several others have been doing this for nearly five years. Collectively, our team has been supporting Basecamp customers for 64 years. It’s rare when someone leaves. So, I’ll repeat myself: it’s not the work itself that creates high churn and apathy in support positions; it’s how the employees are treated.

We all need to start placing higher value on the team that works directly with our customers. That means finding people who are preternatural helpers, first and foremost. What are preternatural helpers? People who enjoy problem solving with others. People who want to cull all sorts of knowledge for themselves and others. People who run to a problem instead of away from it.

Our team is made up of librarians, educators, personal assistants, fraud specialists, and IT professionals. All of these kinds of helpers, in order to succeed in this field, must be strong writers. You need a team of people who can communicate effectively in any form — that means that their written word must be passionate and strong. You need to hire people who can devise a way to gently say no, to kindly show a user how to accomplish a simple task without making them feel stupid. You need to hire people who are capable of handling difficult conversations with grace and candor. You need to hire people who can translate customer conversations into new product features or even new products themselves. Writers can do this because they can conjure these tones and emotions in strangers. Writers can identify, organize, and synthesize information for your customers to understand easily.

It’s a red flag to me when I receive bad support. The red flag is always for the company itself. It’s rarely the fault of the person trying to help me. Rather, these situations show me that the management, the company at-large abandoned this person. It’s a systemic failure, not a personal one, due to poor training, poor wages, no stake in the company (cultural or financial), no trust or autonomy. It’s honestly so easy to remedy.

Once you find the right folks (those polymath writers haha), you need to write and maintain effective and thoughtful training documentation that sets your new hires up for success. You need to constantly support your team. That looks different for each person you hire, so you need to get to know each person individually. Employees deserve regular reviews, regular feedback, opportunity to share their feedback, 1–1s, team chats. You need to listen to your team to know where you’ve failed so that you can atone and reconfigure. Let them guide you as much as you guide them. Your support team deserves competitive wages that can support them in a career — support work is not a stepping stone to another career; it’s its own career. They deserve retirement security, paid time off, childcare, healthcare. I could go on. If you want to treat your customers well, then you have to start treating your support staff well. If you value your customers, then you better value the folks who talk to your customers. Otherwise, you’re setting your customers up to fail and waving that red flag.

Once your team is comfortable and confident, you need to start giving them time away from the queue to process all the information customers gave them, to maintain documentation, to teach and interview customers, to learn new processes, to advance their skills.

Each support representative should have their own project for which they are responsible. On our team, each person spends one full day each week on working on Research & Innovation, a kind of Personal Development. They write help documentation, programming documentation, teach classes, interview customers, write blog posts, do social media engagement, learn programming, etc. I don’t decide what each person works on — I help them come to their own decision. This management style gives them a sense of ownership and dedication, a stake in a team so that there would be a true gap, perhaps even a systemic failure, if they left. Your support staff should not feel expendable. Help them feel essential by trusting them with their own passion project. Let your team show you better methodologies, better processes. Let them suggest protocol. Give them ownership in their work.

Try to remember that you started this process. You shifted the culture. You hired the right people, you trained them effectively. Now trust them. If you don’t trust them, then you took a wrong turn. People will soar when given the freedom. They will be grateful and hard-working, dedicated and loyal. They will challenge your company and make it a better place to work. I can’t say the same for robots.

Introducing Research & Innovation Days on Support

Customer support is a double-edged sword and can be both rewarding and draining. Helping people feels good, but constantly empathizing with strangers can get exhausting. We all hope that the good outweighs the bad, but that’s not always the case. When the scales are imbalanced and there’s stress at and about work, it’s easy to forget that work doesn’t have to be stressful.

Our team answers (mostly) emails and (some) phone calls seven days a week across four continents. Each person works 40 hours a week in Autumn, Winter, and Spring and 32 hours a week in Summer. But, 40 hours a week of nonstop emailing doesn’t allow folks to synthesize the data they just internalized to help guide Basecamp in an interesting direction. How can we analyze feature requests if our energy is zapped at the end of the day, the end of the week? How can we help shape tech support culture at-large if we don’t have time to benchmark or conduct research? Our team is comprised of fourteen badass thinkers with diverse backgrounds, so why aren’t we giving them space to think and collaborate? Finally, how can we introduce more calm into a stressed team?

Over the summer, I convinced Jason and David to let support stray from the 37signals mantra to “hire when it hurts,” which allowed us to hire two people when we thought we were looking for one. Part of my proposal included a schedule that set aside one or two hours per day for each person to work on something other than contacting customers, to be decided by self-selection. When Jayne, relatively new at the time, and I discussed what she could work on during her time off from contacting customers, I encouraged her to use her background as a research assistant to help guide her. That’s how we came up with the name Research and Innovation, or R&I for short.

There’s an element of trust in this type of structure that is essential if your team wants to try this out. Don’t micromanage people’s projects, but do offer suggestions and guidance when asked. I know that each person on the team will spend their time wisely and at their own pace. Ideas aren’t born from ether; they are born from consideration and formulation, research and comparison, all of which require time and space. If someone spends a day formulating an idea, then it was a day well-spent. It’s important not to question that judgment. (If you’re questioning someone’s judgment, then you should also be questioning their position at the company.)

When the time came to execute the concept, we decided to piggyback off our four-week summers: each support rep’s “summer day” during the rest of the year is now their Research & Innovation day. That allows for easier scheduling, gives us an idea of how the summer will look, and provides a full eight-hour shift of uninterrupted focus.

It’s been about a month since we introduced this structure to the team. Some folks do lengthier demos, teaching users. Some create industry-specific accounts to share with users. Some track and analyze feature requests. Some benchmark with other support teams. Some create content for our help documentation. For the record, these were all things we were doing before we introduced R&I. The difference is that instead of squeezing a quick pitch or a fast demo into a ten-minute slot between emails, we can now take our time to do our best work.

Beyond doing our best work, we’ve also noticed a shift in tone and attitude. The team is more involved in the goings-on at Basecamp. We’re happier, more relaxed, with better morale.

Here’s to a calmer 2017!

From Inbox Zero to Inbox Comes Second


Often, the work I do feels invisible. I’m not building a feature or designing a website. I’m ensuring that our support team (a sect of tech with an industry standard of high turnover) has the information they need, doesn’t suffer from too much burn out, and is empowered to make their own decisions. Part of my job this year has been to adjust our team’s culture: a shift that has often felt like repeatedly rerouting a ship’s course.

When we lost a successful, tenured employee to Help Scout last December, we suffered a bittersweet loss. Only a few weeks later did we abruptly lose a newer employee, which became a more challenging loss than anticipated. The combination of losing a long-term team member who shaped our team culture and experiencing a contentious departure by that newer team member hit our morale pretty hard. With shaken morale, we also had to work through the busiest time of the year with those two gone and a third person on paternity leave: we were working at 70% capacity at the height of busy season with a stressed-out team.

January is notoriously busy for us and is always a bit of a shock to the system after the lackadaisical holiday season when customers don’t write to us often. The sluggish season offers a nice break for us after another year of work and allows us to bond with each other and our families. Since customers aren’t writing to us, we seldom have a backlog and rarely a queue, which means we can respond to customers within minutes. November and December are often Inbox Zero.

Enter January. Enter 70% capacity. Enter low morale. Enter a swell from n emails to 6n emails. Enter an obsession with an idealized and impossible image of Inbox Zero.

Enter negativity.

Each day felt like a packed CTA train at rush hour in the winter: sweaty, steamy, and uncomfortable. We went from each answering 60 emails per day to answering 150 per day. I couldn’t spend any time on admin work since we were down three bodies, which meant I couldn’t even begin the hiring process until February. I was too busy to work.

Meanwhile, the team felt the pressure of Inbox Zero. Inbox Zero is an arbitrary goal; there will always be another customer email or phone call or tweet. Inbox Zero is a fruitless fight for control. It became an image that tied us to our screens, that swallowed any self-care practices we had instilled over the years. It also became a habit of treating our customers less like humans who needed support and more like screens to get rid of.

By March, we finally hired two new folks: Carrie and Elizabeth. We brought them to Portland and welcomed them to our damaged team by accidentally showcasing our stress. During a 1-on-1 with Carrie, she brought up how disappointed she was by our negativity and stress: we hired her to help alleviate stress only to pass our stress onto her. Carrie opened our eyes to our bad habits and the true depth of our low morale. Together, she and Elizabeth showed us their fresh perspectives and willingness to fight the negativity we had introduced them to. Without them, we might still be spiraling.

But, we’re still a work in progress. While we’re not where I want us to be — there’s some lingering negativity and stress — I see movement. Part of that movement has been to stop following the 37signals hiring standard to “Hire When It Hurts.” That doesn’t work in support. If you’re waiting for The Hurt to tell you to hire, then your perspective is off and you’re expecting your team to carry the weight of another workload. Instead of carrying extra weight, we’re working on creating space for personal projects, better communication, innovation, brainstorming; if you can’t breathe, then you can’t think.

So, during the summer, we hired Jayne. Last month, we welcomed Esther and Janice. Last week, we promoted Natalie, a senior support employee, to help manage the team (we’re now at a total of 14). We hired more and created a new managerial position to help open that much-needed and well-deserved space for the more-tenured employees to relax into.

And, while we lost two people last year, we gained five this year. That’s five fresh perspectives to hold us accountable to our high standards while reminding us to remain human and keep ourselves first: Inbox Comes Second.