Sharethrough logo

Sharethrough Software Engineer Interview Questions
& Process

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

Based on 7 interview experiences · FREE TO READ

2.7 Rounds average
Average Typical difficulty
57.1% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Sharethrough.

Showing 3 of 7
Sharethrough logo
Sharethrough

Senior Software Engineer

Engineering · more than a year ago

Senior Easy Neutral experience Decline offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Coding System Design Behavioral

The interview process was pretty quick and the team seemed cool, like we could work together well. But then we talked about the salary, and it was way less than I make now. They told me I was 'chasing money,' and that some people on the team could have gotten double their salary elsewhere but chose this company for its values. I get that, but everyone's different, right? Talking about money needs to be handled with some care. My advice to the managers would be to train the recruiters to talk about compensation more sensitively so candidates feel respected.

Confirmed questions4 questions
  • How would you approach this coding problem collaboratively?
  • Can you walk me through solving this code challenge?
  • Describe your approach to designing a scalable system.
Sharethrough logo
Sharethrough

Software Developer

Engineering · more than a year ago

Senior Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Offer
Interview formats
Technical Coding Behavioral Group

It started with a chat with a recruiter to gauge my interest in the company culture, products, work style, and salary expectations. Then, there was a unique technical interview involving pair programming where I was the navigator, working with the interviewer on TDD to solve easy LeetCode-style puzzles. After that, I spoke with the team lead about my problem-solving approach, past projects, and what I look for in a project. The next step was meeting my potential teammates, the product manager, and the team lead for another pair programming session, this time as the driver, focusing on adding a feature to an existing project. Running out of time on that didn't seem to be an issue. I really liked the pair programming format and felt a good connection. The recruiter followed up quickly with an offer and was helpful with my remaining questions.

Confirmed questions4 questions
  • Can you describe your experience with architecture problems and the outcome?
  • How do you typically approach challenges?
  • Could you share details about previous projects you've been involved in?
Sharethrough logo
Sharethrough

Software Engineer

Engineering

Entry Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Take home Onsite
Interview formats
Coding Behavioral Technical

I applied online and a recruiter quickly reached out to set up a phone interview focusing on technical skills and a coding test to do at home. I completed the test over the weekend and got contacted the next day about an in-person interview. Everyone was really nice and professional.

Confirmed questions2 questions
  • Can you tell me about your background?
  • Do you have experience with algorithms?

Sharethrough Software Engineer Interview Questions

Quoted word for word from Sharethrough interview reports.

Build a basic Scala program, easier than LeetCode problems.

Read reports

How would you approach this coding problem collaboratively?

Read reports

Can you describe your experience with architecture problems and the outcome?

Read report

Formats, difficulty and experience

Across all 7 Sharethrough interview reports.

Interview formats

Behavioral 35.3%
Coding 23.5%
Technical 23.5%
Group 11.8%
System Design 5.9%

Interview difficulty

Easy 28.6%
Average 71.4%
Difficult 0%

Candidate experience

Neutral 14.3%
Positive 57.1%
Negative 28.6%