[Nginx487]

For the small startups, who don't have time for BS like leetcode, I advise asking the candidate's code first of all. The senior-level developer almost definitely should have GitHub with his portfolio- or pet-projects. After carefully looking through his code, it becomes 100% clear do we want to talk to him or not. After that we usually had one interview, something like system design + soft-skills. Subjectively, I recall the hiring experience as very successful compared to what I experienced interviewing people for major tech companies according to their guidelines.

[devnullbrain]

>his

There's the rub. Women are disproportionately likely to spend time caring for children and have less free time available for hobbies. Personal projects might be a positive indicator that someone really cares about computing but the projects I've been praised for in interviews make up ~1/500th of the time I've spent developing my skills. It can objectively display the quality of code that a candidate can write but its absence isn't a guarantee that the skills don't exist.