Semrush logo

Semrush Software Engineer Interview Questions
& Process

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

Based on 8 interview experiences · FREE TO READ

3.4 Rounds average
Easy Typical difficulty
50% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Semrush.

Showing 3 of 8
Semrush logo
Semrush

Software Engineer

Engineering · nearly a year ago

Senior Average Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical Coding System Design

First, there was a Recruiter Call where we chatted about my background, what the job is all about, what they expect, and also practical stuff like salary and when I can start. Then, a Technical Interview happened, which was all about my coding chops, how I solve problems, and if my experience lines up. This might have included live coding, designing systems, or looking at code. Lastly, I had a Team & Manager Interview with the folks I'd be working with and the boss, to see if I'd fit in, how I work with others, and how I tackle real problems. It was also my chance to ask them about the team and the job.

Confirmed questions2 questions
  • Can you describe your experience using Python?
  • What's your approach to designing backend systems?
Semrush logo
Semrush

Software Engineer

Engineering · nearly a year ago

Senior Average Neutral experience No offer 2 rounds
Interview process
Technical screen Onsite
Interview formats
Technical System Design

The interview process felt pretty laid-back and chatty, not at all high-pressure or formal. It was all about talking through theoretical stuff and system design ideas. There wasn't any coding, live algorithm challenges, or hands-on technical problems – just a deep dive into theory and how to think about architecture. It made the interview feel chill and interesting, not stressful at all.

Confirmed questions2 questions
  • Could you explain the Hexagonal architecture pattern?
  • How would you design a system similar to Google Drive?
Semrush logo
Semrush

Senior Software Engineer

Engineering · more than a year ago

Senior Easy Positive experience Decline offer 8 rounds
Interview process
Recruiter call Phone screen Take home Technical screen Onsite Panel Background check Offer
Interview formats
Behavioral Technical Coding System Design Presentation Other

The interview process started with a call from a recruiter, then a call with the VP of Engineering. After that, I had a two-hour homework assignment which was strictly timed by the recruiter. This was followed by a technical interview and a call with the team. There was also an online psychological test and a call with the HR Director, ending with an offer presentation. I found the process very clear, straightforward, and easy. I completed all stages in just one month, which is incredibly fast compared to other companies. Some stages were quite short, around 20 minutes, and overall the experience was very positive. The only hiccup was during the 'psychological' test where questions about leadership arose. I answered them from a non-management perspective, as I don't want to be a manager. However, it turned out my definition of leadership was different from the company's, which considers mentorship, helping others, developing architecture, and making tech decisions as leadership. This impacted my evaluation negatively, as mentioned by the HR officer.

Confirmed questions3 questions
  • Could you create a production-ready library, complete with tests and a basic CI/CD pipeline, and then discuss your implementation strategy?
  • What can you tell me about the internals of a programming language and common design patterns?
  • Do you understand the fundamental concepts of Kubernetes (k8s)?

Semrush Software Engineer Interview Questions

Quoted word for word from Semrush interview reports.

Could you discuss the advantages and disadvantages of microservices architecture?

Read report

What can you tell me about the internals of a programming language and common design patterns?

Read report

Do you understand the fundamental concepts of Kubernetes (k8s)?

Read report

What's your approach to handling database degradation, specifically with Postgres?

Read report

Could you create a production-ready library, complete with tests and a basic CI/CD pipeline, and then discuss your implementation strategy?

Read report

Formats, difficulty and experience

Across all 8 Semrush interview reports.

Interview formats

Technical 34.8%
Behavioral 26.1%
Coding 17.4%
System Design 13%
Presentation 4.3%

Interview difficulty

Easy 50%
Average 37.5%
Difficult 12.5%

Candidate experience

Positive 50%
Negative 25%
Neutral 25%