Below is an article originally written by Rose Jen, Product Manager at PowerToFly Partner CircleCI, and published on July 26, 2019. Go to CircleCI's page on PowerToFly to see their open positions and learn more.
Hi! I'm Rose Jen, a product manager at CircleCI. I've run a number of interviews here at CircleCI, and the #1 question I get asked is "What is your experience with the distributed culture at CircleCI?"
I have worked before in companies that allowed remote work. They've offered their teams access to tools to make remote working possible. I've also worked on teams which start out as colocated, but have become distributed by necessity as team members move. Often in these cases, the folks working remotely become increasingly left out and distanced from the rest of the team. Given those experiences, I was initially hesitant about working on a distributed team, specifically with concerns that communication could be difficult, or worse, that I might feel disconnected from my team. However, during my time here at CircleCI, I've noticed that the company's deliberate work on building an inclusive distributed culture put many of my fears at ease. And through this experience, I've seen the difference these efforts make, and learned that merely allowing employees to work remotely isn't enough.
While CircleCI has been a distributed team since the beginning, we do have an official headquarters in San Francisco. To support our teammates all over the globe feeling fully connected, included, and empowered, we work hard everyday toward building a "remote-first" culture. The difference between a team which allows remote work, and one which strives to be remote-first may sound like a technicality, but in practice makes a world of difference to our team members, regardless of where they are. Remote-first means that remote employees are not an afterthought. Being remote-first means being intentional about not just the tools that are used, but also how we plan a company culture to be as inclusive as possible of remote workers while allowing everyone to be the most productive.
For anyone considering joining us, or for those who are looking to foster a remote-first culture in their own organization, here are 5 ways of making it work:
Videoconferencing by default
We rely heavily on videoconferencing at CircleCI – it's quite impossible to go through a workday here without some sort of videoconferencing (we use Zoom). To be maximally inclusive, we are very specific about how we use videoconference tools. First, as a company we invest heavily in hardware and software that makes our reliance on vidoeconferencing work. Every single conference room at our office is fully video-enabled. On the flip side, we expect our employees to have access to high speed internet connections, and to work from a location where they can be clearly heard and seen – being unable to hear someone on a call won't cut it. The success of this tactic relies on everyone's participation. We also made the choice early on to grant every employee full access Zoom accounts – so every team member feels empowered to call meetings, whether large brainstorms or ad-hoc chats.
Additionally, we have practices about how we disseminate information from video meetings. We include a Zoom link with every event invite, so that no matter where the participants are, they can join. At CircleCI, we have a general rule that if there are team members in various time zones who won't be able to attend a meeting, we record the meeting and make it available for viewing at a later time. This gives folks in all time zones the flexibility to manage their day the way that best suits them.
Accessible, structured, and documented team meetings
At CircleCI, most product development teams have a variety of weekly get-togethers: planning meetings, daily standups, brainstorms, design reviews, and retros. These are all done via videoconferencing. Depending on the type of meeting, we also utilize digital tools (Google Docs, for example) that everyone has access to in realtime, through which we facilitate discussions and document decisions as they're made. For example, we use Google Docs to outline brainstorming or retro discussion topics. For planning meetings and standups, we go to our shared Jira board that shows our deliverables and progress, so that everyone is following along in realtime while the discussion is happening. For design reviews, we use Invision, a design prototype tool, that allows designs to be shared across the team and allows team members to provide comments. These have helped us have productive meetings anywhere the team is. I personally don't miss cramming an entire team into the same meeting room, and I'm certainly glad to be freed of the struggle to find available meeting rooms.
Document, document, document
Who doesn't love good documentation? In a remote-first environment, pay special attention to physical artifacts that may disadvantage team members who are not colocated with you. There will always be things that occur in realtime (quick sketches, Post-its) when a few folks are in the same room, but we take efforts to document and share the results of those IRL brainstorms with the team at large and take lots of pictures of any diagrams, roadmaps, and other outcomes, so that everyone can access them afterwards. Find ways to ensure that remote team members aren't just listening in, and look for ways they can participate in realtime. Zoom offers collaborative whiteboarding that you can do from inside a conference call. Even with the best tools, this process will often still be imperfect, and therefore requires mindfulness and some creativity from everyone involved.
No hallway conversations
This doesn't mean that you can't talk to your coworkers face-to-face or around the watercooler. But it does mean that if you have work-relevant conversations that are not digitally recorded, they should somehow get recorded after the fact: put a summary in chat, write up a short document, or find another way to make sure that information can be referred to by remote team members. We also encourage our team members to have impromptu "hallway" conversations over video, whether it's to ask a question or to quickly get the team aligned on a specific topic. Regardless of location, there are some things only a quick 1-on-1 chat can clear up.
Plan together time
Whenever possible, bring your distributed teams together! There's something really nice about being able to spend time with your far-away coworkers in real life. At CircleCI, we plan for teams to meet at a location together at least once a year. Departments do the same as well. It'll require serious logistical planning and a monetary budget, but it will be well worth it as a team-building investment.
What I've shared isn't a definitive guide to operating a distributed company – just some things I've noticed at CircleCI that have made a difference for me and my colleagues while working on a distributed team. It's important to mention: we are always re-evaluating our processes, and looking for places to refine. Things will change. For example, now that we are expanding more globally, it has changed the landscape of what being distributed really means (for example, getting a team together whose members are 1 hour apart vs. 8 hours may mean folks in San Francisco scheduling meetings earlier in the day to accommodate the schedules of team members across North/South America and Europe). These changes have pushed us to change the way we use our tools, and given us opportunities to continue to iterate and improve. Overall, if you're in an organization looking to become more remote-friendly, we encourage you to keep an open mind and experiment to find what will work best for you.
Below is an article originally written by Gillian Jakob Kieser at PowerToFly Partner CircleCI, and published on June 11, 2019. Go to CircleCI's page on PowerToFly to see their open positions and learn more.
A common question we hear in interviews is "What's it like to work remotely at CircleCI?" Well, it's many things, including wonderful, supportive, and, at times, challenging. As we grow our Engineering organization across Europe this year, we expect more folks to be curious about what it's like to work here on one of our distributed teams. We reached out to some of our engineers to find out what their experience is like, so you can hear it directly from some of the folks you might one day be working with.
Perspectives from the team
What do you enjoy about working remotely?
"The flexibility. Flexible hours mean that I can spend time with my family that I would otherwise spend commuting, and that my kids would be in daycare for longer." -Marc O'Morain, Senior Staff Engineer
"I am thankful for the team's ability to continue progressing on work while some of us are asleep. Our team's timezone distribution means I have on-call cover for my evenings and early mornings." -Dan Carley, SRE
"I appreciate that my team (and our company as a whole) make a clear effort to think about what it means to communicate asynchronously. People realize how crucial it is to think about the way we interact, and folks do the work." -Liene Verzemnieks, Support Engineer II
"I enjoy that we are all able to have flexible lives! Our team is passionate about our work and our mission, and I love seeing what everyone is doing outside of work (traveling, working out, cute babies, etc.). I feel extremely supported and cared for by everyone." -Jacque Garcia, Software Engineer
"The ability to make my own schedule. Working mornings/evenings with gym-lunch-power nap in the middle of the day has been a game changer." -Justin Cowperthwaite, Engineering Manager
What makes your team successful as a distributed team?
"We are all very understanding of each other's goals – we communicate regularly on what we are working on and accomplishing throughout the day, and have crushed difficult tasks together. Our team is passionate about our work and our mission." -Jacque
"Distributed communication means writing things down, which helps everyone: people returning from sick leave or holiday, as well as new people joining the company. We use our team Slack channels so that everyone can contribute to answering things we know or learning things we don't know." -Dan
"My team has been open to experiments over time (e.g. two weekly team meetings so everyone gets at least one in-person, real-time conversation with teammates, even if it's not everyone at once). We put a high priority on being kind to one another, and although we don't always talk about it as such, and we put a high priority on psychological safety (e.g. it's okay to ask "silly" questions, or not know the answer, or have feelings). The combination of regular conversations in a variety of formats, plus the CRITICAL glue of Small Hands (periodic in-person team gatherings), really does something magic." -Liene
What advice would you give new remote employees?
"Be open. The people are really nice and supportive." -Dan
"Make sure you plan out breaks and be intentional about creating social interaction with your coworkers (since it might not happen organically)." -Justin
"Get out to the office as much as you can, and for as long as you can when you first start. Try to meet as many folks in person as you can." -Marc
"Overcommunicate: err on the side of asking questions or reaching out (you can't stumble into water cooler conversations, so whatever you can do to create opportunities for communication is extra valuable). Also, define work/not-work, whether that's time-based (e.g. I work 8:00 - 17:00, and then I stop) or computer-based (e.g. this is my work computer, this is my personal computer)." -Liene
"It can be challenging to deal with uncertainty. When in doubt, get people involved." -Jacque
Tips for distributed teams
We've been a distributed organization since the very beginning. As we've grown, we've picked up quite a few lessons along the way (for example, on communicating asynchronously, pairing remotely, and distributed onboarding). For those considering joining our team, a well as those growing their own distributed teams, we'd like to share some of our favorite distributed team tips:
- Use asynchronous communication where possible when working across timezones, and make the best use of any synchronous communication time you have.
- Converse in common team channels rather than Direct Messages.
- Record meetings.
- Say hello and goodbye to your team each day to indicate when you're in/out.
- Make your working hours visible on your calendar, so it's clear when you're available and working.
- Leave summaries in Slack threads after team discussions or huddles.
- Pair often.
The best methods for working on a distributed team, whether at CircleCI or elsewhere, will vary by the team, the individuals on it, and the work you're trying to do. We encourage you to communicate with your teammates, test things out together, and overall be patient. Building a happy and successful team, especially a geographically distributed one, takes time, but having processes that work is worth the investment.