If you’re looking to get hired as an individual contributor somewhere else, maybe you should. But judging from this and other posts of yours, you’re not, so you’re probably not doing it wrong.
It’s just that when interviewing, it can few easier to evaluate some algorithm puzzle than to figure out what it means and whether it’s true that “the app is gonna be great.”
Hm, sometimes when I’m interviewing someone who I know is a “no” it feels like I’m leading them on if I go through the full interview. I thought it would be more respectful of their time to let them know that early, but maybe I am wrong about that?
I’ve also heard (via HR) about candidates being surprised to not get the offer in cases where I kept the interview going and pretended things were going well.
Same, I switched after a long stretch in 2020 where Slate bug fix PRs stagnated. I find the ProseMirror API less intuitive but overall it has fewer bugs and I have been able to customize it pretty heavily.
It’s just that when interviewing, it can few easier to evaluate some algorithm puzzle than to figure out what it means and whether it’s true that “the app is gonna be great.”