6

I can understand why in technical interviews they use those algorithmic questions. It's an incredibly short period of time to assess someone's coding capabilities. BUT can't we find a better way to do it? I mean, I've never implemented dijkstra in a work environment, and I had never heard of someone that faces those kind of problems in a normal day of work.

I may be judging by my limited information, but wouldn't be more useful to actually ask to solve a more plausible problem?

For example, create a microservice that implements this API, send us the GitHub link and the API url.

¯\_(ツ)_/¯

Comments
  • 0
    Unless the position was specifically for implementing dijkstra, that expectation is totally unwarranted. Totally empathize with this.
Add Comment