Ho presentato la mia candidatura online. La procedura ha richiesto 3 settimane. Ho sostenuto un colloquio presso The Helper Bees nel mese di lug 2023
Colloquio
One phone call, and one zoom interview were pleasant enough. The take home “coding exercise,” however, was a straight dump of their entire monolith. The challenge? Isolate and unit test a private component. Not only is this incredibly disrespectful of candidates’ time, this is a bad faith grab to get free work done. I’ve never seen a company do this before and was shocked. The exercise itself was technically impossible because of the dependencies of their seemingly randomly selected class and method weren’t available on an external network. The base class required a SQL connection to instantiate, which is a requirement of compilation, which is a requirement to even run MS Test. What this company should understand is that highly qualified candidates will pass on them because of this practice. Even though everyone is positive due interview decorum, as engineers, we can tell when we’re being taken advantage of and typically align our energy accordingly.
Domande di colloquio [1]
Domanda 1
Figure out how to run our monolith that has over a dozen solution files. No readme or direction whatsoever. Fix the number of build errors that result. Create a unit test project where none exists. Unit test a private method that is called procedurally. Rewrite that method so it’s testable if not. If there are dependencies…good luck?