> every company's interview process has become like Google's although the leetcode hiring model is too often cargo culted by orgs trying to emulate faang this

> every company's interview process has become like Google's although the leetcode hiring model is too often cargo culted by orgs trying to emulate faang this is not representative of the industry at large. if it seems true you may be considering too narrow a slice of it > What would be your advice be to fresh college graduates, or anybody for that matter, who are good at programming but not at leetcode? consider applying to roles that don't use the leetcode hiring model personal anecdote: first job out of undergrad, small shop whose software you probably haven't heard of but have almost definitely interacted with if you live in the US: phone screening, remote technical session with 2 hours (own time) to write 3 functions, on-site interview given a laptop, an hour, and instructions to write a toy API then asked a few questions about solution and general concepts second job, cold emailed a professor asking about openings for a programmer/research software developer, asked to clone and build a project repo and sketch a simple (<1 hour) feature third job, also research software, online application, 1 hour video interview, entirely qualitative, no coding component, having work from the previous role on Github likely obviated the need for a technical session I'm not a great leetcoder, I reason fairly slowly, I struggle under time pressure and observation if you're like me, play to your strengths, you're still competent and you can find work