BrightRoll Software Engineer Interview Questions
& Process

I applied online and got a reply from the recruiter. We had a phone call where she asked me a technical question, which I answered. Then, a phone interview was scheduled with the manager. The manager discussed my work and explained the role. They asked me a programming question over the phone, and I explained how to solve it. They also asked for alternative solutions, which I provided, but it seemed they weren't convinced. The recruiter called later to inform me I wasn't selected and gave reasons. I didn't quite agree with the reason given about lacking passion for my past work, as it's hard to judge passion over the phone, especially based on voice tone. Overall, I really liked the whole process and wish Brightroll success. Good to know Yahoo acquired them.

I applied through campus resume submission and heard back from a recruiter within a few days. She wanted to have a quick chat. I was really excited about the role and felt my background was a good fit. The conversation was surprisingly short, around 20 minutes or less, and the recruiter didn't seem very engaged. I wasn't asked any technical questions or given much chance to talk about my experience. She mentioned I'd hear back in two days, but I had to follow up myself to get a generic rejection email. I was not happy with how unprofessional the recruiter was.

This was for a new grad Software Engineer role. It was a bit long but gave a good feel for the culture and had some fun questions. Started with a career fair intro where I gave my resume and got put on a list for phone screens. Then a recruiter phone screen asking standard tech questions. After that, a 1:1 technical interview where an engineer went over my resume, asked a few easy coding and algorithm questions, and discussed the role (about 45 mins). The next step was a coding simulation, which was fun. It was an hour-long Skype call where I had to code a simple game using whatever tools I wanted, with the engineer available for questions and I could use Google/docs. I liked this because it felt more like real work. If you passed that, you got an onsite interview. Mine was a full day, super tiring, but gave a lot of insight. It had a technical 1:1 in the morning on algorithms, coding, and web stack knowledge. Then lunch with team members. After that, three more 1:1s: one very specific to the role (JavaScript for front-end), and two more conversational ones about personality and culture fit, not typical behavioral questions. I got an offer call later that day. A big plus was the transparent feedback after each step, unlike other companies. The downside was it took a while and had many steps, but it was worth it. The process felt intense at first, but the coding sim and onsite were more relaxed.