For skilled mid-career engineers, dynamic programming problems, np-complete bar raisers.

For new engineers, simple questions that can't be taught in school (questions that require business prioritization)

For older engineers, questions they haven't done since college (big-O, writing algorithms from memory)

Business prioritisation questions are good

Student here, could you enlighten me on those questions?

I fucking hate dynamic programming. I understand the concept, it just never comes to my mind.

Writing algos from memory just isn't relevant in practice, and I refuse to rote learn just for an interview. There's a reason seniors havn't done this since college.

If the company decides to hire senior devs and doesn't manage to come up with meaningful interview questions, their hiring process is borked. What's relevant is knowing when to use which algo.

@Fast-Nop
It's not regurgitating algos, it's using them to solve problems and talking about which ones they're using and why.

@SortOfTested That's not what you wrote in the rant: "writing algorithms from memory".

@Fast-Nop
Apply the refactor ;)

@SortOfTested Yeah then I agree.

Newbie here...does business prioritization refer to project management stuff like agile etc? or does it go deeper than that...or am I totally off base lol

@dmonkey
Questions relating prioritization in the context of a project scope, identifying missing information in requirements, presenting technical questions to business people and customers, stuff like that, and generally explaining how you deliver value to an organization. You don't really build that intuition without some real experience.

@SortOfTested Thank you 🙂👍

@SortOfTested I take the requirements from the customers to the engineers... I have people skills! What the hell is wrong with you people!?