I'll echo this and the related/parent comments -- super common experience for me too. I WANT to use iOS Safari and frequently do -- I just wish their mobile web version was given more love/functionality versus being a stripped down version.
There's a big difference between remote work (which can function 100% perfectly fine in the "Manager's schedule") from "remote work across varying timezones". In my experience (3+ years working fully remotely, 10+ years working partially remotely), timezones (overlap of working hours) matter much more than physical geography.
Even among remote work in different timezones, there's still a huge difference between say a 4 hour timezone (say, covering all of North America) working with people from potentially ANY timezone where you have potentially 0 hours per day of overlap.
Even in an organization that does asynchronous work really well, very few organizations can do everything effectively in async, meaning that you'll always want to have some overlap for synchronous discussions.
My advice for any company concerned about expanding remote work would be to simply limit/restrict which time zones you're comfortable people working in.
Our all-remote person team at Close.com has scaled up to 15+ engineers, 40+ people overall. We do have people all over the world, but we tend to focus our hiring around American & European Timezones, which provides a nice balance of covering a huge percentage of the world's population while still providing enough overlap to have synchronous meetings.
Or just require that people keep a schedule for your timezone. So you can be in whatever timezone you want provided you're working 8-5 UTC-8, for example. Requiring someone be in a specific timezone is just a slightly less of a burden than requiring they be local enough to commute it. You're still excluding a huge swath of potential employees.
Yes, I'm using "timezone" as shorthand for "the timezone of your working hours", which occasionally can/does include people who want to work odd hours to accommodate.
That said, we are always a little skeptical of people who are willing to work very odd hours (e.g. throughout their night), because for many people it's not sustainable for them long-term.
At Close we’re a 100% remote team of ~33 building the sales communication platform of the future. We’ve built a next-generation CRM that eliminates manual data entry and helps sales teams close more deals. We are hiring product-focused engineers to help us unify the world's sales calls and emails into one beautiful workflow.
Our backend tech stack currently includes Python/Flask, Elasticsearch, MongoDB, Postgres, and Redis running in Docker/Kubernetes on AWS. Our backend primarily serves a well-documented public API that our frontend JavaScript/React app consumes.
We <3 open source – using dozens of open source projects with contributions to many of them, and released some of our own: https://github.com/closeio
At Close we’re a 100% remote team of ~33 building the sales communication platform of the future. We’ve built a next-generation CRM that eliminates manual data entry and helps sales teams close more deals. We are hiring product-focused engineers to help us unify the world's sales calls and emails into one beautiful workflow.
Our backend tech stack currently includes Python/Flask, Elasticsearch, MongoDB, Postgres, and Redis running in Docker/Kubernetes on AWS. Our backend primarily serves a well-documented public API that our frontend JavaScript/React app consumes.
We <3 open source – using dozens of open source projects with contributions to many of them, and released some of our own: https://github.com/closeio
I've been at Close for the last 6.5 years and it's been the most fulfilling job I've ever had.
1. The engineering/product problems are challenging and fun.
2. The leadership (and the entire team really) is very supportive, focused on sustainable growth, and provides a lot of opportunities & ownership for each individual.
3. We've developed a remote culture that just works™️.
At Close.io we’re building the sales communication platform of the future. We’ve built a next-generation CRM that eliminates manual data entry and helps sales teams close more deals. We are hiring product-focused engineers to help us unify the world's sales calls and emails into one beautiful workflow.
Our backend tech stack currently includes Python (Flask, Gunicorn, TaskTiger), Elasticsearch, MongoDB, Postgres, and Redis running in Docker/Kubernetes on AWS. Our backend primarily serves a well-documented public API that our front-end JavaScript app consumes.
We open source – using dozens of open source projects with contributions to many of them, and released some of our own: https://github.com/closeio
At Close.io we’re building the sales communication platform of the future. We’ve built a next-generation CRM that eliminates manual data entry and helps sales teams close more deals. We are hiring product-focused engineers to help us unify the world's sales calls and emails into one beautiful workflow.
Our backend tech stack currently includes Python (Flask, Gunicorn, TaskTiger), Elasticsearch, MongoDB, Postgres, and Redis running in Docker/Kubernetes on AWS. Our backend primarily serves a well-documented public API that our front-end JavaScript app consumes.
We open source – using dozens of open source projects with contributions to many of them, and released some of our own: https://github.com/closeio
For someone special who wants to do both hands-on technical infrastructure-focused work AND lead/manage a small remote team (2-3 people) of really talented people doing the same.
WHO ARE WE:
At Close.io we’re building the sales communication platform of the future. We’ve built a next-generation CRM that eliminates manual data entry and helps sales teams close more deals. We are hiring product-focused engineers to help us unify the world's sales calls and emails into one beautiful workflow.
Our backend tech stack currently includes Python (Flask, Gunicorn, TaskTiger), Elasticsearch, MongoDB, Postgres, and Redis running in Docker/Kubernetes on AWS. Our backend primarily serves a well-documented public API that our front-end JavaScript app consumes.
We open source – using dozens of open source projects with contributions to many of them, and released some of our own: https://github.com/closeio
We recognize we are looking for someone very senior here in terms of devops/tech experience + having leadership experience... we're willing to be very competitive in salary/comp to accomplish this. Feel free to reach out at phil@close.io if you want to chat more before formally applying.
I've done the #1 employee thing too. The founder was someone I had worked for previously. He was technical enough that I didn't have to worry about growing the team from there, he handled it all.
I see you mentioned something like. Make sure you’re still excited after 30 days (or fire fast).
That's a big NO-NO for me. 30 days is way too small for any company to make a decision on a hire. It just means your process for hiring is not good. We must start with firing people who were responsible for the that bad hire first.
An employer in the US is bound by US laws on whether the OP is an employee or contractor, no matter where the OP is. (If the OP was defined as an employee then many laws like the ADA would not apply to them, assuming they never travelled to the US office, but Canadian employment laws would, like required notice periods - it's a very complex setup and many employers just won't do it, some smaller companies do it without actually understanding what they're doing.)
