I think most people would be happier if they had more flexibility to choose when and where they work. Sometimes that just means coming in late or leaving early without the hassle or guilt. For some, it means being able to work remotely for short periods of times.
In tech, it's common for companies to support flexible work arrangements, but it's definitely a spectrum. From flexible start times to fully remote companies, see how different engineering teams have built their culture around flexible working arrangements.
We trust our employees and their judgment. While we expect you to be there for our daily scrums and weekly meetings, your work schedule is entirely up to you and your teammates. We try to keep things small. Our typical team consist of 4 developers and a product owner. We work at one project at a time.
You can work either from home or at our fully equipped office space in Gdynia. It’s all about preferences. Currently, one of our developers is working fully remotely. On the other hand, other team members prefer to be in the office every day.
1 Open Positions
We work from our home offices, at cafes, and while traveling. We are a distributed team that believes working hours should be the times you want to work, and that you only need to work the hours needed to deliver your responsibilities. (Of course, you should let people know when you’re going to be unavailable.) We hire hard-working, passionate people and give them autonomy to manage their time and balance their lives so they can feel happy and engaged.
Having a distributed team has been extremely advantageous for us. It allows us to expand our search for talent across the world, gives us around-the-clock coverage, and forces us to focus on creating and maintaining tools and processes that allow for excellent communication. By joining our distributed team, you’ll have co-workers with diverse backgrounds who provide multicultural perspectives on our team and insider travel information.
We have unlimited paid time off and encourage healthy breaks from work to recharge. Because we do have a distributed team and we’ve invested heavily in the tools and processes to support it, even those of us at HQ (in San Francisco) benefit directly in that working from home or while traveling is easy; we’re set up well for it! Ps. Our SF HQ office is pet friendly.
In addition to our main office located just outside of the city, Relay provides our engineering team a co-working space in downtown Philadelphia in order to create a flexible working arrangement. Additionally, we allow some engineers to work from home for a portion of their work hours to accommodate longer commutes. Family comes first here at Relay. A daughter’s basketball game, a son’s play, a family vacation, this stuff matters, so that’s why we try to create a very parent-friendly work environment through flexible work schedules and healthy maternity and paternity leaves for employees.
At Hash, you are free to work at any time in any place. We believe this is a factor that helps people reach their peak performance.
We think that we shouldn't push the work onto people, so we don't organize "sprints" or any sort of "periodical synchronous team ceremony." Instead, we coordinate the work asynchronously so people can always pull a task to do any time they want, and we do our best to maintain development organic and organized.
People collaborate organically (two people will decide how they work best whether that’s via email, Slack, or ad hoc meetings), but we also have minimal structure to keep everyone on the same page.
On any given weekday, you’ll find engineers who are at the office at 9am and occasionally, some that stay until 9pm. Alex and Oliver (co-founders and engineers themselves) set the example by having different schedules and working from different places within the office or sometimes, from home. If you want to stake out in a private office one day and work from couch to couch the next, you’re more than welcome to. We purposefully do not have many scheduled, regular meetings so you don’t need to schedule too much around those. The best engineering work comes from providing some structure and some freedom so that you can decide what works best for you.
Engineers typically work from 9:30am to 6:30pm or 7pm, but that varies. Our main focus is on productivity and availability to engage with the rest of the team. Our headquarters are in NYC, but we have a distributed team with core members in Hong Kong and San Francisco. We prefer people to work on-site when possible, but it's not a deal breaker for us. Some of our core team members work fully remotely.
We work hard to accommodate the different lifestyles of our team members so that everyone is set up for success. One of our engineers commutes from New Jersey, so he comes in mid-morning and dials-in to our team stand-up. One of our co-founders leaves early a couple times a month in order to pick his daughter up from daycare. We want to ensure that everyone is empowered to do their best work.
The only mandatory scheduling revolves around our core cadences: making your team’s weekly meeting and making our quarterly all-team retreats. All other meetings are ad hoc. It’s common for team members to work on a variety of schedules including surfing at lunchtime, or taking a personal day.
Labor Automation Cloud Platform
New York, Toronto, and Lexington (just outside of Boston)
While there is a slight bias towards having people at the office to take advantage of high-bandwidth face-to-face meetings, it’s certainly not a requirement. Some engineering team members are exclusively remote. This level of flexibility and diversity prove to be effective and a win-win.
People are generally expected to be available 10am-5pm in their respective time zones and in practice, this holds true. Some remote folks work at odd hours, but so long as they are communicative about their whereabouts and make required meetings, there’s not much issue.
Additionally, team members have an on-call rotation to handle any platform issues that may come up in off-hours.
Distributed Revision Control and Source Code Management
San Francisco, CA (HQ); Boulder, CO; Amsterdam; Tokyo; Remote (65%)
We have offices in San Francisco, Boulder, Amsterdam, and Tokyo, plus a handful of designated co-working spaces in cities including London, Melbourne, New York City, Portland, and New Orleans. However, we are still a largely remote team. There are no requirements to come to an office on a regular basis, which means you can merge code from your farm in Indiana, or from GitHub’s rooftop in downtown San Francisco - wherever is more your style!
To help us stay on the same page, teams have two ‘mini-summits’ every year. Each team gets together, sometimes inviting partner teams, in order to roadmap and realign, set goals, reflect on the previous six months, and get in some good, old-fashioned face-to-face team bonding time. Whether your team is skiing, doing a ropes course, taking a cooking class, or volunteering together, the summits are a great way to connect with your distributed coworkers on a new level and get to know the people behind the GitHub handles even better.
While pairing partners should try to overlap as much as possible, there is no set schedule for everyone to work together. The only times that people are expected to work are for our agile meetings. Everyone should attend our StandUp, Review, Retrospective and Planning Meetings. Apart from that, we start and end as we please! While most people work between 8am and 10pm, there are no rules for when people do their work.
If people who don’t want to work full-time hours, we are open to signing 50% or 80% contracts. We want everyone to have flexibility to meet their individual needs. We recently started experimenting with fully-remote engineers as one of our colleagues is moving to Florida. This is the first time we’ve had someone work 100% remotely.
As we mentioned above under Work/Life Balance, we are also flexible on where people work. Team members often times work from home, from a cafe, or from the betahaus downstairs.
We have older folks that are closer to retirement and young folks working here as their first job. There are young families who are just starting to have children, singles, and of course people right out of school at Flatiron too. Depending on where you are in life, what’s important to you, and what you were doing the night before, people might get to work at 8 AM; or other people might not show up until 10:30am or 11am and might stay until late, or leave early and continue to work. The bottom line requirement is to be available for standups and meetings. People have the flexibility to work from home. We have some people who come in from Connecticut and have arranged to work from home 2 days a week to avoid a daily long commute.
The office tends to have the most people in from 10:00am until around 6pm. Some folks come later, others earlier. Some others will work from home on occasion. We use Slack as our main communication tool, with the pro’s and con’s of asynchronous communication. Flexibility is important, as some team members have family or care-giving responsibilities requiring them to work from home. We have team members in their 20s, 30s, 40s, 50s, and 60s. We also have developers who do short to medium-term remote work when they need to get away. Some play recreational ice hockey, and those rink times have exacting start times. Others still have evening classes they attend.
You can work from the office, home, or a cafe if you want to. If you need to come in after 11am, that works too. Everyone is flexible in where and when they work, as long as it’s communicated on Slack. This lets people know where to find you if they have a question or want your input on something. At a corporate company, you have to send in a formal request but we want nothing to do with that. Even Nicolas, our CEO, tries to work from home once a week because he has a family.
If you want to learn more about the Algolia team, read our team stories where we discuss scaling, our cultural values, and Jason’s first month at the company. And if you’re already interested in joining us, we hope we’ll hear from you soon!
15 Open Positions
Want to List Your Company?
Submit a team profile!
Select 8 Values
Contact me (Lynne 👋)
Qualify Your Values
Reach Thousands of Devs
Find Value-Aligned Candidates
Have Meaningful Initial Conversations
Don't Fill Roles, Hire Teammates
You can post as many job openings as you want.