WideOrbit Software Engineer Interview Questions
& Process

A WideOrbit recruiter reached out, excited about a role they thought I'd be perfect for. They started with some basic questions, like asking 'what is JSX?'. Next, I interviewed with the hiring manager. It was a casual chat that went well. Afterward, they quickly wanted to schedule technical interviews for C# and React. The C# interview was enjoyable, with questions about my experience related to C#, Entity Framework, and .NET authentication. Then came a coding exercise to output Person objects to a CSV, which was straightforward. The React interview, however, was a different story. A contractor led it while the initial hiring manager was less involved. They bombarded me with obscure JavaScript details, like the reasoning behind React hook names and JavaScript multithreading. They sent me Codepen links with code snippets and asked me to predict their output, including one example with various typeof expressions. Frustratingly, the contractor would interrupt my thought process and even speak over me when I started answering. The recruiter's communication also ceased after this interview, effectively ghosting me. It seems I dodged a bullet, as working with that contractor would have been unbearable.

A recruiter reached out to me about the role and did a technical screening. We had some dropped calls due to bad reception, but the recruiter was cool about it. Then, instead of an onsite, I had a video call with a senior engineer because of travel issues. It was a mix of talking about technical stuff and a friendly chat about the team's needs and what I was looking for. The next day, the recruiter let me know about the next steps. I ended up declining to move forward because I already had offers from other companies with comprehensive packages. Honestly, interviewing with WideOrbit was way better than the tough, long processes at other places. The recruiters were nice and real. The team and engineers I talked to were all chill, skilled people I'd love to work with. The problems they're solving are interesting, especially since the teams are so small and focused.

I met with the dev manager and we chatted about design models and how they do implementation. This guy was super sharp and really explained the company's visions and goals well. He talked about how their product offerings made them number one in the market and why customer satisfaction is always the top priority. No excuses, work hard, feel good about it, and build the future. I was sold.