> personally coached by a google software engineer for months
> done and given 100s of mock interviews
> paid for some to be done by professionals
> 100s if not thousands of hours on Leetcoding and algorithms trying to improve
Neither of these are relevant if you want to work as a programmer. I say this because probably millions of programmer never done any of those things before they get a job as a programmer.
Getting a job is more about how good you are at working with others, more than anything. When they are interviewing you (or even more important, working with you) they want to see that you're collaborative and can contribute. Sometimes that's surely knowing the best algorithm and knowing how to implement it without searching for a solution, but most of the time it's not.
It could be that you already are very good at programming, but it doesn't matter because you're a shit person. Meaning that maybe your soft skills are very lacking compared to your technical skills.
You don't have to be the best programmer in order to have a successful career (sadly?) and you can definitely be comfortable just being a average developer. You certainly have other skills, or can acquire, that compliment your programming skills.
You'll get more attractive as a programming if you're not just someone who can program blindly, companies want someone who can solve problems + program. Or know how to create products + program, or manage financial + programming, so on. Knowing something other programmers don't, that is useful will make you a lot stronger candidate.
And stop focusing on immediate "point"/"chapter" exercises like Leetcode. They are inconsequential when it comes to actually working as a programmer.
Question: what have you been doing for 5 years exactly if only 1.5 years of those was at a workplace?
>Neither of these are relevant if you want to work as a programmer. I say this because probably millions of programmer never done any of those things before they get a job as a programmer.
Yes, underlying talent and intelligence is what matters. Leetcode is just the way companies filter for that today.
>It could be that you already are very good at programming, but it doesn't matter because you're a shit person. Meaning that maybe your soft skills are very lacking compared to your technical skills.
I have both bad soft skills and tech skills.
>Question: what have you been doing for 5 years exactly if only 1.5 years of those was at a workplace?
I did Leetcode almost since the beginning of my 4 years of university. 4 years in school + 1.5 years on the job = 5.5 years. I rounded down.
> half years of professional coding experience
> worked diligently at Leetcode for those 5 years
> personally coached by a google software engineer for months
> done and given 100s of mock interviews
> paid for some to be done by professionals
> 100s if not thousands of hours on Leetcoding and algorithms trying to improve
Neither of these are relevant if you want to work as a programmer. I say this because probably millions of programmer never done any of those things before they get a job as a programmer.
Getting a job is more about how good you are at working with others, more than anything. When they are interviewing you (or even more important, working with you) they want to see that you're collaborative and can contribute. Sometimes that's surely knowing the best algorithm and knowing how to implement it without searching for a solution, but most of the time it's not.
It could be that you already are very good at programming, but it doesn't matter because you're a shit person. Meaning that maybe your soft skills are very lacking compared to your technical skills.
You don't have to be the best programmer in order to have a successful career (sadly?) and you can definitely be comfortable just being a average developer. You certainly have other skills, or can acquire, that compliment your programming skills.
You'll get more attractive as a programming if you're not just someone who can program blindly, companies want someone who can solve problems + program. Or know how to create products + program, or manage financial + programming, so on. Knowing something other programmers don't, that is useful will make you a lot stronger candidate.
And stop focusing on immediate "point"/"chapter" exercises like Leetcode. They are inconsequential when it comes to actually working as a programmer.
Question: what have you been doing for 5 years exactly if only 1.5 years of those was at a workplace?