
Talon.One Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 83 interview experiences · FREE TO READ
Which role are you interviewing for?
27 roles · 83 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Talon.One.
Technical Writer
I applied in November 2024 and heard back quickly from a recruiter who set up an interview with the Hiring Manager. We had a good conversation where they asked about my background and my thoughts on the technical writing process. They seemed more focused on design thinking than my technical skills, which was cool. It felt like a low-pressure initial chat. I then got a take-home assignment, which I submitted. After waiting about two weeks for feedback, it felt off, like it wasn't even for my submission.
- Can you share your experience?
- What are your thoughts on the technical writing process?
Senior Backend Engineer
You'll start with a recruiter call that's basically a cultural fit interview. Then there's a technical coding challenge where you'll spend a few hours designing and implementing a solution for something. After that, you'll have a take-home challenge, followed by a technical review of your take-home. Many high-level managers and senior developers reviewed my project. They let me know based off the work I submitted that this company is most likely using people for free work. RED FLAG!!!! They expect you to build a fully functioning production ready service to integrate with their existing software for your 'take home'.
No confirmed questions were included in this interview report.
Senior Software QA Engineer
The interview process was pretty fast and organized at the start. I did a screening call with HR, then an interview with the hiring manager. After passing both, I got a QA automation task to do, which I finished and sent back within 3 days. Sadly, I got rejected just because of typos in the README file with the project. They didn't even look at how I designed or approached the task. I asked for more helpful feedback, but they said they didn't have the time and wouldn't share anything else. It started out good, but it was disappointing not to get useful feedback and to be judged on small mistakes instead of the actual work.
- In the initial screening, I was asked about the key differences between a good and a bad QA engineer.
- The subsequent interview was more technical, probing into my methods for handling tasks and challenges from past positions.
Product Manager
First, they check your resume. Make sure to tailor it to the job description. If you're shortlisted, you'll move to the next stage. Then, there's an HR round where they check if you understand the role and the company well. It's important to read Talon One's blogs and documentation. Also, know yourself well. The next is the Hiring Manager round, a great conversation to dive deep into product management and your experiences. After that, there's a task that really shows the company's understanding of Product Management and Ownership, pushing you to think about your past experiences. Make sure to focus on the problem side and consider different angles and stakeholders. Finally, you'll meet the team from engineering, design, and strategy. This simulates a real work situation where you discuss the case in depth. There's also a two-way culture/team fit assessment. I found the process difficult because many companies don't focus enough on the problem side of tasks. Talon.One is a pleasant surprise! The interviewers are friendly and create a relaxed atmosphere, making it feel more like talking to colleagues.
- Tell me about your previous PM experiences.
- The questions on the task are comprehensive that come up during the discussion.
Talon.One Interview Questions
Quoted word for word from Talon.One interview reports.
“What are the differences between Slices and Arrays in Go?”
Read reports →“What is the difference between a buffered and unbuffered channel?”
Read reports →“Could you please provide a legal opinion regarding the seminar that Talon.One organized in Berlin?”
Read reports →“How would you create a coupon in Talon.One and ensure a successful response is received in Postman?”
Read reports →“How would you explain binary search to someone who isn't technical?”
Read report →“What approaches exist for incorporating testing into software development workflows?”
Read report →“Do you have any general questions regarding the Golang language?”
Read report →“What are your thoughts on why people from my country might be perceived as not straightforward?”
Read report →“What are some top Customer Success strategies and best practices?”
Read report →Formats, difficulty and experience
Across all 83 Talon.One interview reports.