I applied through a recruiter. The process took 7 weeks.
Embarking on what I hoped would be a swift sail with PW turned into a six-week odyssey through a sea of indecision. The journey began with the usual HR pleasantries, yet it was the following rounds that unfurled the flag of confusion. A quartet of interviews, each more perplexing than the last, seemed to be a masterclass in time-wasting. By round 4, the CTO, with a mere four years under his belt, appeared more like a deer in headlights than a tech-savvy leader. Questions tossed around like a salad with no dressing, which were all over the place and utterly tasteless. It was a performance that could make one wonder if the role itself was just a mirage. After a meticulous document submission, akin to handing over the keys to my professional kingdom, PW slammed on the brakes, shelving the position like a forgotten novel on a dusty bookshelf. The irony was a tech company unable to tech its way out of a paper bag in hiring. In short, PW's hiring escapade was a wild goose chase led by a team seemingly using darts on a job description dartboard. There was an experience as enlightening as a power outage, and it was equally unwelcome.
Design problem, blah, blah, blah.
The following metrics were computed from 2 interview experiences for the PhysicsWallah Technical Architect role.
PhysicsWallah's interview process for their Technical Architect roles is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for PhysicsWallah's Technical Architect interview process.