Toggl logo

Toggl Interview Questions
& Process

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

Based on 136 interview experiences · FREE TO READ

3.1 Rounds average
Average Typical difficulty
61% Positive experience

Which role are you interviewing for?

30 roles · 136 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Toggl.

Showing 4 of 136
Toggl logo
Toggl

Solutions Engineer

Engineering · nearly a year ago

Mid Easy Positive experience Decline offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Coding System Design Behavioral Case

You begin with an online application where you submit your resume, cover letter, and sometimes portfolio or GitHub links. Next, an HR or talent partner screens your profile to see if you're a good fit based on your skills, experience, and education. Then, there's a 15–30 minute introductory call with a recruiter to confirm your motivation, communication skills, and salary expectations. Following that, you might get an online test or a take-home assignment, which could involve coding, data analysis, or prompt-engineering tasks. Finally, there's a 45–60 minute virtual technical screen focusing on problem-solving, algorithms, or case studies. For tech roles, this might include system-design or Python challenges, while consulting roles could involve a client scenario or case-based reasoning.

Confirmed questions4 questions
  • coding questions
  • questions about system design
  • behavioral questions
Toggl logo
Toggl

Product Designer

Design · a year ago

Senior Difficult Positive experience Accept offer 5 rounds
Interview process
Take home Technical screen Onsite Presentation Offer
Interview formats
Technical Behavioral Coding Presentation

The hiring process at Toggl was really well put together, efficient, and felt considered. It was a good chance for me to show what I can do and also to check if Toggl was a place I'd want to be. The HR people were super quick to reply, updating me basically every week, so I never had to wait around wondering what was happening. My whole hiring journey took about two months and went through a few steps: - An automated test with some open questions, where I got an instant score and a pass/fail for the next round. - An async screening where I had to answer some company culture and behavioral questions on camera via their system. - A home assignment that I had a week to finish, but it was timed once I started, giving me only 2 hours to do it, to make sure I didn't take too long. The task was about finding, ranking, and fixing a problem in their product, and I had to record and send my solution within that time limit. - A technical chat with the Design Lead and a PM, where we talked about my past work and my ideas from the home assignment, plus behavioral and technical questions, especially around working together and communicating. - A paid test week where I worked on actual design tasks with potential colleagues, ending with a final presentation. - Job offer I felt really sure about wanting to work at Toggl after all these stages and how involved I got, so I was happy to accept.

Confirmed questions5 questions
  • Can you tell us about your experience working remotely and with Toggl?
  • What are your career aspirations for the next three years?
  • What suggestions do you have for enhancing Toggl Track?
Toggl logo
Toggl

Product Manager

Product · a year ago

Senior Average Positive experience No offer 5 rounds
Interview process
Take home Technical screen Recruiter call Onsite Background check Offer
Interview formats
Technical Coding Case Behavioral Presentation

I made it to the final stage, and I really liked the interview process at Toggl. It was fun and gave a good look into the company and their product vibe. It felt well-put-together, good at checking if you have the right skills and fit for a remote-first, PLG company. First, there was an async test on finding products, deciding what's important, and solving problems. Then, another async interview about making decisions and working with others. After that, an async home task where you have to record yourself. Then, a technical chat with the Head of Product about your past work, how you plan roadmaps, and PLG stuff. If all goes well, there's a paid testing week. It was thorough, but I felt the target candidate profile wasn't clear throughout. The early parts and the feedback made me think they wanted one type of person, but the final interview showed they were looking for something else. This was a bit confusing and made it hard to show my experience that really matched what they eventually wanted. It would be better if the job description and the questions asked were more aligned. For experienced folks like me, having clear expectations from the start helps us focus on the most relevant parts of our background, especially in the later stages when a lot of time has already been spent.

Confirmed questions8 questions
  • What's key in product discovery?
  • How does a PM work with and help the dev team?
  • What would you do if a product metric suddenly dropped?
Toggl logo
Toggl

Product Manager

Product · a year ago

Senior Average Negative experience No offer 5 rounds
Interview process
Recruiter call Take home Background check
Interview formats
Behavioral Technical Presentation

I'd advise skipping this interview process, even though the role looks super appealing. I do have to say the HR folks who reach out via email are really professional. But, it's a tough process for the candidate and super quick for toggl. The first three stages are automated. Stage three involved a home assignment where I had to improve their current pricing plans, which took several hours. They also wanted a presentation video of it. I got rejected after sending the home assignment without even talking to the hiring team about my work. I would have preferred to be rejected at stage one and not waste hours providing free consulting disguised as a company-specific home assignment.

Confirmed questions3 questions
  • Can you share an example of a product you successfully launched and how you measured its success?
  • Tell me about a feature you launched and what lessons you learned that would lead you to make different choices now.
  • What qualities do you look for in a product team you'd want to collaborate with?

Toggl Interview Questions

Quoted word for word from Toggl interview reports.

Write code to find the length of the last word in a given string.

Read reports

Based on the provided data in the table, what is the calculated average CPM?

Read reports

If a negative phrase match XXX is implemented, for what search terms would the ad still be displayed?

Read reports

Implement a simple REST API parser in JS, then display and manipulate the data it received.

Read reports

Given the use of Broad Match modifiers, which keywords would be activated by these specific search terms?

Read report

Can you write a function that calculates the total number of beer bottles bought, given an initial amount of money, by repeatedly buying beers and selling empty bottles until the money runs out?

Read report

Can you explain what React Pure component is and how to use it?

Read report

What is considered the most effective content type for attracting users who are likely to convert, with choices relating to long-tail keywords and user intent versus specific targeted keywords?

Read report

Can you provide examples of how to optimize the 'data-ink' ratio in a bar chart?

Read report

Formats, difficulty and experience

Across all 136 Toggl interview reports.

Interview formats

Technical 35.7%
Behavioral 22.8%
Coding 16.2%
Presentation 11.4%
Other 7.2%

Interview difficulty

Easy 11.8%
Average 64.7%
Difficult 23.5%

Candidate experience

Positive 61%
Negative 25.7%
Neutral 13.2%

Reports by job function

Engineering 51
Product 30
Sales 16
Design 15
Marketing 15
Operations 7