GoodData Interview Questions
& Process

The interview had 2 rounds. The first round was 1hr and focused on technical aspects like Javascript, React, and TypeScript, along with some git questions. The second round was a 90-minute one-on-one at the office. This round included two parts: first, solving a JavaScript algorithm problem, and second, theoretical, behavioral, and scenario-based questions.

The interview started with a technical round where I had to write a BASH script. They let me use online resources, Google, and AI as long as I shared my screen, which I initially thought showed they valued work style and thought process. However, the reality was different. The office manager was quite rude when I had issues with the entrance system, not even offering water. After the second and final round, I got an offer, but only had a few hours to decide, which contrasted with the manager's promise of a week to accept. They were also vague about important job details like on-call duties and background checks, which could be dealbreakers for some. Later, an HR rep called to ask about my diploma details, expecting immediate answers like I had it right in front of me. This felt like a memory test, not a credential check. They then asked me to email pictures of documents, but hadn't sent a list of what they needed, despite promising to. I offered to come in so they could scan them. The HR rep also kept mentioning a penal register record I already had, repeating themselves as if I didn't understand. They had documents saved on Google Drive, waiting for the official email to share them. It seemed like passing interviews didn't guarantee an offer, as you could fail the HR evaluation, which felt subjective and based on the rep's personal opinion rather than document verification. Their culture seemed to be about claiming to 'do GOOD' without practicing it, and relying on manual, insecure processes for documents. In 2017, I was rejected due to EU residency requirements, which felt misleading. Even in 2023, it seems things haven't improved, with poor quality and a process that feels like a warning to avoid them.

I applied online in December 2014. Around the start of January, I got an email response and a phone screen interview. The recruiter seemed inexperienced and disorganized, often needing reminders to follow up. She even forgot to send the written confirmation for the face-to-face interview details. The in-person interview was with a senior developer/architect and another Senior Technical Writer. It was quite engaging and lively, but also demanding, involving a thorough questioning about my skills, experience, and handling of different situations. We discussed my understanding of Agile & Scrum and how I apply content adaptation to it. After this, they sent a take-home assignment. I had to select content from their API documentation, developer portal, user guides, and manuals, and make any necessary adjustments or corrections within a week. This assignment was particularly strenuous, requiring me to review over 200 pages and aim for professional standards using industry best practices and technical writer handbooks. A concerning sign was the recruiter 'forgetting' again to give feedback on my submitted task. Only after I followed up did she send a standard rejection email. It was frustrating to learn the outcome this way, as if my application had slipped her mind. Overall, it was a disappointing experience.

I was pretty skeptical going in, especially with some of the not-so-great reviews online. But Jessica, the Talent Scout, was really impressive. I liked that they called her a 'Scout' instead of 'Acquisition.' She was upfront about why the company had issues with culture and climate in the past. We ended up talking for more than an hour, and I actually left thinking that GoodData has made some serious improvements and could be a fantastic place to work.