What worries me about this move is getting stuck and the potential gap in my resume. I've met so many people who "temporarily" became Uber drivers and ended up stuck in the gig economy for years. If none of my side hustles work out, I'm assuming I'll need some impressive personal projects to make up for the gap in my resume. That or just lying and hoping I get away with it. But if I don't find anything in the next ~6 months, I won't have much of a choice, will I?
But your full-time job right now is to get a job in your field (which at this point in your career means "tech".) You might start in support, or testing, or something like that, but you want to get your foot in the door.
Naturally there are a LOT of people in the market right now, so you want to stand out from the crowd. If you understand that this is primarily an exercise in marketing and not tech, then you'll be on your way. To get a job you "sell yourself", so you can't just rely on a CV.
Be creative. Be bold. Be proficient (in that order). Convince "me" (ie an employer) that this is the best opportunity they have. Stand out from the crowd.
Good luck.
I'd probably steer clear of those "Instant Applications" on LinkedIn. When the bar to apply is that low, they're just going to be flooded with noise.
Working on side hustles and applying for more full time work are not mutually exclusive pursuits, so why not do both?
2) Applying to jobs by filling out forms online is going to be mostly fruitless. You will occasionally get bites, but even as a senior engineer, I've found these to mostly be wastes of time. Instead, find companies that you are interested in. Then, go on LinkedIn and find engineering managers, team leads or even senior engineers and reach out to them with direct messages. Everyone thinks they need to reach out to the CEO or CTO, but they get 1,000 messages a day. If you reach out to someone lower down, they will typically have enough sway to get you in front of the people making hiring decisions.
3) Even for the best engineers, there's a randomness and luck component to interviews. The best way to practice for interviews is to actually do them. Try to spread a wide net and get as many interviews as possible, even for companies you aren't interested in working for. The experience will get you in the groove. And remember, it's a numbers game. You might be great at LeetCode, but get that one question about heaps that you can't answer. Just learn from your mistakes and move on.
4) If you can, try to appear employed. For better or worse, people will see you as more desirable if you are employed. This might mean setting up an LLC called Foo Software, giving yourself a role of Software Engineer, and then bidding on projects on Upwork. You don't have to lie about what you are doing if anyone asks (and most won't ask for details), but this gives you something to put on your resume and some experience.
5) Everyone on HN talks about having amazing side projects on your github account. Take this with a grain of salt. I find that almost no one ever asks or looks at my github account when making a hiring decision. There's a small but vocal group of people who hate standard interviews and therefore like to say that looking at projects should be the metric by which you judge candidates. There's merit to this philosophical argument, but in practice, most companies just don't care.
6) As far as "unskilled labor", if you need the money, go for it. But I don't personally think that it will help you to have it on your resume.
7) There's lots of remote jobs today and by all means apply, but you will have the biggest leg up if you apply to jobs that want people in person and you are willing to go in to the office.
When you get the job, here are a few pointers that will help you ramp up:
Understanding codebases:
- https://news.ycombinator.com/item?id=19924100
Testing pipelines, scaffolding, issue templates:
- https://news.ycombinator.com/item?id=26591067
Making the most out of meetings and leveraging your presence:
- https://news.ycombinator.com/item?id=22873103
Product development:
- https://news.ycombinator.com/item?id=22827841
Giving a damn:
- https://news.ycombinator.com/item?id=20356222
If I disappear, what will happen:
- https://news.ycombinator.com/item?id=25008223
Consulting, understanding the problem your "client", who can be your manager, has:
- https://news.ycombinator.com/item?id=24972611
On taking notes. When you're told something, or receive a remark, make sure to make a note and learn from it whether it's a mistake, or a colleague showing you something useful, or a task you must accomplish.. don't be told things twice or worse. Be on the ball and reliable:
- https://news.ycombinator.com/item?id=24209518
Product, architecture, and impact on the team:
- https://news.ycombinator.com/item?id=24503365
Onboarding new hires to a codebase, what if it were you, improve code:
- https://news.ycombinator.com/item?id=22860716
Tips to learn from videos:
- https://news.ycombinator.com/item?id=22710623
- https://news.ycombinator.com/item?id=22723586
Communication with the team:
- https://news.ycombinator.com/item?id=21598632
- https://news.ycombinator.com/item?id=21614372
Reduce information asymmetry, template for taking minutes of meetings to dispatch to the team:
- https://news.ycombinator.com/item?id=21427886
More meeting notes. Reply to a person who had trouble talking in corporate meetings:
- https://news.ycombinator.com/item?id=20323660
Communication, alignment:
- https://news.ycombinator.com/item?id=24177646
Useful things for the team and product that add leverage:
- https://news.ycombinator.com/item?id=21808439
Management involvement as a spectrum:
- https://news.ycombinator.com/item?id=22715971
Researching topics:
- https://news.ycombinator.com/item?id=25922120
Keeping up with a firehose of information:
- https://news.ycombinator.com/item?id=26147502
Fractal Communication: communication that can penetrate several layers of management and be relevant to people with different profiles and skillsets:
- https://news.ycombinator.com/item?id=26123017
Remote work, use existing tooling and build our own. Jitsi videos, record everything, give access to everyone so they can reference them and go back to them, meetings once a week or two weeks to align:
-https://news.ycombinator.com/item?id=26179539
Write better. Always.