I applied online. The process took 3 weeks. I interviewed at BandPage (San Francisco, CA) in May 2015
Interview
There were a series of interviews. The first round was over the phone with the head of the marketing department. The next round was in person in their SF office. There were a series of interviews that day, not just with the head of marketing. It was a relatively casual environment and the interviews seemed more like conversations.
Interview questions [1]
Question 1
Why BandPage? What do you know about what we do? What are some excel forecasting processes are you familiar with?
I applied through a recruiter. The process took 3 days. I interviewed at BandPage (San Francisco, CA) in May 2015
Interview
Company started out with a "culture" phone screen that went really well. They described the community in their offices and wanted to make sure that I was passionate about music and such. Made it sound like finding someone that could fit in with their "family" was the number one job requirement.
A day or two later they requested a tech phone screen. I had been warned by an associate who had previous dealings with them that they were a bunch of flakes and that I shouldn't waste my time. Unfortunately, I ignored his warning and experienced it first hand. The questions were fairly basic and low-level for a modern startup, and I yet again got the feeling that their "culture" was the most important thing. I felt like it went extremely well, until I heard back from my recruiter. The screener at BandPage said that they would pass on me because I had no experience in two key technologies. Here's where the flakiness presented itself. Of those two technologies, I have years of experience in one, listed it on my resume and was never once asked about it during the phone screen. With the second one, all I was asked was a quick "are you using it in your current job?" To which I answered no and he immediately moved on. I didn't get a chance to explain that not only am I proficient in it, but I'm a regular contributor to the community open-source code behind it. I tried to get my recruiter to follow up on these items, but BandPage never responded.
Aside from them just doing a horrible interview, this also made my recruiter question whether I was being truthful on my resume. I moved on to another recruiter and am now happily employed by a company that doesn't have their heads up their backsides.
I applied through a recruiter. The process took 3 weeks. I interviewed at BandPage in Oct 2014
Interview
My interview process was: (1) Initial call with a recruiter to judge the fit. (2) Phone screen with the CTO. (3) Semi-casual lunch / interview with the management staff. I learned more about the company and was asked a lot of questions about my experience and leadership style. (4) On-site interview for about 5 hours. I met multiple engineers, managers, the architect/co-founder, CPO, and CEO/co-founder.
I was asked technical questions (general software dev questions and coding questions), and questions about my experience and strategy towards building and shipping software products. The meeting with the CPO & CEO taught me a lot about the company and its mission. I was impressed the CEO took time out of his busy schedule to meet with me 1-on-1. I thought everyone was smart, passionate, and friendly, and asked good questions. The interview was challenging but not off-putting.
Interview questions [1]
Question 1
I was asked a JavaScript coding question that I had never been asked before. It was difficult, and took a good 30 minutes to solve. Out of respect for BandPage's interviewing process (because they probably still use the question) I won't reveal the exact details. It was very relevant to the position and a good judge of my expertise in JavaScript coding skills. The type of question was: implement this highly abstract and highly useful utility that you've probably been using in your work from a 3rd party library. It was really interesting to work out how that type of code functions at a low level. I learned something new by solving the problem.