Cboe logo

Cboe Software Engineer Interview Questions
& Process

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

Based on 40 interview experiences · FREE TO READ

2.8 Rounds average
Average Typical difficulty
50% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Cboe.

Showing 3 of 40
Cboe logo
Cboe

Software Developer

Engineering · more than a year ago

Mid Average Positive experience No offer 5 rounds
Interview process
Recruiter call Take home Technical screen Onsite Background check Offer
Interview formats
Behavioral Technical Coding

It started with a video call with the hiring manager, focusing mostly on my past experience. Then, I got a take-home assignment where I had to design a simple order book and test it with some trades. The second part involved four interviews back-to-back: first, discussing my take-home project, second, with the hiring manager again about my previous work, third, again discussing my past experience and a challenge on string encoding, and fourth, yet again about my previous experience. The interview wasn't too tough, and the team seemed pretty chill. They were quick with communication, which was nice, but sadly, no offer came my way.

Confirmed questions2 questions
  • Can you design an order book?
  • How would you encode a string?
Cboe logo
Cboe

Software Engineer

Engineering · more than a year ago

Senior Average Negative experience Decline offer 6 rounds
Interview process
Recruiter call Phone screen Take home Technical screen Onsite Panel Presentation Background check Offer
Interview formats
Behavioral Technical Coding Other

I got contacted by a recruiter on LinkedIn and the process kicked off with a recruiter phone screen, followed by a Sr. Manager phone screen. Then, I had a take-home coding assessment which took a few hours. After that, there was a technical interview with 8 people from the team, including the Sr. Manager, other Managers, and Sr. or Principal Engineers. The questions covered culture fit, my work history, technical topics, the take-home assessment, and I also did 3 live coding challenges. I really liked the team I met and thought the interviews went okay, but I knew I struggled with the live coding challenges, so I wasn't expecting to proceed. The process was pretty straightforward until this point. Surprisingly, the recruiter reached out and said they wanted to move forward with me as a 'special case', calling me 'lucky'. I repeatedly asked what this 'special case' offer entailed but got vague, evasive answers. Despite the uncertainty, I really liked the technical folks I met and decided to take a chance on another 'special case' round of interviews. This involved two 30-minute calls with the department's VP and the manager who would be my hiring manager. Both meetings felt a bit aimless, like we were all unsure of the purpose. I received an offer, but it was for a regular Software Engineering role, not Senior, which might have been acceptable given my performance on the coding challenges if the recruiter had been upfront from the start. Instead, I got consistently inconsistent and evasive answers throughout, and felt pressured to accept the offer. Ultimately, I decided not to move forward with the company.

Confirmed questions8 questions
  • Questions about your culture fit
  • Questions about your work history
  • Behavioral questions
Cboe logo
Cboe

Software Engineer

Engineering

Intern Average Neutral experience No offer 1 round
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical Coding

So, I had my first interview with the hiring manager. It was planned for 30 minutes, but he ended up asking me to stay for an hour because he hadn't looked at my resume beforehand. He spent some time reviewing it and then asked me some questions about my current job. After that, he explained the application his team is working on. He then wanted to see if I could understand some code he had written on a whiteboard. I wasn't expecting technical questions in this round, so I hadn't refreshed the technical knowledge I wanted to. I had actually asked the recruiter about the interview format when scheduling, but didn't get a response. Overall, the interview felt friendly and nice. We had a good conversation, but unfortunately, I didn't make it to the second round.

Confirmed questions4 questions
  • What is your motivation for applying to Cboe?
  • Tell me some trivia about JavaScript.
  • Tell me some trivia about SQL.

Cboe Software Engineer Interview Questions

Quoted word for word from Cboe interview reports.

Write a Python function to check if a string is a palindrome.

Read reports

Implement a function to return the nth fibonacci number. Provide both recursive and iterative implementations.

Read reports

How would you find the second highest value in a specific column of a SQL table?

Read reports

Could you explain the logarithmic complexity for data structures like Dictionaries and Binary Trees?

Read report

Could you implement a function that returns the nth fibonacci number, providing both a recursive and an iterative solution?

Read report

How would you read and manipulate data from a binary file?

Read report

Could you create a website feature, specifically a frequently updated price table?

Read report

Can you write a program to analyze market data input and display the top ten symbols by executed volume in a table?

Read report

Formats, difficulty and experience

Across all 40 Cboe interview reports.

Interview formats

Technical 40.2%
Coding 28.3%
Behavioral 27.2%
Presentation 2.2%
Other 1.1%

Interview difficulty

Easy 17.5%
Average 55%
Difficult 27.5%

Candidate experience

Negative 32.5%
Neutral 17.5%
Positive 50%