3 ms·
I'd probably start by asking myself, what type of company do I want to work for? And what type of job do I want? Scroll job boards and see what is out there and
by harrisonjackson 4y ago
I'd probably start by asking myself, what type of company do I want to work for? And what type of job do I want? Scroll job boards and see what is out there and what appeals. Then go buff up any skills you need to get a job at those companies.
A great way to do that is build a clone of some aspect of their product or business. This will prepare you for the interview and job like an insider. You'll be able to talk about the parts of the product that were hard and why. Then all of a sudden your interview is just a good conversation.
Force yourself to do it the way an actual engineering organization does it, too.
If you aren't sure _how_ engineering teams organize projects, deployments, testing, etc then do a lot of googling and even reach out directly to CTOs, PMs, Senior devs, etc at different companies and just explain your exact situation - even link to this thread.
Lots of people are willing to take the time to help especially if it is as simple as saying... "At company X we do Y and Z" and then that gives you another thing to dig into. And you've potentially made a helpful contact/mentor.
It sounds like you don't have a lot of extra time to develop yourself into the perfect candidate for your maybe dream job, so for now you could probably pay the bills using freelancing job sites and offering IT/web dev help to local small businesses.