Cloud Success Architect Interview Experience - New Delhi, India
Process
Gave 3 rounds of interviews (1 hr each). All were cleared.
Got a call from HR. They asked about my current CTC, expected CTC, and if it was negotiable (I said 'No').
The next day, I received an email congratulating me on my selection. They asked for the "Name to be written on Offer Letter," PAN card, and my current organization's offer letter. I shared those details.
The day after that, I got a call from HR stating they could only offer a certain amount of CTC, which was not close to what I had asked for.
My only question was, why did you take my details such as offer letter and PAN card details and tell me "I am selected" when you were planning to negotiate? All those documents should be asked for after the negotiation is completed.
I asked the same question to HR. She said she would ask a senior HR to discuss with me.
Till date, there has been 'no call.' I sent a follow-up email. 'No reply.'
Advice for everyone: Don't share documents until you finalize the CTC and have an agreement.
Last words: Such a worst experience with the TA team was unexpected from such a reputed organization.
Questions
What are Docker and Kubernetes, and what are their architectures?
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the Red Hat Cloud Success Architect role in New Delhi, Delhi.
Success Rate
Red Hat's interview process for their Cloud Success Architect roles in New Delhi, Delhi is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very negative feelings for Red Hat's Cloud Success Architect interview process in New Delhi, Delhi.
Red Hat Work Experiences
- 4.0Good to go companySoftware Engineer • Current EmployeePuneMarch 31, 2025Pros: Good work culture with an open source modelCons: Not good for a long term perspective
- 1.0Blue wash is complete - Red Hat is not the SameSoftware Engineer • Current EmployeeRaleigh, NCAugust 5, 2026Pros: Talented colleagues who have a lot of experience in open source technologies. Healthcare benefits and PTO are good.Cons: Unsustainable Delivery Cadence: The department enforces a monthly release cycle for AI initiatives without providing adequate time, resources, or stability to meet these deadlines safely. Opaque Leadership and "Moving Goalposts": Strategic decisions and priority shifts routinely happen behind closed doors without communication to individual contributors. Goals or developmental projects assigned by management are frequently abandoned a month later, making it impossible to establish steady progress or achieve long-term impact. Punitive Culture and Lack of Accountability: When projects miss marks due to shifting directives, upstream dependencies failing, or lack of cross-functional handoffs, blame is systematically placed downward onto individual contributors rather than addressing the structural breakdown. Retributive Management Style: Communication from leadership often feels punitive rather than developmental. Vague expectations combined with rapid, unannounced shifts in direction create an environment where setting employees up to fail becomes a systemic pattern.
- 5.0Culture > PromotionSolution Architect • Current EmployeeCanberraJuly 5, 2024Pros: The best thing is the good culture.Cons: Getting promotions can be tricky. I have seen 2 promotion embargoes in 3 years.
