e-Builder Business Analyst interview questions

eBuilder's team and offices both appeared modern and professional. Their HR staff handled my inquiries as well as can be expected and with timeliness. After two phone interview rounds (and initial pre-screen with the recruiter) I was asked to visit the Ft Lauderdale location for an on-site final round interview (three hours, four blocks of 30m each with a break before a requirements assessment roleplay) after which I was not extended an offer. I bear no ill will toward the eBuilder staff and having worked in a hiring managerial role I can completely grasp their stylistic approach; but I can also definitely agree I was not a good fit for their team after being on-site. In contrast to the upbeat and free-flowing discussions of the phone interviews, I witnessed a more robotic and less genial staff on-site. I get it: nobody wants to come offline from their responsibilities in order to sit with a candidate who may or may not end up part of the staff; but I come from a more modern 'startup-style' world wherein candidates are looked at as potential members of the team to woo and generate a positive impression. Instead I was met with a barrage of standard interview questions that could have (and frankly usually are) a function of phone interviews, prior to an on-site. The staff I witnessed was dour at best (with the exception of the office manager and HR team members that clearly had their best foot forward in stark contrast), and the team members I saw returning after their lunches definitely didn't give the impression of an engaged and excited workforce. The senior team members I met with very clearly had other things to do judging by their rather hurried interactions, general lack of engagement, or constantly buzzing phones (I'm surely not the only one that engages 'Do not Disturb' mode for meetings), or other things on their minds at the very least. Working in sales I know what it looks like to have an engaged audience: I couldn't help but feel like I was wasting everyone's time by being there, which definitely doesn't beget the most positive experience. The BA role at eBuilder is highly consultative in a waterfall environment with a 'configure' versus 'sprint-develop' approach to implementations over 7-8 weeks to delivery: if you read this and think 'Are they working in 1995?', odds are good you're not going to be a great fit. After two hours of a lukewarm reception we executed a roleplay scenario wherein the slate of interviewers ironically portrayed themselves: reticent and withdrawn senior client representatives whom I was tasked with drawing out requirements data. If the goal was a trial by fire, the previous hours were an excellent setup for the finale, and it definitely showed their operational style and level of client buy-in. If sales hasn't already cleared the path for clients to meet the "What would you say your biggest issues are?" question with something besides "Everything seems fine actually- not sure why we're all sitting here?" then there's a huge gap in the client onboarding process. I left their offices trepidatious, at best, and in retrospect am slightly glad I was not extended an offer: I would have been put in a difficult position to decide between what I experienced and my existing role in an agile and fluid environment, and that's a hard call to make. eBuilder works in a change-reluctant industry (construction) merged with a highly dynamic one (software) and I imagine it takes a very specific style of individual to take on their unique challenges; it appears I wasn't that fit. I wouldn't call this a 'negative experience' because it taught me a lot about what signs to look out for in other interview processes going forward, and further reminded me how lucky I am in my present role. The eBuilder interview was a lot like going out to the bars with your single friends as a married person and watching the rather disappointing and exhausting mating rituals: you can't help but sigh with relief when you go back home to your spouse and realize you'll never have to deal with that again. Stray thoughts: Retention appears to be an issue based on some interview questions. I'm not especially surprised. Their staff takes their lunches offline. That's rather telling about rigidity, but also means you won't have much luck reaching someone over your lunch break if that's the time you have free for personal matters (like phone interviews) in your current role. Not a knock against them, of course. BAs are heavy travel consultants at eBuilder- 75% travel is a little confusing in the post-Skype/videoconference/screensharing world for a software product. This definitely should've been a red flag, because it is. eBuilder is very much what it says on the tin. I wouldn't recommend expecting a dynamic and vibrant workforce. An on-site is as much a sales pitch for the employer as the employee and if I failed, I'd have to argue they did too.

The interview process was very long. I think they were hesitant about bringing me on and that's why it took so long to hear back. I also had two final round interviews. In the end, I had to decline the offer, unfortunately. I had one phone screening then they flew me for a day of in-person interviews. It was very long, and I met with about 5 people for a 30 minute interview each. The last step was the role play scenario. It wasn't as bad as I thought it would be. I was told I would be contacted with next steps within a few days; however, I didn't hear back for almost 3 weeks. Then, I was asked for another final round interview (phone interview).