Satispay Software Backend Developer interview questions

The process was smooth and professionally handled. I had a call with someone from the Talent team — well-paced, respectful, and with a friendly tone throughout. One thing I genuinely appreciated was receiving written feedback. That alone sets Satispay apart from many other companies. The feedback was constructive and clearly meant to be helpful — and I respect that. However, I couldn't help but notice a subtle undertone in the message: I was advised to use the STAR method to improve the structure of my answers, even for broad questions like “Tell me about yourself”. I was also told that “structured communication” is something they value highly. Reading between the lines, the implication was that my communication style came across as overly talkative or unfocused. I respectfully reject that interpretation. I deliberately avoided listing certifications and buzzwords at the start — not out of lack of experience, but to keep the conversation authentic and avoid sounding arrogant. Ironically, this choice may have been misread. Nothing deeply negative here — just a caution for future candidates: if your natural communication style is narrative, reflective, or context-driven, be prepared to adapt to a more formulaic approach. And if you choose to keep things real, be aware it may be (mis)interpreted differently than intended.

- Primo step conoscitivo con HR - Secondo step di colloquio tecnico online, problema leetcode easy - Successivo iter di 3 colloqui in presenza a Milano (treno pagato) - Primo colloquio tecnico in presenza, sempre leetcode easy, con due engineer - Secondo colloquio tecnico con altri due engineers, non codice ma domande, basate sui "pillar aziendali" - Terzo colloquio con Engineering Manager + Lead Software Engineer piu incentrato sulla cultura ma sempre sui "pillar aziendali"