Job hunting isn’t fun: endless applications, repetitive cover letters, sourcing referrals, and lots of competition. It’s all quite stressful. To its credit, LinkedIn has been working hard to revolutionize the process over the last few years. It offers salary comparison tools, dedicated job hunting groups, and a resume assistant.
Now, LinkedIn has another feature that you’ll love: a tool that lets you find potential new roles based on how long your commute would be.
LinkedIn’s developers (rightly) believe that your commute time can have a massive impact on job satisfaction. Nobody wants a two-hour drive every morning and night, five days a week. That would turn even the dreamiest of jobs into a nightmare.
The new feature—called Your Commute—will calculate your would-be travel time to potential jobs, all within the LinkedIn app itself. Let’s take a look at how to use it.
How to Find Job Commute Times Using LinkedIn
At the time of writing, the feature is only available on the LinkedIn mobile apps, although the feature will come to the web version of LinkedIn at some point in the future. To see the commute for a job listing, follow the steps below:
- Open the LinkedIn app.
- Click on the Jobs tab at the bottom of the screen.
- Scroll down past the Job Description section and locate the new See Your Commute section.
- Tap on Set starting address in the From field.
- Set your departure time in the At section.
- Choose either the car, public transport, or walking icon above the map.
You will now see your commute—including time and directions—in the map section.
Note: The recruiter must have entered an exact location for the Your Commute feature to be available on any given listing.
If you’ve already got a job and just want to find more information about your journey, such as how much your commute costs, you better off using an app like Waze or Google Maps.
Image Credit: Jirsak/Depositphotos
Read the full article: How to Find the Commute Time to a Potential New Job Using LinkedIn
from MakeUseOf https://ift.tt/2KLjlVi
via IFTTT
0 comments:
Post a Comment