How to Determine If Candidates Will Thrive in a Remote Work Environment
hackernoon.com
hackernoon.com
I've worked from home, successfully, for many years, and I disagree with that criteria. Everyone works from home differently, and I know people who can rock their work exactly because of the added flexibility to care for their home and family on their work breaks. It decreases the stress in their life to slice their day in different ways, and allows people with busy lives to do better on all fronts.
There are many different ways to manage remote teams - some are hands-off, only concerned about whether the work is done. Some monitor their people to be sure they are 100% online during "working hours". Many are in a middle ground, with expectations set of specific response times to Slack, IMs, emails, etc. Likewise, there are many different remote working styles. Some people do well with a typical 8 hour day. I tended to target a 40 hour week, but that would be made of many 2-3 hour chunks throughout the week, not 8 hour blocks.
At the end of the day, you have to trust your team to do their work. The companies that are resistant to their remote people handling personal tasks during their "working day" don't truly have that trust.
The flexibility of being able to intermingle personal tasks throughout the workday is paramount to remote work. It totally does reduce stress and it allows you to work when you're productive and not work when you're not. I find that I'm a very bursty developer and I think that's more the rule than the exception in our profession. Remote work arrangements really help accommodate that reality where output is not constant throughout the day.
I made the same comment elsewhere. Completely agree with your post here.
I don't regularly work from home, but I have solved several difficult problems while doing laundry, and I can specifically think of one time recently that was during a workday while I was folding towels. I know it's happened other times as well, I just can't specifically think if it was during the day while working from home.
I've also solved problems while showering, mowing the grass, eating dinner, and laying in bed trying to fall asleep.
Who knew -- developing software involves lots of thinking. You don't have to have your butt in a seat in front of the computer in the office to think. Sometimes doing something completely different is just what's necessary to break through -- whether this is getting up to get a drink, going for a walk, or doing sometimes completely non-computer-related like laundry.
Neither is necessarily 'better'; both have their place in our daily lives. The 'diffused mode' regularly doesn't get the credit it deserves as people (e.g. educational systems) are hammering too much on the 'focused mode'.
If you are interested in learning how to use the 'diffused mode', more things related to learning, and optimizing the way you learn I can recommend the free course on Coursera called Learning How To Learn by Dr. Barbara Oakley and Dr. Terrence Sejnowski.
[1] https://staciechoice1010.wordpress.com/2014/08/08/focused-vs...
... Or not. Make it an open office space, with people taking around you. Then you'll get the worst possible.
- I can focus
- I can go on a walk w/ my dog, wife, kid(s) whenever I want
- I can sit and think without worrying that I don't look busy to some stupid manager...
Lots of reasons, and they're all perfectly acceptable. Good leaders will realize that the best work often happens when you're not directly working (e.g. in the shower, doing laundry, going for a walk). Being able to step aside and do these things throughout a workday is a productivity boost.
One of the things people often forget about in this discussion is the lost company time from being at the office. Yes, valuable conversations can happen in the hallway, but more often than not a lot of non-work chatter does too. I'm fine with that -- I don't want to work in a POW camp -- but to me it highlights how ill-considered the "laundry folders = bad workers" mentality is in many cases. I worked in a cube farm for 5 years, then from home for the past 4 years. I'm vastly more productive at home.
That really just means they're a butts-in-seats company that doesn't have an office. Take this from a job listing of theirs[1]
> we don't care if you work at night, on weekends, in your pajamas, after class, in another timezone, etc. We do ask that you are available by Skype during regular 9-5 CST work hours
That's great if you can flex your work time, but if you have to always be available, that means you are either working or thinking about work almost all the time. This makes work even more stressful, unless you only work during the proper business hours.
On another note, the laundry thing is just ridiculous. That's a 5 minute task. People in an office environment burn 10 minutes at a time playing ping pong, foosball, or any number of time wasters.
[1]: https://community.articulate.com/discussions/building-better...
Decorum prevents me from saying how I truly feel about that.
Cool things about working for us:
Potential to earn bonuses for projects. Very *LOW* salary but since we are ROWE (Results Only Work Environment), bonuses are part of the deal!> You would be part of our underpaid production team
Of course, one of the benefits of working from home is that you can do a load of laundry and perhaps background process on a complicated problem in the meantime. No question that it's a nice perk. The flexibility to craft a healthy work-life balance is wonderful.
I think the point in the article is that if that's the FOCUS of why you want to work from home, it COULD be a red flag. The people we've found really thrive in our remote environment are those that cite the fact that they are more productive when not working in an office.
This doesn't sound very compassionate to engineers leaving big, dysfunctional companies (which by the way preach the exact same ethos of personal responsibility). Basically, they are damaged goods who aren't expected to thrive in a better environment?
The problem with small companies is usually they are chaos and often cult of personalities. It's not their fault, it's their nature. They have to be able to pivot their business on a dime. That's tough on developers though, particularly when the thing you've been working on get scrapped on a pivot.
What it boils down to is it's short sighted. He's professing like he's solved the interview process. I'll bet his success / failure rate is just like everyone else's.
Btw, if you're really good you can work remotely even in the largest companies. Just work your way up to your own P&L, hire a global team and away you go. Probably will have to check in a few times a year in person, but that's no big deal.
Small companies can be hellholes too, especially when runway is short, or competition is fierce. Like anything, it depends on the culture.
As far as staying at big companies, inertia is a big reason. It's easy to justify staying at a place that pays really well, particularly if you have a family, a car payment, and/or a mortgage. 5 weeks of vacation is nice too; that comes with tenure and leaves as soon as you do. I have to constantly check myself to see if I'm miserable. I have scars for staying miserable for too long. It's bad for my career due to burnout. Not everyone has learned that lesson though.
Que?
There are only a few companies worth that much in the world. The only (well known) company big enough to buy another company for that amount is Saudi Aramco.
He's probably generalizing for the sake of writing, but you can get some really lazy positions that really can rot your skills if you don't drive yourself. We're talking about companies that barely need more than for-loops and if-statements and some CRUD.
If you try to go from that to a fast-paced startup then I agree you're chances of thriving are going to be much lower. You have to absorb all of the startup's knowledge in addition to not having enough technical skills "in cache".
This is 99.9% of all companies, including startups.
How many companies need developers to write a new sorting algorithm that is 15ms faster?
Compassion aside, it also isn't the least bit accurate. If our process sucked that bad in large companies, then I shouldn't have the numbers to show for it. Somehow, though, we manage to be really profitable despite being lazy idiots.
I've posted this elsewhere on HN, but if you find an engineer or manager with a history of accomplishment at large companies, you're lucky to have them. Not only can they get shit done, but they can get shit done even with the distractions and roadblocks from big company politics. Those folks would probably be very effective in a remote position given their ability to filter noise. But yeah, if someone sucked in a big company, they might suck in a startup, too.
- If they talk about how great it was to do their laundry during work hours, thumbs down
- we don't care if you work at night, on weekends, in your
pajamas, after class, in another timezone, etc. We do
ask that you are available by Skype during regular 9-5 CST
- Cool things about working for us:
Potential to earn bonuses for projects. Very *LOW*
salary but since we are ROWE (Results Only Work
Environment), bonuses are part of the deal!
As someone who successfully works remotely full time: nope, nope, nope. These guys have offloaded their office space costs to their employees homes under the guise of a flexible work schedule.I could answer this questions, but have a tendency for long, technical explanations. ;-)
procedure ShowTime; // A procedure with no parameters
begin
// Display the current date and time
ShowMessage('Date and time is '+DateTimeToStr(Now));
end;
function Average(a, b, c : Extended) : Extended;
begin
// return the average of the 3 passed numbers
Result := Mean(a, b, c);
end;
Edit: thanks for the formatting tip.But if you were interviewing someone who claimed to know Delphi/Pascal at all and didn't know this off the top of their head, it would be a big red flag.
It would be like asking a C programmer what's the difference between "void foo(){...}" and "int foo(){...}". They had better be able to tell you the difference without having to think about it.
If "knows Pascal" is one of the job requirements, it's actually a good question.
Two spaces at the beginning of each line.
And you have two hours to edit a comment. :-)
Very likely, no.
Unless those companies somehow got very good on your "a" point and told nobody, their more filters they add the biggest the likelihood of having one that is anti-correlated to competence. And just one such filter can be enough to cut all the extremely few great candidates.
I wouldn't do a 5 hour interview, I don't care who the company is. I haven't had to do a cold interview (not referenced by an existing employee) since my first job out of college 20+ years ago. There is no way companies are going to find talent doing those long slog interviews, unless they pay 2x rates or something.
Just the thought of 5 hour interviews makes my stomach queezy.
That's only 4 words.
It seems like a rather cruel interview question, now that it qualifies as uninteresting trivia.
If you worked in Delphi, it most certainly isn't trivia. It's like asking what does void mean in C type dialects or what does the = vs == do. It's not trivia, it's trivial.
That is a great quote; I hope you don't mind if I borrow it from time to time.
The comments that this is "nuanced" or a "silly gotcha" are interesting. I wonder if these commenters have ever programmed in Delphi or Pascal? (No offense intended to those commenters if you have.)
I've never used Delphi itself (although a program I wrote was bundled with it for a while, if you remember WinSight). I did write some Pascal code 35 years ago for DOS and the original Mac OS, but haven't touched the language or looked at it since then.
But even I knew the answer to this right off the top of my head. It's so fundamental that if you don't know it, you don't know the language at all.
Sure.
>It's so fundamental that if you don't know it, you don't know the language at all.
That's what we were shooting for. We knew there was no way we would know a rock star without working with them, and we were more than willing to accept good people who had room to improve. We couldn't accept someone who didn't know the language. It worked out really well for us. Because the interviews were short, we could fit a lot more in during a workday and get the process over quickly.
I never did voluntarily, because "real programmers" just didn't do that. But there was always some legacy POS written by a non-software person--who no longer works for the company, of course--that had been embedded into an Excel spreadsheet and never once tasted source control, but it was somehow critical to the business, anyway, and you might have been assigned the task of figuring out what it did and turning it into "real code".
While I have a low sample size, it seemed like those reduced from about 10 MB of godawful brute-force spaghettified spreadsheet macro, down to about 10 lines of Java or C#, using algorithms and basic library functions. The hardest part is convincing your boss's boss that they both do the same thing, because the guy who wrote the macro spent so much time on it that there's just no way it could actually be so simple.
As I favor considering aptitude in addition to skill, asking gotcha questions about jargon or syntax doesn't seem fair to someone who could hear that 4-word explanation and instantly understand what you meant.
This sounds like precisely the kind of person I want to work with, regardless of whether they are remote or co-located.
Talking about the work/life balance benefits of remote work is a bad thing? This makes even less sense since remote work is usually coupled with flexible work hours.
Not that I've read this year, but I think we're finally past peak FizzBuzz.
Wow, I really like lunch time with my teammates so... I think I'll go remote where I can't do that at all and just freeloading on a random company so I can do my laundry from home! No one will ever notice my evil scheme! Said no one ever.
Highly recommend anyone who has opinions about certain rights try hiring someone for a gig and see how much the responsibilities come to mind, when it comes to being effective.
Some people aren't geared to work from home, or good at it from the get go. They still may be geared to work remotely (maybe a coworking space). Managing distractions at home is no different than managing distractions at the office. Same goes for finding a way to be effective at the office vs remote.
The ability to focus and manage distractions is something that can take people a while to figure out, and a worthwhile thing to focus on.
I just try to remember the value of removing the commute - If we take an the 2 hours a day saved in a commute (door to seat), it saves 60 hours a month, or 720 hours a year. That's an entire 30 days of living per year of extra waking hours.
Great, back to the "you've gotta have experience to get experience" dance.