Getting that next job is not a walk in the park, what advice would you give someone in this situation?
For further actions, you may consider blocking this person and/or reporting abuse
Getting that next job is not a walk in the park, what advice would you give someone in this situation?
For further actions, you may consider blocking this person and/or reporting abuse
Marius -
πWii π³οΈββ§οΈ -
mahdi -
Tapp.AI -
Top comments (35)
My wife is in the middle of a career change.
She wants to get inside the IT sector.
I can show you how we are doing it.
1) First we defined a list of job titles that might be a good fit for her: product manager, project manager, product owner, agile coach, ...
2) Next we looked up for people around us that are currently employed with one of those job titles.
One way to do this is via a LinkedIn search:
Search > People
area=Berlin ; title="product manager" ; sectors="..."
3) Next we created a list on Trello of the companies where those people work.
We went on their website to collect basic metadata. For example the
Zalando
card contains this:4) Then my wife reviewed all of this and asked herself in which companies she would like to be. Asking questions like
In the end we have three lists, the top-tier where she would really love to work, the third tier where she is explicitly not interested, and the second tier "Why not?".
5) The crucial point is that we do not focus on what online job offers are or not available at any random moment. We focus on which companies she would like to work, and getting to know them very well.
Huntr is a free service that is specifically designed for this.
huntr.co/
Looks useful, but it's centered on applying to online job offers no? As I said, they are not our focus.
You can fill in any kind of job you like.
They have a DB of existing companies that pulls the internet but you enter anything in.
I tried it, good tool.
I would say this sistematical approach is so awesome.
The crucial point is that responding to online job offers follows an inverse Pareto law:
Also you avoid the imposter syndrom of not feeling legitimate.
Once you have found companies that you like, what you can do next is obvious: go and discuss with them. Maybe they will find something to do for you that is not what you first imagined but where you will be a better fit.
It depends on what career-stage they're currently in. If they're unemployed and asking for advice they're probably more on the junior side, have been applying for a tonne of jobs and getting rejected without clear reasons. Here's what I would say to such a dev:
Dealing with Rejection
Improving Communication
Strategy
These are the thoughts that come to me off the top of my head. Above all, stay calm, make sure you're getting enough sleep, and use this down-time to get in touch with some hobbies and maybe catch up with friends that you might've not had time for lately.
All the best. :hug:
Credit for this tactic goes to a GaryVee video btw. :)Β β©
This is probably the best comment I've read on dev.to in months. Props to you, sir.
Thank you very much sir. π
I've gotten every single position I've had through leads. From friends, from family, from acquaintances, from schoolmates.
In a bit of irony, for most of the positions I've applied for, my list of references was entirely with people already employed by the company.
I'm not a "networker", and I'm naturally shy. I work very hard at overcoming my introversion. But even I have found references, tips, and leads to be the best way to land a position.
Build some software by yourself! It's nice to have something to show off to potential employers, it denotes initiative and it's a great way to learn.
leetcode is your best friend for next 3 months. Go shake hands with leetcode π€
I'm not super familiar with leetcode as a user of it, would you recommend any advice on how to approach using it to help someone out of their unemployment situation... like beyond their basic getting-started instruction?
After some thoughts, here are the steps I would take:
Okay, all of the above should complete in 2-3 days. It's one day for resume, one day for sending messages on LinkedIn, and the rest time (a few hours) to figure out the short term goal.
After setting up the goal, the next part is training.
Going to technical interviews is much like playing sport (if not going to the battlefield). We have to be mentally & technically trained for it. Leetcode comes in at this point.
We can find lots of practical interview skills in the book, Crack Coding Interviews.
I hope anyone looking at the steps can find them helpful :)
Let me also take 1000 steps back. I made huge assumption: my perspective is from traditional hard-core coding interviews. If your goal is small startups (where your skillsets weight more than coding interview skills), then you can ignore some of the recommendations.
When the company demands specific skillsets, perhaps a few side projects would be more helpful in the short term!
leetcode is a really unattractive option if money is tight.
Do you mean the $159 yearly membership fee? Yeah, that was not so nice since lots of resources are community-based on leetcode.
I think there are quiet a few free alternatives to leetcode ;)
Do not try to learn too many new frameworks. Just pick one you don't know but is in demand. Get back to going deeper into a framework you already know. Prepare for all nitty gritty and obscure things they ask in interviews. Also try getting some AWS certification as it adds some weightage in today's cloud everything world.
Reach out to your network. A majority of jobs are not advertised, and the way to access this hidden job market is through people you know: friends, family, old co-workers, etc.
Also, it might be a good opportunity to build the side-project you've been putting off, or learn a new technology. It'll help during the interview process when they ask 'Do you have any side projects?'.
There are no guarantees and no universals, so the usefulness of this advice may vary, but I wish you the best of luck.
Keep going. I quit my previous software job because it's not where I wanted to stay. I took the opportunity to take on coding projects and build my first portfolio site during that time. I was very worried that I wasn't going to find a job soon, let alone reach the interview stage during my job search. I ended up finding a new job within the same year at an awesome company and I am very happy. β€οΈ
Don't fall for the talks of recruiters! Some might indeed be able to find you the perfect job, but they are being paid for every candidate who signs a new contract. So they make money based on quantity instead of your job satisfaction.