Software Engineer applicants have rated the interview process at Tipalti with 2.9 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 41% positive. To compare, the company-average is 48.3% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 8 days to get hired, when considering 17 user submitted interviews for this role. To compare, the hiring process at Tipalti overall takes an average of 20 days.
Common stages of the interview process at Tipalti as a Software Engineer according to 17 Glassdoor interviews include:
Phone interview: 37%
One on one interview: 19%
Skills test: 19%
Presentation: 11%
Other: 7%
Personality test: 7%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 1 week. I interviewed at Tipalti in Oct 2023
Interview
First - HR Call 30 min.
Second - Code interview. 1.5 hour
Third - Design Interview. 1.5 hour
Fourth - HR before contract.
The process exists remotely in Zoom. They are nice people
Interview questions [1]
Question 1
You have 1 hour to do a task - You get a class and you need to using in reflection and print his attributes.
I applied through an employee referral. I interviewed at Tipalti (Tel Aviv-Yafo) in Oct 2025
Interview
They made me a design about things related to the company, questions about payments and the flow between services.
I was given a question about transferring funds from the company to the bank.
I applied online. I interviewed at Tipalti in Oct 2025
Interview
Interviewed with the recruiter which was very brilliant, kind and helpful. Then head towards the tech interview.
Unfortunately, the technical interview experience was the complete opposite. It felt unprepared and quite awkward. The panel consisted of one junior and one senior engineer, both of whom were very quiet and difficult to engage with, which made the interview uncomfortable.
During the technical tasks, it felt like they already had a specific solution in mind and were reluctant to discuss alternative approaches, despite software engineering often allowing for multiple valid implementations rather than a single “correct” answer.
This was disappointing, as it negatively impacted what could have been a positive experience and left me feeling that my chances were undermined by the interview setup rather than my ability. I hope future candidates have a more structured and collaborative technical interview experience.