How to let it be known you are only down for remote work?

DatabaseHead

Just curious how you would list this on your resume, when posting to indeed etc.

My resume has a job summary, I was thinking about putting it up there as more of an objective, but wasn't entirely sure. Has anyone played around with this? I've heard of people putting their salary requirements at the bottom of the resume etc, but never just calling out remote work.

One other thing....... What about if you just want some remote days not all. Thoughts on how to word that? Where would you put this information at on your resume? Would you?

scaredoftests

I would never put your salary requirements on your resume. That is my 2 cents. In addition remote discussion should be saved for the interview.

DatabaseHead

Why would you interview if they never had the intention of offering remote work? Seems like a huge time waster to me.

markulous

There should be someone from HR or IT contacting you to schedule an interview, I'd probably bring it up then before you go any further.

Mishra

Personally, I wouldn't put it on your resume. It has a chance to close a door you likely wouldn't want closed.

I would just bring it up in the initial phone call from the recruiter. It's OK to be clear near the end of the phone call when they ask if you have any questions.

Verities

Not sure about your experiences with remote access, but in the past when I've had it, my employer expected me to be available 24/7 in the event things hit the fan. I didn't enjoy getting woken up at 3 AM for some stupid server being down. I am very happy to say I no longer do on call work or have remote access, so no work outside normal hours unless its overtime .

JoJoCal19

I'm kind of in the same boat. I'm looking for either fully remote or partial remote only. I figure to bring it up in a first interview with the actual hiring manager, and bring it up as "What is xxxxx company's position on flexible work arrangements including remote work?" and then "Is this position able to take advantage of those options?". I wouldn't want to be automatically filtered out of jobs on the front end because I would consider working in office for the right opportunity.

Techytach

Maybe list it as a strength under synopsis. Like;

"Strong worth ethic 100% of the time, from remote to the office, I always give my all. Looking for new opportunities to work any time any where."

Or something. If you really wanted it on the resume.

Danielm7

Verities wrote: »

Not sure about your experiences with remote access, but in the past when I've had it, my employer expected me to be available 24/7 in the event things hit the fan. I didn't enjoy getting woken up at 3 AM for some stupid server being down. I am very happy to say I no longer do on call work or have remote access, so no work outside normal hours unless its overtime .

Sounds like you're talking about just handling issues from home, the OP is talking about never actually going to the office. I'm curious what your job does when things do hit the fan now? Just call you and make you drive in?

Verities

Danielm7 wrote: »

Sounds like you're talking about just handling issues from home, the OP is talking about never actually going to the office.

OP does mention working remote a few days in the last sentence of his post.

Danielm7 wrote: »

I'm curious what your job does when things do hit the fan now? Just call you and make you drive in?

They accept that the issues will persist until I get in the next day. Benefits of being in contracting work is that you can point to legal restrictions and if they are violated, you can sue.

Plantwiz

Start your own company and offer remote support to businesses, otherwise, I do not see anyone hiring an applicant to solely work remotely.

Catalog companies have telephone folks work remotely and I know of several clients who do the 'busy' work from home, but these folks are typically issued a device and remote in to take calls and such, but their role is very limited. All the 'guts' stuff, networking, security management, resets and such is handled from the corporate hive and doled out unless it is a weekend and a caller needs assistance. I have not seen a situation yet where the company would leave the trusted individual outside the walls and have them VPN in or remote in to service the network. Inevitably, something fails and it requires hands-on at the device level to correct.

Simply for security reasons, I just haven't run into a situation yet where the main IT folks get to sit at home and handle business 100%...the times they remote in are typically on-call weekends/evenings/holidays and that is to keep the rest of the company (sales people and the accounting folks who are working odd projects, well working).

Basically, I would not put that I only wanted remote work as my sole responsibility on a resume. This would be something, I think, that develops over years of trust and growth of an organization, but someone still needs to be onsite.

Kinet1c

Here's a website that has remote only jobs: https://remotebase.io/

They do exist but are obviously not as common as office based jobs. Good luck in your search.

scaredoftests

My husband works from home (systems engineer), but he has to travel to the main office every 2 months or so to Mountain View or go to NYC every other week.

Danielm7

Verities wrote: »

They accept that the issues will persist until I get in the next day. Benefits of being in contracting work is that you can point to legal restrictions and if they are violated, you can sue.

Interesting, I guess it just depends on the company. I was a contractor until recently and when there was an issue i'd remote in and deal with it. I'd either bill for the time or take it off later in the week, it didn't mean that I wasn't responsible for making sure everything was functioning. I can't even imagine a system blowing up at 5:30 on a Friday and my company just accepting nothing working until Monday morning when people came back to work.