How hard are Persistent Systems Cloud Engineer interviews, and what is the offer rate reported by candidates?

Candidates reported that Persistent Systems interviews for the Cloud Engineer role are difficult, with the most common difficulty marked as difficult. Across 4 reported interviews, the offer rate was 25%. This suggests you should prepare for a strong emphasis on architecture and design depth.

What are the interview rounds for Persistent Systems Cloud Engineer, and how does the loop progress?

The process starts with an Initial Technical Screening to gauge foundational skills, then moves to Detailed Technical Interviews that cover both generic and role-specific topics. It concludes with Managerial or HR Rounds focused on fit and discussion. Plan to shift from broad capability early to detailed design and implementation choices in the middle stages.

What topics do Persistent Systems test most for a Cloud Engineer?

Persistent Systems most commonly tests Cloud Architecture, Migration Strategy from on-prem to cloud, scalability design, security measures and data protection, and cost optimization. Role-relevant scenarios also include legacy system migration like ERP, data analytics pipeline performance, and high-traffic web application scaling. Expect a mix of migration planning and system design under performance and cost constraints.

What does Persistent Systems expect from you in cloud architecture and migration questions?

You should be ready to design a high-level cloud architecture for migrating an on-premises data center and explain provider selection for a migration scenario. There are also prompt patterns around migrating a legacy ERP system to the cloud and outlining how to scale high-traffic web applications. Answers that connect architecture decisions to trade-offs like cost versus performance and security versus latency are explicitly aligned with preparation guidance.

What security and optimization areas come up in Persistent Systems Cloud Engineer interviews?

Security and optimization questions focus on data protection and compliance, plus how you would test and validate systems after migration. Cost optimization is also part of the expected coverage, including proposing a strategy for cloud resource utilization post-migration. Prepare to discuss both controls and operational validation steps, not only architecture.

What compensation should I expect for Persistent Systems Cloud Engineer, and does it vary?

The provided interview data includes an offer rate and interview details, but it does not include compensation figures for Persistent Systems Cloud Engineer. Because no base or total pay numbers are present in the supplied material, you cannot reliably infer a salary range from this dataset alone. If you have a level or location target, share it and I can help interpret it using only supported details.

Persistent SystemsCloud Engineer

Updated Apr 1, 2025

Persistent Systems Cloud Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Cloud Engineer at Persistent Systems, newest first and distilled into what to expect across the loop.

Get your personalized Persistent Systems Cloud Engineer prep plan

Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.

Build my free plan

Hot & recentNewest first

> 1 year

Difficult Negative Hyderābād

My experience soured fast. After a referral started moving things along, I ended up going through technical rounds with a cloud team, but the process felt chaotic mainly because of follow-ups and communication gaps. I had to keep chasing for feedback, and it dragged long enough that I ended up joining another company while waiting. Even after that, the recruiter part stalled—I kept trying to reach them for updates, but calls weren’t answered.

When an in-person round was eventually scheduled, the tone was the biggest shock. The interviewer’s demeanor felt unnecessarily dismissive and humiliating, and the whole interaction made it hard to stay confident, even when I was prepared. It wasn’t just tough questions; it felt like the process was conducted in a way that pushed candidates down rather than evaluating them fairly.

> 1 year

Average Positive Pune

I went in expecting a standard technical loop, but my process leaned heavily toward system-level thinking and cloud/distributed concepts. Early on, my first technical step was a focused screening where I answered questions about distributed systems and scalability—things like what distributed systems are, the Raft algorithm at a high level, and what makes one type of database better than another in distributed settings. I also got asked about concurrency topics like sharding.

From there, the questions broadened into practical engineering knowledge. I was asked why Go is used and how concurrency works in Go, including what reflection is in that ecosystem. I also had a short coding task where I needed to check if a string was a palindrome. On top of that, I was quizzed on Docker and Kubernetes concepts.

Share your interview experience

Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.