Re:What would a recession mean for developers?
by exdsq on Saturday May 28, 2022 @03:56AM
(#31538458)
Some startups are still requiring weird whiteboard questions sadly. Interviewed for a role recently and was asked to navigate a maze of obstacles and teleports with possible infinite loops, saying the minimum number of steps to leave the maze if it’s possible. That was for a test engineering role so… WTF.
[ Parent
| on HN ]
Re:What would a recession mean for developers?
by bigDinosaur on Saturday May 28, 2022 @04:04AM
(#31538498)
I assume they wanted more than a DFS or BFS or similar with loop detection? The teleports sound like a fun twist, although I'm not sure they change that much since from a graph perspective presumably they're just another edge?
Re:What would a recession mean for developers?
by 414techie on Saturday May 28, 2022 @10:48AM
(#31540757)
Yeah, but does that kind of problem really exist on a regular basis for a test engineer on that team? I doubt it.
Re:What would a recession mean for developers?
by bigDinosaur on Saturday May 28, 2022 @09:15PM
(#31545313)
It's probably not that relevant to the job, but as far as weird questions go it's not too bad. It's presumably not leetcode hard, basically.
Re:What would a recession mean for developers?
by exdsq on Wednesday June 01, 2022 @04:11AM
(#31579356)
Actually it was literally a hard leetcode question! The other 3 were 2 medium and 1 easy. I can work out easy and medium leetcode answers from first principles in an interview setting, usually. I can't with hard ones tbh.
But ultimately it seems very divorced from reality of what I do, which is TestOps (building out CI pipelines, reporting, test infra, etc...).
Re:What would a recession mean for developers?
by DeathArrow on Saturday May 28, 2022 @10:24AM
(#31540563)
They wanted to know if you can traverse a graph, which is something pretty simple.
I don't see a need for outrage here.
Re:What would a recession mean for developers?
by exdsq on Wednesday June 01, 2022 @04:10AM
(#31579344)
I'm sure it's simple if you know it! But having not taking an algorithm class before, and having completed three other Algorithm questions within the 90 min total allotted time, I crashed pretty hard. I solved it afterwards when I had time to really think, but didn't know it off the top of my head.