
Localytics 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
Candidate interview experiences
First-hand accounts from people who interviewed at Localytics.
Software Engineer
It started with a small take-home task sent by email, doable in a few hours. After that, a standard coding interview via Skype. If that went well, they invited me for an onsite interview. The onsite involved a mix of design questions (I got one), coding questions (we had an in-depth discussion on a data structure), and a larger, more complex version of the initial take-home task, which I had about an hour and a half to complete. The overall experience was good, and the engineers focused on my problem-solving approach. So, even if the problem is unfamiliar, keep trying; they'll offer some assistance.
- Focus on system design questions. Study how to construct scalable systems.
- The tasks involve getting data out of multiple JSON files, which you can consider as database tables.
- You should be prepared to handle this task in a language good for file handling, like Python, which I used.
Software Engineer
It started with a quick phone chat, then a full day of in-person interviews. The interview day included a programming test where they'd give you a computer and a paper with problems, then leave you alone. They'd give you a very brief description of what you'd be working on before you get there. They'd say you can program in any language and ask what you'd prefer. Be warned, there are right and wrong answers to this question, and answering incorrectly means you probably shouldn't even bother showing up. It's crucial to be experienced with the technologies they use. They might say it's not important, but since most questions involve sample code or programming in those languages, you'll be at a major disadvantage if you're not at least moderately skilled. You could be a great engineer, but if you have to ask about syntax for Ruby or Javascript, you'll lose points. One bad interview can end your chances. After all that, it took about 2 weeks to hear back, which is a long time for a company to communicate, especially if they're not moving forward. The overall experience was negative, mainly because of the zero communication after the in-person interviews.
- Would you be able to do pair programming in a language that you aren't familiar with?
Software Engineer
Did a short take-home coding challenge, then an in-person interview. It was a pair programming session with one engineer and some whiteboard design discussions with others. I interviewed here before, got rejected the first time because they said I wouldn't learn the language fast enough. I learned it at another job. This time around, they rejected me saying the team felt I didn't know any more than they did. They're super picky and don't know how to hire, you'll just waste your time so don't bother.
- Implement the game of life
Localytics Software Engineer Interview Questions
Quoted word for word from Localytics interview reports.
“Implement the game of life”
Read reports →“Given 2 TSV files, read them and answer questions based on the data within them.”
Read reports →“Can you extract data from a JSON file and then perform different kinds of summary and aggregation operations on it?”
Read reports →“What about control flow in JavaScript?”
Read reports →“What about software architecture?”
Read report →“Can you discuss Functional Programming and related JavaScript concepts?”
Read report →“And some logical tasks?”
Read report →“Would you be able to do pair programming in a language that you aren't familiar with?”
Read report →“Were there any data mining questions?”
Read report →Formats, difficulty and experience
Across all 9 Localytics interview reports.