Real, anonymous reports from people who interviewed for Software Engineer at Tipalti, newest first and distilled into what to expect across the loop.
My process started with a recruiter outreach and then quickly turned into work that felt very connected to Tipalti’s product domain. I was given a design-style question that focused on how payments-related parts of the system work, especially the flow between services.
After talking with a recruiter by phone, I moved into a Zoom sequence that felt very structured. The first technical screen was a short session that still included a LeetCode-style problem, and I had to talk through my approach as I worked.
The initial recruiter outreach is generally positive and supportive, setting a friendly tone for the process, although some candidates noted inconsistencies in scheduling and communication afterward.
Candidates typically complete a home assignment focused on coding and design within a fixed time frame, which is seen as a critical part of the evaluation process, though some found the expectations unclear or the task overly demanding.
The technical interview rounds are structured and include coding exercises, system design discussions, and sometimes front-end tasks, with a focus on clear communication of thought processes and problem-solving approaches.
Experiences vary significantly regarding the atmosphere during technical interviews; while some candidates found it collaborative and friendly, others felt it was tense and unengaging, impacting their performance.
Candidates reported a high bar for performance, with a strong emphasis on correctness and clarity in coding, as well as the ability to articulate design decisions, which can lead to feelings of pressure during interviews.
Feedback after interviews is often perceived as lacking, with some candidates expressing frustration over generic rejections and a desire for more constructive closure regarding their performance.
