There's no downside to applying for jobs. Attemting to get a job, talking to companies, doing interviews, etc. are all good practice for getting a job. You can make feedback on yourself, and some companies may even offer feedback (many don't however for legal reasons). You'll get rejected oftne, or not even get interviews, but hey, that happens even with lots of experience.
You can use a practice service as well, like interviewing.io.
I agree. I definitely think the focusing on one project is a good route, but I'm hardly certain of that or feel like it's the only way, but more importantly, the answer is at least DO BOTH.
Apply while you build out your portfolio. So much of the job search has an element of chance and you never know who will be enamored by your talent, personality, or simply have a big need for help. It's their job to disqualify you, not yours.
Honestly, not getting the interview, is was I fear. If I get interviews and they go bad. That would be feedback, but if I don't.
I know I'm overthinking and procrastinating. But that's truly why I'm asking all these questions, because I fear they'll see the 6 years of no experience and just ignore me.
Though I found one of your comments where you say "If you've been programming for 5 years, then it's 5 years experience. I don't care whether that was paid or hobby work." which is kind of where I'm at. Even though my priority was something else, programming was a hobby. Though, unfortunately I only recently started to make sure I don't leave the projects I work on get deprecated and lost.
But yes, even though it's not rational I fear that if I start applying without knowing what they might want I might never get to know what I'm not getting interviews (at least)
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.
There's no downside to applying for jobs. Attemting to get a job, talking to companies, doing interviews, etc. are all good practice for getting a job. You can make feedback on yourself, and some companies may even offer feedback (many don't however for legal reasons). You'll get rejected oftne, or not even get interviews, but hey, that happens even with lots of experience.
You can use a practice service as well, like interviewing.io.
I agree. I definitely think the focusing on one project is a good route, but I'm hardly certain of that or feel like it's the only way, but more importantly, the answer is at least DO BOTH.
Apply while you build out your portfolio. So much of the job search has an element of chance and you never know who will be enamored by your talent, personality, or simply have a big need for help. It's their job to disqualify you, not yours.
Honestly, not getting the interview, is was I fear. If I get interviews and they go bad. That would be feedback, but if I don't.
I know I'm overthinking and procrastinating. But that's truly why I'm asking all these questions, because I fear they'll see the 6 years of no experience and just ignore me.
Though I found one of your comments where you say "If you've been programming for 5 years, then it's 5 years experience. I don't care whether that was paid or hobby work." which is kind of where I'm at. Even though my priority was something else, programming was a hobby. Though, unfortunately I only recently started to make sure I don't leave the projects I work on get deprecated and lost.
But yes, even though it's not rational I fear that if I start applying without knowing what they might want I might never get to know what I'm not getting interviews (at least)