Bottomline logo

Bottomline Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 142 interview experiences · FREE TO READ

2.8 Rounds average
Average Typical difficulty
48.9% Positive experience

Which role are you interviewing for?

30 roles · 142 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Bottomline.

Showing 4 of 142
Bottomline logo
Bottomline

Software Engineer

Engineering · a year ago

Entry Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen
Interview formats
Behavioral Technical Coding

So I had four interviews. First was like a quick chat with the recruiter, just talking about me and the job. Then I talked to the director of software engineering, and he hit me with some technical questions on the tools we use like Java and SQL. After that, I had a chat with a senior software engineer. He asked more tech questions, plus stuff about data structures and algorithms, like how to reverse a string in Java and how to handle matching parentheses. I didn't actually code live, just talked through my approach. The last interview was with the VP of engineering, and he asked a lot of the same technical questions. It all seemed to go well, but they ended up hiring someone with more experience.

Confirmed questions4 questions
  • Can you explain what a SQL trigger is and its use cases?
  • Describe your approach to reversing a string in Java.
  • How would you approach solving the matching parentheses problem?
Bottomline logo
Bottomline

Account Manager

Sales · a year ago

Mid Average Negative experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Behavioral Technical

A recruiter from the company contacted me on LinkedIn about a job opening. I went through a total of 4 interviews. The interviews themselves were good, but scheduling them was a real hassle. I had to keep following up for weeks just to get updates, and they'd either ignore me or say they were still interviewing. My first interview was in early November, and the next two were within a week. After a lot of chasing, I finally got the fourth and final interview scheduled, which was a full month after the third. Then, silence for another month despite my constant check-ins. I finally got a hold of the recruiter, who told me the team liked me but their priorities had shifted and they were no longer hiring for that role, but rather for someone more junior. So, two months of my time were wasted because they reached out to me and then decided not to hire for the role after a lengthy process.

Confirmed questions1 question
  • Could you describe some of your Key Performance Indicators?
Bottomline logo
Bottomline

Customer Success Manager

Sales · a year ago

Mid Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen
Interview formats
Behavioral

I was contacted by a Senior Recruiter on LinkedIn and had an initial call that went well. She suggested I move on to the next stage, which was an interview with the Manager of Customer Success. A Zoom meeting was set up, and I joined a minute before it was supposed to start. I ended up waiting for about 15 minutes, but the manager never showed up. After that, my attempts to contact the recruiter to reschedule were met with silence. I get that companies might choose other candidates, but it's basic courtesy to at least let someone know instead of wasting their time. It was totally unprofessional, and if that's how Bottomline operates in other departments, I'm glad I didn't get involved further.

Confirmed questions1 question
  • Can you tell me about your current role and your experience?
Bottomline logo
Bottomline

Principal Engineer

Engineering · more than a year ago

Staff Average Positive experience No offer 2 rounds
Interview process
Recruiter call Technical screen Phone screen
Interview formats
Technical Coding Behavioral

Applied online for the Principal Engineer role. Had a recruiter call on July 18th, 2024, and the first technical interview was set for July 31st, 2024. The first interview was good, the interviewer was humble and realistic, even letting me reference materials. It focused on experience and problem-solving approach rather than memorization, which was appreciated. I advanced to a second round with the engineering manager. However, during the first round, I realized the job expectations didn't align with my view of a Principal Engineer role. I discussed this with the engineering manager in the second round and decided not to proceed due to the mismatch.

Confirmed questions7 questions
  • Can you write Java Stream code to process a list of 6 numbers, printing 'A' for divisibility by 2, 'B' for divisibility by 3, and 'C' otherwise, ensuring the loop runs only once?
  • Explain how to implement web security in a Java Spring Boot application.
  • Describe the idempotent principle and identify whether PUT or PATCH is idempotent.

Bottomline Interview Questions

Quoted word for word from Bottomline interview reports.

What do the URLs typically look like for PUT and PATCH requests?

Read reports

What is the difference between a parent and a child pipeline in git?

Read reports

Does Ansible operate in a pull or push mode, and is agent installation a requirement?

Read reports

Can you write Java Stream code to process a list of 6 numbers, printing 'A' for divisibility by 2, 'B' for divisibility by 3, and 'C' otherwise, ensuring the loop runs only once?

Read reports

Can you explain the distinction between git fetch and git pull?

Read report

Could you write pseudocode to identify the longest substring that does not have any repeating characters?

Read report

Could you explain what 'init' means in the context of Python?

Read report

Could you outline the steps for writing a Dockerfile to install Nginx?

Read report

Given a feature branch with updates and a master branch, what's the procedure for merging?

Read report

Formats, difficulty and experience

Across all 142 Bottomline interview reports.

Interview formats

Behavioral 41.9%
Technical 34.2%
Coding 9.7%
Other 5%
Presentation 3.7%

Interview difficulty

Easy 19.7%
Average 66.2%
Difficult 14.1%

Candidate experience

Negative 29.8%
Positive 48.9%
Neutral 21.3%

Reports by job function

Engineering 59
Operations 25
Sales 17
Analytics 11
Other 11
Finance 7