“Experience” is generally defined as prior work history in the same field, not occupational knowledge. An entry level job necessarily means that you can apply for the job and still have a chance to get hired even if it is your first ever job (or, in a perfect world, that’s what it would mean, yet we live in a world where “entry level” job postings exist that also require 3-5 years of prior work history in the field).
Of course, just because it’s an entry level position, that doesn’t mean that someone who knows nothing about the job they are applying for can get it. That’s why I specified that every job has skills that you need to train either on the job or independently. In the case of python programming, you would absolutely need those skills down pat before applying to the job, because the expectation is that you are sufficiently competent with the language and can start on projects right away.
In my experience, maybe 20% of your job is based on what you know about the language going in. The rest is learning that particular companies pipelines, practices, and code base. Junior devs are absolutely expected to learn on the job, both about the product and development in general.
Junior devs are expected to learn on the job, but to come in with a solid base level of proficiency.
My internships and first junior position didn’t require me to know the language they used, but they required me to know a similar language and be able to program already. Being able to at least write pseudocode was absolutely required for those interviews.
Not true. For example, “entry-level” Python programming jobs will expect you to have experience with the Python programming language.
They will not teach you Python programming skills, let alone programming skills in general, on-site.
You’re conflating with “no occupation experience” with “no prior experience.”
“Experience” is generally defined as prior work history in the same field, not occupational knowledge. An entry level job necessarily means that you can apply for the job and still have a chance to get hired even if it is your first ever job (or, in a perfect world, that’s what it would mean, yet we live in a world where “entry level” job postings exist that also require 3-5 years of prior work history in the field).
Of course, just because it’s an entry level position, that doesn’t mean that someone who knows nothing about the job they are applying for can get it. That’s why I specified that every job has skills that you need to train either on the job or independently. In the case of python programming, you would absolutely need those skills down pat before applying to the job, because the expectation is that you are sufficiently competent with the language and can start on projects right away.
In my experience, maybe 20% of your job is based on what you know about the language going in. The rest is learning that particular companies pipelines, practices, and code base. Junior devs are absolutely expected to learn on the job, both about the product and development in general.
Junior devs are expected to learn on the job, but to come in with a solid base level of proficiency.
My internships and first junior position didn’t require me to know the language they used, but they required me to know a similar language and be able to program already. Being able to at least write pseudocode was absolutely required for those interviews.
You can absolutely be trained on the job for a python career. I am Software Developer and was mostly trained on the job before I received the title.
I’m curious. Did you have any prior Python programming experience or any programming experience at all before getting the position?
Not formal. Although I wrote Powershell scripts for the team I was on previously.