Sensor Tower logo

Sensor Tower 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

3.3 Rounds average
Average Typical difficulty
28.6% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Sensor Tower.

Showing 3 of 7
Sensor Tower logo
Sensor Tower

Software Engineer

Engineering · more than a year ago

Entry Average Negative experience No offer 2 rounds
Interview process
Take home Technical screen Phone screen
Interview formats
Coding Technical Behavioral

I had a terrible interview experience. It started with a Codility test which I aced. Then I was scheduled to speak with the hiring manager. Before that, I asked the recruiter what to expect, and they said it would be a casual chat about my resume and some problem-solving. However, on the day of the interview, the hiring manager was 30 minutes late. When he finally showed up, we immediately jumped into a virtual whiteboarding session on Google Docs. He didn't ask anything about my background or projects, nor did we discuss the company or role. I wasn't prepared for live whiteboarding, as I don't practice Leetcode much, and I find it hard to perform under pressure. The manager seemed surprised, and I mentioned the recruiter's misleading information. He offered another chance, possibly with another Codility test, but I was ultimately rejected.

Confirmed questions1 question
  • Calculate the rolling average of N items
Sensor Tower logo
Sensor Tower

Senior Software Engineer

Engineering

Senior Average Negative experience No offer 4 rounds
Interview process
Recruiter call Take home Technical screen Phone screen
Interview formats
Technical Coding Behavioral

I applied via Stack Overflow and the initial step was a recruiter phone screen. After that, I received a take-home assignment in Ruby, which was to build a CSV parser. Once that was submitted, I had a 1-hour phone call with an engineer. I thought this would be a general technical discussion, but it turned out to be a live coding session, which I wasn't explicitly told about beforehand. The engineer sent a CoderPad link, and we started with the first coding problem: grouping anagrams. I finished that quickly, and then we moved to a second coding problem. While I was setting up the structure for the second problem, the engineer wanted to discuss a key implementation detail extensively. It felt more like an evaluation of my ability to discuss and communicate technical concepts rather than finding a specific solution. With very little time left, the engineer suggested using an external library for the problem, which seemed to contradict the idea of solving it from scratch. In the final few minutes, I was given the opportunity to ask questions about the company, which was also the only chance to ask technical questions. The engineer didn't ask me anything about my background or experience, not even at the start of the call. I followed up the next day and heard back from the recruiter who sheepishly explained that the engineer felt my skills weren't up to par for a senior role.

Confirmed questions4 questions
  • I was asked to create a parser for CSV formatted files as a take-home assignment.
  • For the live coding portion, I needed to group words that are anagrams of each other.
  • I was asked to discuss implementation details for the anagram grouping task.
Sensor Tower logo
Sensor Tower

Software Engineer

Engineering

Mid Average Positive experience Decline offer 5 rounds
Interview process
Recruiter call Take home Onsite Onsite Offer
Interview formats
Coding Presentation Coding System Design Behavioral

I applied via referral. First, there was a recruiter phone screen, then a take-home coding challenge. After that, I had an on-site product demo, and then a full day of on-site interviews. The whole experience with Sensor Tower's engineering recruiting team was amazing. The recruiters and interviewers were attentive, engaging, and the whole process felt really personal. A couple things I really liked: the recruiters took the time to get to know me and found common ground to connect with the company culture. The interview process was collaborative; they actively asked how they could make me feel comfortable in the office. They also had an open lunch where I could meet more of the team in a relaxed setting, but introverts could also opt out to recharge privately. It was clear they value their team dynamics. The offer was very good from the beginning, and negotiating the offer felt like a fair and open discussion. Honestly, Sensor Tower is the first place I'd look to work again.

Confirmed questions5 questions
  • How would you approach algorithm problems in a coding quiz?
  • Can you demonstrate your pair coding and communication skills?
  • Tell me about your approach to system design.

Sensor Tower Software Engineer Interview Questions

Quoted word for word from Sensor Tower interview reports.

How would you approach algorithm problems in a coding quiz?

Read reports

What are your thoughts on product-focused engineering discussions?

Read reports

How do you see yourself fitting into a customer-oriented and product-driven engineering team?

Read reports

Formats, difficulty and experience

Across all 7 Sensor Tower interview reports.

Interview formats

Coding 31.6%
Technical 31.6%
Behavioral 26.3%
Presentation 5.3%
System Design 5.3%

Interview difficulty

Easy 0%
Average 85.7%
Difficult 14.3%

Candidate experience

Positive 28.6%
Negative 57.1%
Neutral 14.3%