The more the company sees developers as a cost center (e.g. legacy companies who put developers in the IT org), the more they're looking for specific technologi

The more the company sees developers as a cost center (e.g. legacy companies who put developers in the IT org), the more they're looking for specific technologies. "I need a dev with 7 years of Spring Bott!" The more the company sees developers as a crucial input to innovation and building a more valuable company, the more the emphasis is on capabilities. "I need a senior developer that's great at solving problems. I don't care what tech stack" But in the second case, a core capability needs to be passing a typical developer interview. So you'll need to practice writing code in a time limit with someone watching you. You'll also need to practice designing a system. ^ it is dumb that this capability matters, but it's the reality today. There are some companies that interview differently where you actually build real-world things without someone looking over your shoulder, but it's not the norm yet.