Tech interviews are discouraging because they are so open-ended, especially on the tech-screen stage. Without knowing more about your circumstances here's what

Tech interviews are discouraging because they are so open-ended, especially on the tech-screen stage. Without knowing more about your circumstances here's what I found works for determining expectations: - In the phone screen try to clarify that the tech-screen questions are in the domain of the role you're interviewing for. Good recruiters will be open with that information and should be up to date on their hiring procedures. Pressure them more if they remain vague, consider it a red flag if they don't budge. - Get comfy with writing {B,D}FS algorithms, --not just that you know them-- write them out. Same with writing a tree/graph data structure. For some reason cycle-detection is a common question, be familiar with tortoise and hare algorithm as well as coding it up. - Search on glassdoor to see if anyone drops any interview questions - Search github to see if anyone uploaded a take-home if there is one The hardest part about tech interviews is the rejection and moving on mentally. Where I am now we have a pretty non-technical process but the caveat that compensation is a little lower (remote, US only), you can figure out how to DM me through my profile if you need something sooner than later.