After some thoughts, here are the steps I would take:
Retrospective on the unemployed situation: anything to improve, avoid, or learn?
Note down a list of dream companies. Like another response mentioned, Tier1, Tier2, Tier3 and such
The employee recommendations are critical but don't be shy from direct emailing to recruiters on LinkedIn.
Prepare the resume. It is mandatory.
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.
Make a plan about how to address Easy/Medium/Hard questions
Use a company filter to narrow down the coding problems to tackle, because that should cover most aspects of coding interview
Don't just try to solve problems on your own. Engineering is all about learning best practices, which means most beginners learned the coding interview skills through looking at others' solutions. Ironically, yes, we have to study solutions first before we all in solving a problem independently
Schedule phone screens to push ourselves
Mock interview, coding on a whiteboard, on paper
...
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!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
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!