ModCloth Interview Questions
& Process

Initially, I applied for a different role and went through a phone screen. They passed on me for that position but kept my application on file. About a month later, they reached out about a Project Manager opening. The interview process involved an initial day of about four interviews, followed by a second in-person interview two weeks later. Then, there was a final phone interview. I received the job offer approximately five days after that. Be ready for a long and possibly irritating interview cycle, as interviewers often change or leave. It was ultimately worth the effort, but I'd advise approaching it with considerable patience. Also, don't hesitate to ask interviewers for feedback; they'll give it to you honestly, which is a really good thing.

The process began positively, but quickly declined. After an initial chat with the recruiter, who was impressed but lacked job specifics, I completed a skills test. I then had an interview scheduled, but had to follow up for details. The interview involved speaking with three people. Two were technical interviewers who couldn't explain the role's expectations. One criticized my lack of Ruby on Rails experience, despite it not being in the job description. I suspected they were seeking free advice. The recruiter mentioned she was going on maternity leave and advised emailing if I didn't hear back. After two weeks, I emailed and learned nothing had been discussed. A few days later, I was informed I didn't get the job, which was disappointing given their apparent uncertainty about the role.

I applied online and after a few weeks, I was invited to a second round. This involved a "mini-test" where I had to create a detailed report on potential new features and bugs based on a user testing script. It took me about two hours to finish. Soon after submitting, I got an email saying they were impressed but wanted another written test before an interview. This second test had broad questions about three user scenarios: describing the current system's capabilities and limitations, explaining how and why to change it, detailing potential impacts on other features, and identifying necessary business decisions. I put a lot of thought into my answers, clarifying that I was making suggestions based on assumptions about their production process and technical infrastructure since I didn't know the specifics. A few days after sending this in, I received a generic HR message stating they didn't have a suitable position for me right now. I tried to follow up with the person who sent the tests, but never got a response. While I don't mind advance written tests, I was bummed not to get an interview or even a personal follow-up, especially after putting so much effort into my responses. Their casual rejection felt a bit rude.

It took a really long time to get through the interview process. I first had a phone interview, then I met in person with my manager and the Department Manager. After that, I had a Google Hangout call with the Controller who's in San Francisco. Then, I had another in-person meeting with the HR Manager, another manager from the Finance Department, and the Department Manager again. Finally, I had a phone call with the CEO in Los Angeles. The whole thing took two weeks and really messed with my work schedule.