Skip to content

Persistent Systems Interview Experiences

These Persistent Systems interview notes are rewritten from public student posts and prep-site summaries. Your panel can still look different.

Usual flow: Online assessment (aptitude + CS fundamentals + coding) → Technical interviews → Communication / SVAR (Amcat reported in Martian path) → HR

Martian internship-to-PPO pathway with staged training assessments is a distinctive campus pattern reported for Persistent.

DSA, OOP, core CS, projects. Martian path: tech interview after final assessment, then speaking/listening (SVAR) on Amcat before HR.

Hobbies, interest in CS, knowledge of Persistent, relocation readiness (Martian GFG account).

Cleared OA (aptitude/logical/CS + 2 coding) → 6-week internship training with weekly MCQs → final assessment (MCQ + 2 coding in chosen Java/Python track) → tech interview → SVAR communication test → HR (hobbies, company knowledge, relocate). Offer mail next day; offer letter about a month later.

These notes come from public reports and can differ by campus, year, and role. If your college placement email or the official careers/notification PDF says something different, follow that.

After technical rounds, Persistent Systems usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.

Hexaware · Coforge · Thoughtworks · Mphasis · LTTS