We work very collaboratively and pair-programming is a vital part of our culture.

Somewhere between 80% and 90% of our work is done while pairing. We pair program regardless of location, so whether you’re physically side by side at the office or on your own in the comfort of your own home, we’ll likely pair. We tried tools like tmate and saros for collaborative editing, but have also found that simple video calls with screen sharing work. The drivers share their screen and the co-drivers do their best to not interfere except for talking. If anything, remote pairing has helped us become more disciplined when pairing! 😀

We enjoy being a cohesive team, even when we’re not physically coding. We eat lunch together, do a team breakfast each month, and regularly get drinks together after work. Our engineering team is also close to the other teams at the company. Every month, we do an information exchange and also meeting to touch base on what our company values are and discuss our company’s culture. Once a year, we also have team days where we visit a new European city.

We often think of ourselves as an elite sports team. It's always we, never me.

Let’s Do This is a collection of seriously impressive individuals, but we thrive as a unit and are willing to make personal sacrifices on behalf of our team members. Our team-first mentality stems from our shared love of exercise and the product we’re building, and a mutual understanding of fun. Everyone has a voice in big product decisions and when we’re not working, we go to the gym together, go on runs during lunch together, and enter races together, too.

Perhaps one of the best examples of how team orientated we are is our willingness to move across the world with each other. During Y Combinator, eight of us moved from London, UK to Palo Alto to make the most of the 3-month batch. We raised a seed round after YC, and four team members moved to San Francisco together to open the office. In the summer of 2019, we took the whole team (everyone from both London and San Francisco) to Cambridge, UK for an intense “training camp” where we more than doubled all of our top-line metrics in six weeks in the run up to our Series A. None of this would have been possible without a team that believed in each other, put each other first, and was willing to make personal sacrifices, like moving their lives across the world in pursuit of a shared dream.

Even as a distributed company on two continents, we maintain cohesion. We keep open communications and everyone feels like it is easy to reach out to anyone else in the company, regardless of their role or location. Early in 2019, we helped relocate a U.S. engineer, Connor, to London and also moved a UK engineer, Tom, to San Francisco. Our hope is that every engineer spends at least one week each year working out of their non-home office, and so far, many of us have spent up to six weeks doing so. Doing so helps us stay close to one another and feel comfortable making quick FaceTime calls to discuss cross-office issues when we’re not in the same city (a much better alternative than potentially misinterpreting written Slack messages anyway).

If you ask anyone at Let’s Do This why they work here, what they love most about working here, or which value represents LDT the most, the clear winner is always “the team.”

Autonomous product-area-driven teams

Angaza has five engineering teams: three in San Francisco and two in Nairobi. Each team has a high degree of autonomy, physically sits together, and owns internal processes such as daily standups and work tracking. Cross-team "working groups" bring together engineers across the company to solve common challenges and address shared concerns. The typical team has several engineers, a product manager, and an engineering manager. Together they own a broad area of functionality. For example, our IoT Solutions team owns everything from embedded firmware to time-series databases, while the Network Partnerships team integrates an ever-growing range of digital currency services.

We all succeed or fail together.

Teams jointly commit to deliverables and help each other achieve those goals. Since we offer so many products and services, coordination and cohesion among teams is crucial. We rely on good teamwork and synchronization to ensure we're not duplicating work or changing things that will have upstream or downstream impacts on other processes or products.

We utilize scrum meetings and quick daily stand-ups with team leads to sync up with relevant teams. Product and UX work across teams so all parties understand their role in the overall vision and stay aligned. We use Aha! for roadmapping and strategic product views and Jira for sprinting and executing on those initiatives. These products are “open” in that there is a common view and understanding to manage natural complexities.

Everyone on our engineering team, regardless of level, is expected to make decisions or contribute to them. Some decisions are routinely made at the team level (design patterns, open-source libraries, etc.) while others need to be made with more insight into cross-team or cross-product strategies, company goals, or industry trends and may be made by engineering leadership with input from relevant teams. For certain products, there are bi-weekly architecture meetings open to anyone who is interested. Not all decisions are democratic, but all team members have a say in how their solutions are built.

Billtrust promotes a "we all succeed or fail together" culture. People ask for help when they need it and generally everyone is willing to help, whether it be through code reviews, pair programming, mob programming, sharing lessons learned, or bouncing ideas off each other. The dynamic is different on each team, but getting to done is culturally and objectively a team effort. Since we have development teams in New Jersey, Colorado, and India, we use tools like Slack, Google Meet/Hangouts and Zoom to connect with one another. Our engineering teams work in “agile pods,” which have their own screen that can be connected to a Google Meet allowing remote teammates to join at any moment and have pseudo face time with everyone.

Individual contributor != I work alone.

We think about productivity at a team level, and not as much as individuals. People have different strengths, and we want to take advantage of that while investing in our weaknesses to make the team more versatile and robust over the long term. A huge part of why we all love working at Sparkswap is that we get to come to work everyday and collaborate with one another. We (Brad, Martine, Danny, and Trey) feel lucky to have found our tribe and we think this is by far our biggest (and most unfair) advantage. Our tribe is collaborative, we genuinely like and care about one another, and we’re all passionate about doing really great work.

We truly work better as a team than we do as individuals. It is common for people to “check in with the team” at various points on a project to get feedback and bring everyone up to speed. We frequently work in teams of 2 instead of the whole group. For particularly thorny issues during design or code review, we all think through the problem together. (We literally sit together around a whiteboard to solve it together.)

We are co-located in part because we think the high bandwidth communication (both intellectual and emotional) that comes with in-person working is worth the trade-off of losing some (many) candidates. It’s incredibly important to us that all new hires consider themselves to be a mentor, a good teammate, and an enthusiastic learner.

We’re a small and close knit engineering team.

We’re currently 10 engineers that are split into three separate teams that serve three different customers: we have our Agents Team, our Buyer Team, and our Platform team that builds and supports internal tooling that our company runs on. We take advantage of our current small size and make sure that everyone has a say in every big decision. (Something we hope to continue doing even as we grow.)

As one example of how team-oriented we are, we recently rented a loft in Williamsburg and worked “remote” together for a week. It was our inaugural Tech Debt Refinancing Week where we walked through all of our products, identified anything that was a pain point, and improved or fixed it. Not only was it incredibly productive, but it was also fun. (We even made mugs for it!)

As a team, we also make sure to support one another in “picking your path.” Not everyone wants to follow a manager track, so we happily support engineers who want to work as individual contributors (ICs). And just because you don’t have plans to become a formal manager, there are also plenty of opportunities to mentor. We currently don’t have any junior engineers at Ribbon, but we’re excited and ready to bring on junior devs who are looking for senior mentorship in their first or next role.

We celebrate team successes.

It’s a reflection of how humble we are and what motivates us day-to-day. Team members will go out of their way to help each other, even if it means that their personal tasks will fall behind, so long as it is in the interest of the greater good.

We emphasize this by aligning the entire team around a common team goal and being fully transparent on how we progress towards that goal. And when we meet those goals, we celebrate as a team! Recently we took the entire team on a 3-day retreat to Whistler and went white water rafting. We have monthly social events where significant others are always welcome.

Another example is how we do our year-end bonuses, which are tied transparently to team objectives, rather than individual ones. In that way, either the entire team wins or the entire team loses!

Everyone is involved in the decision making.

As founders, we go out of our way to collect everyone’s feedback through monthly one-on-one meetings, surveys, and voting on Trello/excel, this includes office location, off-site activities, as well general company process improvements. We are open to hiring individuals who prefer to work alone. At the end of the day, it's about getting the work done, and finding joy and meaning in the work that you do, regardless of the personalities around you. I want to attract candidates who want to take on a lot of responsibility at a growth stage company, is emotionally mature, and wants to work in a drama free environment.

There are no solo projects at Lever.

Everything we do is team based. We have two pairing rooms (called Pairadise), which are always occupied. We focus on aligning around team goals throughout projects, which means we’re incentivized to give and receive help (pairing, mentoring, whiteboarding, unblocking tickets, etc.) over focusing on solo hero work.

Collaboration also prevents us from creating silos of knowledge. It facilitates information sharing and there are many “game-changing” instances where one person’s good habits or use of a awesome tool gets shared across the team to everyone’s benefit.

Above all, we are big believers of succeeding and failing together as a team. We celebrate feature launches with a physical trophy ceremony where the team presents who built what and why. They then place a small token that represents the project in a glass case with white gloves, music playing, and all the pomp and circumstance a feature release deserves.

We are a flat organization with no managers.

We’re currently too small of a team to worry about titles. In the not too distant future, we’ll have more clearly defined roles and a hierarchy that fits our company culture, but for now, we are one team. We have deliverables and company goals that we all work towards together. The way we plan and operate is heavily collaborative. In the rare cases where we don't have a consensus, we operate under a "first among equals" style where the CEO acts as final arbiter.

Meet our team:

• Ryan (Cofounder)
• Ben (Cofounder and CEO)
• Jason (Software Engineer)
• Eric (Director of Engineering)
• Stephanie (Cofounder, Product and UX Design)
• Mike (Cofounder, President)

You can also learn more about who we are on our team page.

Each team works together to determine what their team values are.

A lot of what we do at Box is team-centric. For one, even though we’re becoming a large company (~300 engineers), we still hire into individual teams rather than hiring into the greater organization and then later placing people on teams that need more resources. Once you’ve joined your team, you’ll likely do team building activities to help you and your teammates assess how the overall team is doing. We have different work experiences, perspectives, and working styles and no two teams have the same dynamic. It’s important that we draw from our past experiences and share ideas, practices, and processes to elevate the team while also making sure to learn from what didn’t work. We are incredibly team oriented in this regard. Engineering managers also work together to share knowledge and help one another build engaging, cohesive team cultures. What is the best team you’ve ever been a part of and why? We want to know.

We build teams to have strong ownership and accountability.

Our engineering department is split into three distinct teams: Product, Platform, and TechOps. The Product Team owns customer facing features like adding API endpoints, new protocol support, and our developer dashboards. The Platform Team develops and maintains robust, scalable, and easy-to-use abstractions in support of the Product Team. Our TechOps team creates, manages, and ensures the smooth and secure operation of our technical infrastructure.

Each team has a team lead who both decides on its process and how to empower each team member to have an active voice on important engineering and product decisions. The teams hold regular retrospectives to reflect on what is and is not working well.

Being at the heart of Dublin City, our team has a multi-cultural mix with employees with different areas of expertise.

One of our strengths is having an open and clear communication channel between different teams. The Technical and the Business teams are both just a stone's throw away from each other. We try to eat lunch together, and also have monthly team dinners so that we can bond with one another. While we do provide the facility of working remotely, we prefer working together as a team.

All of our product teams are formed around a ‘triad’: a PM, lead engineer, and designer.

We follow the Inspired model from Marty Cagan to create cross-functional teams centered around specific business objectives. Every triad has at least three people (and their supporting casts behind them) and all stakeholders are equally valued and included from ideation to product maintenance. By having these three perspectives represented across all stages of the product life cycle, we’re able to build better products, faster. We also place an emphasis on testing and failing quickly, which enables us to move through multiple iterations with speed: once we find something that works and verify it by data (we A/B test, do small rollouts to subsets of users, and use Pendo to track events), we build it to scale.

Our triad model is wonderful because it also guarantees a tremendous amount of exposure to every team member: product managers understand technical challenges, engineers learn design processes, and designers can watch how user needs translate during problem solving.

We believe that clearly defined goals – combined with awesome people, true empowerment, and nearly total autonomy – create the best results.

We encourage folks to work in ways that makes them and the team strongest and most productive. We embrace the idea that everyone and every team has its own unique working style. We have a "how to work with me guide" folder. New hires read through the folder when they join and also outline their personal working style. To respect each team member’s time, we avoid unnecessary meetings and ensure that any meeting we do hold is run by a meeting owner with a clear agenda.

We have collaborative, cross-functional teams comprised of designers, product managers, and engineers.

As of August 2019, we have three overarching themes to which smaller teams of 3-6 engineers each belong:

• Product: LightStep’s several product-themed teams build towards better features, usability, and value for our customers. Check out our demo – it’s one of the many experiences we’ve been working on that ties together all of the other work our teams do!
• OpenTelemetry: The OpenTracing-OpenCensus merger into the OpenTelemetry project comprises a critical piece of LightStep’s work in observability overall. Engineers on this team are focused on the open source ecosystem. Their work can vary from hosting podcasts, giving talks at developer conferences, and building functionality on our open source roadmap. We also look for language specialists for this team to create and support client libraries (e.g. iOS, Android, Python).
• Platform: LightStep’s platform engineering theme is comprised of two main initiatives – one in site reliability, and the other in building a unified data/metrics platform.

In addition, any engineer can propose a new project, which goes through a selection process. All projects typically start with a conversation with the product manager (PM) on your team, followed by a collaborative drafting of a 1-2 page brief that outlines the problem space, potential impact, and engineering effort level required to complete a solution. Briefs are then grouped together, reviewed, and further vetted by the entire team, including the PM, EM, engineers, and designers. During this process, we have both verbal and written mediums for anyone to provide feedback. Ultimately, the teams make a collective decision to work on the highest impact projects.

Even our interview process reflects how collaborative we are. Every engineering candidate meets with panels of two team members who focus on productivity and teamwork. Having a pair of interviewers lead each onsite panel helps reduce bias in the hiring process and more accurately assess a candidate’s ability to collaborate and work with diverse perspectives. Using the feedback from both interviewers, we can continuously reflect on and improve our interview practices. We’ve heard from candidates that they also appreciate this setup, since more people in the room adds greater perspective and generally yields more interesting conversations.

Teams are how we organize: Our work. Our communication. Our meetups. Our Impact.

When our founder and CEO Matt Mullenweg talks about the Future of Work (as he does in his podcast, Distributed, and in a recently published TED talk) he shares his belief that distributed teams are a big part of that future. And we know, from years of hiring and from our recent user research study on hiring, that talented and diverse candidates might be just as interested in pursuing a role with a specific team, versus simply pursuing a specific role.

We go to great lengths to help each team in our company continuously iterate, share feedback, and meet goals. All full-time Automatticians are members of a certain team, and work as closely with their teammates as possible on all tasks. All teams have areas of responsibility, but can choose to go outside them. Teams have names that aren’t descriptive, because teams aren’t limited in the ways they can influence any part of the company.

Automattic teams also have their own unique rituals, from how they hold standups in Slack with geekbot or take turns writing biweekly updates for other teams, or how they kick off projects and celebrate successes.

Teams are so central to how we work that our Team Leads are less managers, and more leaders. They help employees cultivate opportunities for impact and growth, while staying on top of the vision and goals for their team and all of Automattic. Developer Team Leads spend time with extra coaching sessions, biweekly leads roundtables, and get-togethers at relevant lead dev events.

In fact, we’re so constantly iterating on the tools that help our teams perform well together that in 2019 we launched Happy Tools, a suite of products for handling scheduling, customer support, and other things that help distributed teams navigate the future of work.

We have a strong founding team and recognize the importance of collective experience and skill sets.

Together, we have a wealth of knowledge in cybersecurity and it is our cumulative experience that gives us an unfair advantage as we take on this massive market. Managed Security Service Providers (MSSPs) already represent ~20% of total global security spend and the global Managed Security Services market is projected to quadruple to $101B by 2026.

Learn more about who we are and please reach out if you’d like to help us build a first-of-its-kind AI platform to manage cybersecurity holistically!

• Dr. Sameer Bhalotra (Co-Founder and CEO): Sameer previously worked as Co-founder/ CEO of StackRox, as a cybersecurity executive at Google, as COO at Impermium (acquired by Google), and as a board member for numerous security startups. He has served in various roles in government including Senior Director for Cybersecurity on the National Security Council staff at the White House and Cybersecurity & Technology Lead for the Senate Select Committee on Intelligence.
• Ed Gardner (Co-Founder and Head of Product): Ed was previously a Senior Program Manager for Enterprise Protection and Detection at Microsoft, and Senior Technical Program Manager for Consumer Data Protection at Amazon working on a content classification and data loss prevention service. He spent nearly 10 years at Akamai Technologies, working in various roles including Senior Service Architect for Platform and Security, Service Architect for Cloud Security Solutions, and Senior Program Manager.
• John Nurczynski (Co-Founder and Head of Strategic Operations & Business Planning): John was previously team lead for Customer Success at Arceo Analytics and Operations Manager at StackRox, two rising security startups in Silicon Valley. He was Senior Analyst within the Investment Banking Division at AGC Partners, specializing in Cybersecurity and Enterprise Software. John is also a former Senior Associate within the Wealth & Asset Management Division at Ernst & Young.
• Jerry Heinz (Head of Engineering): Jerry previously led NVIDIA’s GPU Cloud for AI/ML, Professional Graphics, and Gaming. Jerry is the former Head of Advanced Gaming Technologies for AWS and led Amazon AppStream, Amazon Lumberyard, and operations for Amazon Game Studio. Over his career, Jerry has led engineering at multiple startups in online-dating, e-commerce, member management, education, and mortgage banking.

Good humans are core to our company.

What distinguishes us at Jane is that we’re truly a cohesive team comprised of good humans. Some of us like to surf together (Pleasure Point is just half a mile down the road), play music together, and the list goes on. We also have a company-wide happy hour every six weeks. Our friendships extend beyond work, and we think that speaks to how bonded we feel as a team. It’s akin to being on a sports team really.

We all have different lives and fully support one another. Some like to arrive at 8:30am while others arrive at 10:14am for our daily 10:15am standup. Some are regular cannabis consumers while others have never consumed it before in their life! Many people take a work-from-home day once a week, and we’re always open to flexible scheduling. (Need to pick your kid(s) up from school? Go for it!)

We purposefully design our onsite interviews to be as human-centered as possible and we’ve gotten a lot of positive feedback: “That was unlike any onsite I’ve ever experienced!” is a common refrain. We have candidates meet with as many team members as possible, from engineering and design, to C-suite execs, to get a feel for what it’s really like to work here. The more exposure you have to the people at Jane, the better. After all, you’re not just interviewing for a job, you’re joining a team.

At the end of the day, we all pitch in to get things done and feel collective ownership for what we’re building. All accomplishments are co-accomplishments. 🙌