Conductor logo

Conductor Software Engineer Interview Questions
& Process

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

Based on 9 interview experiences · FREE TO READ

2.7 Rounds average
Average Typical difficulty
77.8% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Conductor.

Showing 3 of 9
Conductor logo
Conductor

Senior Software Engineer

Engineering · more than a year ago

Senior Average Positive experience Accept offer 1 round
Interview process
Technical screen
Interview formats
Coding Technical

The interview included a 30-minute coding assignment and then a 1-hour session with technical questions about the skills mentioned in the job posting. The interview was done by two people.

Confirmed questions1 question
  • Can you name the parts of a URL?
Conductor logo
Conductor

Software Engineer

Engineering · more than a year ago

Entry Average Positive experience Accept offer 6 rounds
Interview process
Take home Recruiter call Technical screen Onsite Panel Presentation Offer
Interview formats
Coding Behavioral Technical System Design

Applied and got an online coding test, then a recruiter call. After that, had a video meeting with an engineer to go over the coding test. Then, I had in-person interviews with some engineers and the Director of Engineering, which was a good experience. The last step was meeting the CTO to ask questions and figure out my team.

Confirmed questions6 questions
  • Tell me about System Design.
  • How do you approach Data Structures?
  • Let's discuss Algorithms.
Conductor logo
Conductor

Software Engineer

Engineering

Mid Easy Negative experience No offer 3 rounds
Interview process
Technical screen Onsite Onsite
Interview formats
Technical System Design

For a programmer role, the process is very step-by-step. It started with a technical screen, then I learned about the company and took time off work for a 5-hour onsite interview. I had already done an initial screening and two technical rounds on-site. However, they decided to discontinue the interview process because they were looking for a more senior developer. This could mean either they didn't review my resume properly or the feedback from the two rounds was negative. I felt I performed well in both face-to-face rounds and wasn't bad enough to warrant discontinuation. I believe candidates should be given a chance to improve in subsequent rounds even if they don't perform optimally in one. It felt like a complete waste of my day, and I hope the company will be more considerate of candidates' time in the future.

Confirmed questions2 questions
  • Could you implement a data structure?
  • Can you design something based on the company's work?

Conductor Software Engineer Interview Questions

Quoted word for word from Conductor interview reports.

Can you write a function that takes a string representing an equation and returns its result as a string? For example, if given "5 + 14 + 80 x 4 / 8 - 6", return the answer as a string. Just use a brute force method and don't worry about complicated data structures.

Read reports

Formats, difficulty and experience

Across all 9 Conductor interview reports.

Interview formats

Technical 35%
Coding 35%
System Design 15%
Behavioral 15%

Interview difficulty

Easy 11.1%
Average 88.9%
Difficult 0%

Candidate experience

Negative 22.2%
Positive 77.8%