I haven't joined a new job in over 30 years, so what do I know.
But having seen quite a few come (and go) it seems to me that some context knowledge helps with getting up to speed.
It's not so much that ypu come in knowing the language (most don't) but doing a bit oc research, perhaps watching some videos, all help to learn the jargon. This can mean a faster learning curve when they tell you the important stuff.
Certainly the externals help. Can already use Git, know their way around SQL and SQL tools for inspecting databases, know something about database design (3rd normal form) - you don't have to know any of these, but it helps to hit the ground running.
And of course you can easily find out topics that might be useful by, you know, just asking in the interview or later.
What IDE, or text editor do they prefer - knowing your way around that will help you hit the ground running.
But having seen quite a few come (and go) it seems to me that some context knowledge helps with getting up to speed.
It's not so much that ypu come in knowing the language (most don't) but doing a bit oc research, perhaps watching some videos, all help to learn the jargon. This can mean a faster learning curve when they tell you the important stuff.
Certainly the externals help. Can already use Git, know their way around SQL and SQL tools for inspecting databases, know something about database design (3rd normal form) - you don't have to know any of these, but it helps to hit the ground running.
And of course you can easily find out topics that might be useful by, you know, just asking in the interview or later.
What IDE, or text editor do they prefer - knowing your way around that will help you hit the ground running.