Epassi interview questions

- Initial call the recruiter - Call with the head of engineering. - Tech call with a staff engineer to talk about system design and some questions about the framework like Spring etc. Firstly the recruiter is super unavailable. Disappears for days/weeks. You can keep following up throughout the process. Secondly made up feedback was given to me saying that I need more experience in Java (I am 16 years with Java btw) and Spring. They asked me 0 questions about Java. And a couple about Spring which I answered, even corrected the interviewer at some point. May be he took it personally and got insecure. I dont regret it :D They will never find good people if they keep running after people knowing a specific framework. Waste of time and energy. If you see this opportunity, just skip it.

Not a process I would recommend. The interviews were technically interesting, but the evaluation felt inconsistent and very very unfair. Different stages communicated different expectations, and the final rejection feedback did not match the actual system design discussion at all. The interviewer explicitly moved rapidly across multiple unrelated topics as part of the format, yet the final feedback later claimed that "edge cases, trade-offs, and scalability considerations had to be introduced by the interviewer". That was not an accurate reflection of the discussion, where I had proactively covered scalability, Kafka/outbox, retry/idempotency, transaction modeling, reconciliation, multi-tenancy, and partial failure handling. The process gave the impression of subjective calibration and retrofitted feedback rather than a clear, transparent senior engineering evaluation. Based on my experience, candidates should think very carefully before investing significant time in this process, as the time investment may not be treated with the same level of fairness and consistency.