What would be really cool is reconceptualizing hybrid work as quarterly retreats, where the company provides housing and other amenities for 1 to 2 weeks every quarter. This gives everyone time to bond and work on harder problems.
I get this wouldn't work as well for those with families because being away for that long is tough, but this would be great for say juniors and seniors with greater flexibility. It also solves some of the other issues, ie I could move to an MCOL and just fly in once a quarter to work together with everyone. The "retreat" aspect of it would also incentivize more people to be there.
On the company side of things, instead of leasing out a building for a long time, they can just rent short term and use the money they are saving to make the retreat more fun and productive.
As far as your quarterly meetings comment is concerned, even that is a variation of hybrid. I worked at a company once that had the quarterly meetups. It worked, but sometimes it was a disruption to a normal routine, especially for some co-workers who flew cross-country. Another company (100% remote company) had the annual weekly retreat which I liked better. You got your face time/watercooler collaboration bullshit/whatever out of the way, then 358 days of peace til the next one.
My advice - figure out your core niche (i.e. GCP, Go, Rust) and reach out to 2-3 firms and propose your services and availability. Look in your LinkedIn network for any 1st or 2nd connections working at consulting firms.
As far as side-projects and open source contributions, this is a two way street. When I look at side projects, I look for how well you are utilizing best practices in your code. If it's a sloppy, poorly documented mess it doesn't look favorably for you. If you use your side projects as a marketing tool they should be well-polished.
And that's bad because?
I have yet to see a 1–2h take home test actually be doable in that amount of time. It’s more like 8–10h to get going, have something meaningful, and code that isn’t inscrutable.
One company gave out sample code and asked me to optimize it so it ran under 5 seconds. The exercise was in parallelizing or caching/reusing what you could per the requirements.
it was great because:
- problem statement clearly defined
- skeleton code provided
- about 2 hours to complete
- solved an actual, real-world problem
We have crossed the rubicon on remote work. The shift has been well and truly paradigmed.
To choose to restrict your candidate pool to a small geographical location, pay relocation, pay higher salaries, have a lower employee NPS, have higher company carbon emissions, whilst your competitors have a much larger non-geographically constrained talent pool, with more attractive, flexible, family-friendly working conditions and pay less for those employees, making their companies more competitive.
It’s a no-brainer. The status quo has completely shifted. Any CEO that doesn’t yet realize that should consider quitting.
Source: https://www.bbc.com/worklife/article/20240322-us-salaries-hi...