I have only been involved in software engineering interviews at BigTech for senior devs in the System Design round (because doing System Design is part of my $D

I have only been involved in software engineering interviews at BigTech for senior devs in the System Design round (because doing System Design is part of my $DayJob). Just to explain my perspective. When I was in the real world and when I interviewed at my current job, I practiced being able to explain my experience in STAR format based on my “career document”. In the real world, all of my “interviews” were mostly just my talking to CxOs and directors at small companies. My loop for my current job was all behavioral after the initial screening and even that was more system design than anything else. If you know there is going to be a coding interview, wouldn’t it behoove you to practice that too - or “grind leetcode?” I did DS&A back as part of my job during the first decade of my career bit twiddling in C across multiple architectures and later on maintaining a custom compiler toolchain. But I would definitely have to practice to be interview ready at this point. The coding part of my job has gotten a lot easier during the last decade. It’s been about knowing what to write and getting buy in