Simulmedia Interview Questions
& Process

The first interview was technical, it started with a recruiter's introduction. The interview was engaging and the process felt smooth and well-structured. The questions were relevant and thought-provoking, making the conversation flow naturally. The test task was of medium difficulty—challenging enough to be interesting but not overwhelming. It allowed me to showcase my skills effectively and provided a good insight into the company's expectations. Overall, the experience was positive, and I appreciated the clarity of the process.

I wanted to share my interview experience, hoping it might help others. The first call with Simulmedia's representative felt like it was all about what they needed, not what interested me. It also ran over by 15 minutes, so I couldn't ask my questions. The interviewer mentioned an 11am-8pm availability requirement a couple of times, which seemed to imply overtime expectations, contradicting their flexible availability claim. Then, I was asked to do a technical assessment on Coderbyte. As an Engineering Lead, I expected questions about code design and architecture, but the assessment seemed more suited for a junior/mid-level role. Two exercises were almost identical, involving data structure transformations, which felt redundant. The assessment had: 1. Transforming a big data structure from a URL response. 2. A similar transformation with a different data structure. 3. Validating a string-formatted float. 4. An SQL assessment. Tasks 1 and 4 seemed valuable, but 2 and 3 felt irrelevant and repetitive. There were also about eight Git questions and another SQL query, which felt unnecessary. The Coderbyte tool was the hardest part; it didn't give feedback on errors, making it tough to figure out mistakes when it marked solutions as wrong without explanation. After about 3 hours, I got a generic rejection with no specific reasons, which was disappointing and unhelpful. I hope Simulmedia uses this feedback to improve their technical assessment for Engineering Lead roles, respecting candidate time and ensuring it aligns with the position.

The interview involved behavioral questions and some technical aspects related to the job. The interviewer seemed uninterested from the start, maybe hungover or having a bad day. I realized it wasn't a good fit but tried to keep the conversation going. It felt like a waste of time. They didn't follow up with next steps or a decision.

Applied online. Had a phone screen with the Hiring Manager. Next, a 3-hour analytics test was given where I had to analyze a sample dataset and create a PowerPoint presentation. This was followed by a 3-hour onsite interview with 6 people. In total, about 8.5 hours were spent on the interview process, not including prep time for the analytics test. After this, there was zero contact for over 3 weeks, followed by a canned rejection email from someone I never met. When I asked about the presentation I spent 3 hours creating, the hiring manager and analyst said they only glanced at it and had no real feedback. It's fine to reject a candidate, but after bringing someone onsite, a follow-up within 3 weeks is the least a company can do. I guess I dodged a bullet, because if they can't manage a simple interview follow-up, I can't imagine how day-to-day operations function there.