Marchex Interview Questions
& Process

I thought the interview was pretty straightforward and not too tough, but maybe that's because it was for a contract role. It started with a recruiter phone call where we went over my resume, what I'm looking for, and why I'm interested in the company. Then, I had a casual chat with an executive about my background and career aspirations, and I got to ask a lot of questions about the company. The last part involved four 30-minute interviews with different team members. They asked me to discuss my experience and then threw some common behavioral questions at me about how I'd handle different scenarios. I got the offer a few days after that.

I saw a Perl job ad and applied. First, I had a chat with the recruiter over the phone and exchanged some emails. After a bit of back and forth, I did a technical phone screen. Then, they invited me for an on-site interview. It was a long one, 4.5 hours with 6 sessions, and I met 8 people in total. We did coding on the whiteboard, talked about designing an object model for blackjack, and designing the SQL DTD for a music system. They also asked about handling team conflict. It was pretty standard stuff. Two managers pitched their teams to me, and I got to ask them about the customers, the product, and how the company operates. They even mentioned work-life balance, which was nice. I made sure to say how excited I was about a Perl opening and the chance to work with Asterisk. The next day and the day after passed with no word from Marchex. On the third day, I emailed the recruiter to ask what happened. He called the next day and said I did great on the technical side, but they were moving on because they didn't think I was that interested in the job, even though they never actually asked me about my interest.

A recruiter reached out via email. I got put on a group email accidentally, but nothing sensitive was shared. The recruiter was mostly OK. The first interview was a casual phone call with the hiring manager. Right after that, I had a technical phone screen, and then later that day, I got an invite for an on-site interview loop. The loop had three 2-on-1 interviews, a 1-on-1 lunch interview, and a quick chat with the recruiter at the end. It took up most of the day. Mostly technical programming questions and some resume stuff. The recruiter emailed to wish me luck the day before. It seemed to go well. I then had a second on-site 2-on-1 interview with two other team members, which also seemed good. Later, I was told that even though my interviews went well and everyone wanted to hire me, the job itself was eliminated, so they couldn't offer me anything. I then had an informational interview with another manager and two on-site 1:1 interviews for a smaller team, but that didn't work out and they sort of forgot about me. Most of the process felt alright, but I was always a bit unsure about the company. The workspace was basically a cube farm, which is pretty average and doesn't really stack up against the bigger tech companies or startups in Seattle. It really sucks to cancel job openings after interviewing people, and it says a lot about their management.

First there was a phone screening, then several back-to-back in-person interviews at their downtown offices. The offices were nice, and the interviews were in a big conference room. They were really good about offering breaks and stuff. The hiring manager interview was last, which is a shame because you really want to make a good impression on them and you're pretty tired by then. The questions were mostly about your skills and why you want the job, not super specific about their products, so just do your homework and you should be fine.