I don't know why they made so many algorithms, data structures and big O questions during interview, when all they wanted me to do was to maintain some legacy, tight coupled, spaghetti code with no architecture, documentation, tests nor any kind of engineering behind :/

  • 0
    I agree. I think a much more effective interview exercise would be “how well can you refactor this code?”
Add Comment