Boston University Interview Questions
& Process

I had four interviews with different senior folks on the team. It was a pretty solid process, and I got a good sense of the job and the team vibe. First up was the lead consultant, and we talked a lot about my past projects, my tech skills, and if my background fit what they needed. They really dug into things, so I knew they were checking my knowledge and how I solve problems. Then I met with the hiring manager, who would be my boss. We covered how the team works, what the daily grind is like, and their current projects and challenges, and how I'd handle them. It wasn't super technical, more about fit and communication. After that, I talked to a manager from a team that works closely with them. This one was super technical, covering big data, HPC, distributed systems, and the future of cloud computing for science. They also asked about my thoughts on new tech and future trends. The last interview was with another senior person. This was all about the deep technical stuff from my past work that relates to what they're doing now, and also my research interests and how they might grow with the team's goals.

There were two interviewers. One asked most of the questions. Besides the usual HR questions, he noted the high competitiveness: 'there are 250 applications and only 2 openings.' I heard others who were rejected also got this info, so I'm not sure if it's a subtle rejection signal or a typical thing at this university. The other interviewer tested my foreign language proficiency. We had a good talk with promises, but no follow-up.

So I applied for this Salesforce Business Analyst job. After the recruiter first talked to me, there were three more rounds. The first round was with the VP of a department and the BA practice manager, and they asked me about my BA skills. The second round was with the lead project manager of the department and the executive director of applications at BU, and we talked about the Salesforce projects and my Salesforce background. The last round was with the manager I'd be reporting to directly.

So, the interview process kicked off with a phone interview, which was basically a recruiter screening. They asked about my experience, past projects, my reasons for seeking a new role, and my knowledge of the company. It was about 30 minutes, just to check if I was a good fit for the job and company culture. Then came the coding interview, done online with a shared editor. I had to solve some algorithm problems – challenging enough to make me think, but they cared more about my problem-solving approach than a perfect answer, so I talked through my thinking. After that, it was a deeper technical interview focused on system design. I was asked to design a messaging system, using a virtual whiteboard to go over databases, APIs, scaling, and error handling. It was more of a collaborative discussion that really tested my architecture skills. The fourth stage was a behavioral interview with a senior manager. It was all about teamwork, how I communicate, and deal with conflict, using a lot of 'tell me about a time' questions. The STAR method was really helpful for this. Finally, there was a virtual lunch with some team engineers. This was a more relaxed round, focused on culture fit, getting to know me as a person, and we chatted about tech, personal projects, and even hobbies and funny tech stuff.