[marionzualo]

IMHO (unfortunately) in tech the skills that allow you to succeed in a job are different than the skills that allow you to get hired for a job. This is a generalization, but I think that is what happens in most places.

@patio11 has written a bit about this: https://twitter.com/patio11/status/1086379271415713792 @tqbf and Erin Patek https://sockpuppet.org/blog/2015/03/06/the-hiring-post/

I think this leads to a lot of false negatives when interviewing. but if you are applying you obviously want to increase your chances of succeeding so, you have to know how to 'play the game'.

My recommendation to you would be: 1. spend a lot of time preparing for these tech interviews. Study how they are structured. There is a lot of material online (blog posts) as well as books documenting what it takes to succeed. 2. there are some people that do paid courses on "how to interview at FAANG style companies". they may be worth depending on the upside. Note that not all companies have those types of interviews but if you are aiming for them it makes sense to prepare the best you can.

[faeyanpiraat]

I’ve been doing coding interview exercises used at big corps. It is sent via email daily.

They seem to be quite easy and after solving some, it feels like I’ve ‘seen them all’.

You cannot be doing anything fancy in a short interview afterall.

If this is really how they filter programmers, it does not seem like a really good way to measure one’s ability to create true value.

[pm90]

They aren’t measuring your ability to create value but in how you approach problems you don’t know the answer to. In many cases you will get a pass even if you don’t solve the problem, but can talk about what the solution would look like, what the interesting parts of the problem are, and so forth.

[aisengard]

But if you know the answer to all of them, what are they really measuring? Once you study enough there's not really much new under the sun. It's a really fatal flaw in the typical interview process.

[pimmen]

A good interviewer could ask some questions to find out if the answer is just memorized or if they understand the concept. And it would test your willingness to educate yourself on a domain, which is something I would value in my team.

And I say this as someone who doesn't particularly like the modern tech interview style, I think actually trying to build something is better. However, it does have some merit in measuring a candidate's ability even if it's not necessarily that great.

[cpursley]

What's the daily email you're using?

[faeyanpiraat]

Not sure about the url, but he does lots of youtube as the “tech lead”

[bmn__]

Shyu's sites: http://techinterviewpro.com http://algopro.com

[dominotw]

not op but

dailycodingproblem.com

[definitegrunt]

Thanks for these links! They're very helpful.

[cheez]

Or, just hear me out, you can use that time, take a little risk and develop your own products.