Invisible Technologies Interview Questions
& Process

The whole process was super disjointed, like zero continuity between rounds. I went through 6 rounds total, and weirdly, there were two coding challenges. I nailed both. The first one was to build a full OpenID Connect (OIDC) provider: a central auth/SSO server for other apps, an OAuth 2.0 server for tokens, and an IdP for user identity stuff, registration, login, and profile management. It had to be production-ready, with AWS deployment using Terraform and had to be done in 4 hours, including unit tests and docs. The first two interviews went great. Then came the system design, and that's when it got weird. The interviewer seemed clueless about the project they picked, making it hard to answer questions. The questions were ridiculously vague, making me doubt myself, but nope, they were just poorly framed. Super abstract stuff that's just frustrating. It felt like they wanted to see how I'd react under pressure. For instance, one question was about a client with tons of data sources and an ontology, wanting AI to map it all. A decent start, but they just asked, 'what are your next steps.' I asked clarifying questions, and they kept saying, 'that's all you get.' The scenario was totally unrealistic. I thought to myself, 'I wouldn't even take this client,' but you're supposed to answer in a technical interview. Turns out, that was the right answer, which is wild because that's usually decided much earlier. It seems like they're a volume shop, taking on tons of small, vague POCs, having people use AI on them for a few days, and if it doesn't work, they drop the client. It feels like a boiler room of people vibe-coding low-quality solutions at scale hoping to land contracts. Not great.

I was contacted by an HR representative from Invisible Solutions regarding a Software Engineer position. The interview process consisted of 7 steps: 3 in-person interviews, a coding assessment, and other online evaluations. I went through all the stages, which included a system design interview. However, the team's specific needs for the role and the expected impact of the chosen candidate were not clearly communicated. The expectations seemed to vary between interviewers, leading to a disorganized process. After the final interview, I awaited an update but did not receive an offer. Despite my attempts to follow up, I received no feedback, and my final email went unanswered. This lack of communication created a poor impression and felt disrespectful of my time. Consequently, I cannot endorse the hiring process due to its unclear role expectations and inadequate follow-up communication.

The response time was pretty slow for me, I had to wait 4 months for the second round of interviews. I almost gave up hope, but they eventually got back to me with a positive outcome. You don't interact with a person during the interviews, which makes things easier because you can avoid random questions and get prepared. The number of tasks they require for the offer can change during the process; they initially stated 3 tasks but I ended up completing 5.

The interview process started with a recruiter call, followed immediately by technical rounds. There were two technical rounds, each lasting an hour: one for system design and one for a coding challenge. It was a bit unusual not to have a hiring manager or team member meeting before the technical parts, which felt disorganized. I didn't make it past the coding round, though I didn't find it that hard; I just didn't manage my time well because communication with the interviewer was unclear. While this specific opportunity didn't work out, I'm hoping the experience will make future interviews smoother.