
Sinch Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 16 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Sinch.
Software Engineer
I had a great technical interview today. First, I explained how TypeScript works under the hood, walking through how the compiler uses the Abstract Syntax Tree for type checking before emitting JavaScript. Then, I tackled a medium LeetCode string problem using a straightforward sliding window approach. It went smoothly!
- Can you explain the internal workings of TypeScript, including its use of the Abstract Syntax Tree for type checking prior to JavaScript emission?
- How would you approach solving a medium-difficulty LeetCode string problem using a sliding window technique?
- Regarding system design, can you discuss a KeyValue Store?
Software Engineer
It started with a quick 15-minute chat with the recruiter about the job and what they're looking for. After that, I had a 45-minute meeting with the engineering director. We mostly talked about my resume and what I've done before. They did most of the talking and it didn't feel like a super intense interview. The next step was a 1-hour panel interview with a principal and a senior software engineer. They really dug into the technical stuff, asking about my skills in Kotlin, OOP, Docker, agile, pair programming, concurrency, Spring, event-driven design, RabbitMQ, and log tracing. I felt pretty good about how that went and thought my skills were a good match. A few days later, the recruiter said they'd need about a week to collect feedback from everyone. I waited over a month and didn't hear back, so I guess they went with other people.
- Can you share your opinions on Kotlin, covering both aspects you dislike and enjoy?
- Could you elaborate on your resume and previous work experiences?
- What are your views on pair programming?
Software Engineer
The interview process started well, with a recruiter call to align expectations, followed by a good technical interview where the interviewer was professional and attentive. Then, I received a take-home assignment with a week to complete it. Two days before the deadline, they informed me I had missed it, which was incorrect as I still had two days left. They acknowledged the error and extended the deadline by two days. I submitted the project early, including notes on areas needing improvement due to time constraints, as I was still employed elsewhere. The next morning, I received feedback, which seemed AI-generated, rejecting me. The feedback mentioned the same improvement points I noted and contradicted itself by praising my test suite coverage while citing insufficient coverage as a rejection reason. It was frustrating as the company and project seemed appealing.
- Could you build a contacts API with authentication using just Java core and Gradle?
- How do you balance urgency and deadlines with product team demands?
- What's your perspective on observability and monitoring?
Sinch Software Engineer Interview Questions
Quoted word for word from Sinch interview reports.
“What's the behavior in Go when reading from a channel that's already closed?”
Read reports →“What does HTTP status code 500 mean?”
Read reports →“What is the middle node of a linked list?”
Read reports →“Is Go considered an object-oriented programming language, and what's its connection to OOP principles?”
Read reports →“Can you explain the difference between threads and processes in Java?”
Read report →“Can you explain the internal workings of TypeScript, including its use of the Abstract Syntax Tree for type checking prior to JavaScript emission?”
Read report →“Could you build a contacts API with authentication using just Java core and Gradle?”
Read report →“How would you implement this cache, specifically regarding the use of Mutexes?”
Read report →“What is your understanding of log tracing?”
Read report →Formats, difficulty and experience
Across all 16 Sinch interview reports.