Piksel Software Engineer Interview Questions
& Process

I got the internship through the Global Engineering Girls initiative. It was an online meeting with HR and a developer. They were nice and open to collaboration, explained the company culture, and I got asked some technical and non-technical questions.

The interview was with a senior architect who seemed more impressed with himself than actually giving information about the available position, the company, and seeing if I would be a good fit for the opening. He explained his role, and the size of the company, their client, and then went into an hour long question series that consisted of questions more appropriate for interviewing a Computer Science Professor rather than a Software Engineer. For a company so large, it made no sense to ask a developer architectural verbiage that will NEVER be applied to the tasks that would be assigned to them. All the questions could've easily been Googled, and didn't prove anything that makes a developer great. I would've much rather been given a code assignment to display my coding abilities, rather than having to answer questions such as, "What makes Java a unique Object Oriented language?" and "What language does Java compile to?" and "In what year was Java created and the name of the language?"...The interview was very insulting, and afterwards, I told the recruiter that I wasn't even interested in the results. Thirty minutes into the interview, I just wanted the guy to stop talking and if I had to work for him, then I knew I wouldn't want the job at all, regardless of the tasks given.

The agency set up the first technical phone interview. The interviewer called on time and did a quick screening of core technologies for about 30 minutes. They asked if I had any questions at the end. Then, I had a face-to-face interview with an architect and a resource manager that lasted around 100 minutes. They asked a lot of in-depth questions about my past projects and the technologies I've used. After passing the face-to-face, I got an offer in a couple of days, so their interview to offer process was really quick. You can negotiate a small raise, and it'll be handled through the agency. Some recent interviews also included an extra written technical test. My advice is to know your core technologies and frameworks really well. If you don't know something, just say so, because the architects at ioko are talented and reasonable; they won't judge you on just a few wrong answers. They are talented and friendly people. Be ready to work on different projects in highly agile teams. You'll be working with the best technologies, so be prepared to perform at your best as they have high standards. It's a work-focused culture, and you might need to travel to client sites.