Zuora Consultant Interview Questions
& Process

First round was a phone interview with a recruiter where they asked about my experience and some technical stuff. Second round was with the hiring manager, also a phone interview, and they asked more about my experience and technical topics. Third round was on-site and involved four 45-minute interviews. It was more technical questions than behavioral. They had me do whiteboarding for pseudo-code, look at code snippets, asked a couple SQL questions, some IQ riddles, and a few 'Tell me about a time when...' questions. My background was a good fit because my work experience was similar to the job description. They asked about programming buzzwords, and I was honest about not knowing some since college and that I'm not a developer. The second interview went well; they said I was a good culture fit and had good communication skills. I was again honest about not being a developer, only having taken programming classes in college and not using Java post-college. I explained my code interaction was limited to modifying, fixing bugs, testing, and occasional Salesforce Apex triggers, not full development. I didn't want to misrepresent myself. They seemed to appreciate my honesty and weren't concerned I lacked deep knowledge of algorithm complexity or APIs. I double-checked the job description, which mentioned 'familiarity' and 'understanding' of OOP, and stated only 50% of the role was technical. The third interview, however, was very technical. I did well on behavioral and riddles, but the coding questions were very difficult, and it was humiliating when each interviewer asked variations of 'Do you feel unqualified for parts of this job?'. Overall, they were nice, but it was a waste of time, and I tried to avoid this exact scenario multiple times. My advice to Zuora is to update the job description to clearly state they need actual development experience.

I first connected with Zuora at a job fair and spoke with an SVP, which made me feel they were genuinely seeking candidates. Following that, I was invited to their HQ for in-person interviews and had two additional interviews via Skype. The interviews were challenging but enjoyable because the interviewers were very organized. The process began with an overview of Zuora's business and system architecture, followed by an explanation of how my role fits into the bigger picture. They then inquired about my background, experiences, and future plans. I was impressed by how enthusiastic and proud everyone was about the company's growth and their work. This experience solidified my desire to work there with that team.

I initially met the hiring manager at a school information session. We had a good conversation, and he gave me his business card. He mentioned the possibility of a part-time role before graduation and a full-time position afterward. Following up via email, I was contacted by an HR representative who scheduled a technical interview at a local office. The questions were fairly straightforward and the interview lasted about an hour. Later, HR informed me they wanted to proceed and invited me to their Atlanta office for a second interview. Although it was presented as a meeting with a VP, it turned out to be another technical interview, focusing more on intellectual and mathematical problems than programming. About a week after that, I received a rejection email stating I needed more computer science coursework and should reapply after graduation. It was frustrating because I felt this could have been addressed during the initial resume review, saving me considerable time and effort, especially since I had prepared extensively and endured long commutes during rush hour for both interviews. When I inquired about the reasons for rejection, the HR staff mentioned the second interviewer felt my programming skills were weak. This was surprising given the second interview heavily featured logic puzzles like the 'heavy ball' problem, which I solved quickly. I'm unsure how my programming ability was assessed. I also asked about the mentioned part-time position, but was told it was never an opening, which left me feeling misled. On a side note, I observed that many staff members seemed to be from the same university. Despite my background from a top university, there were comments about my school, and I perceived some bias during the process, suggesting a preference for candidates from their alma mater.