Cvent is Hiring Intern - Cloud Operations | Gurugram | 2027 Batch Students

Job Description

𝐈𝐦𝐩𝐨𝐫𝐭𝐚𝐧𝐭 𝐟𝐥𝐚𝐠 𝐛𝐞𝐟𝐨𝐫𝐞 𝐭𝐡𝐞 𝐰𝐫𝐢𝐭𝐞-𝐮𝐩: This posting explicitly states eligibility for "𝟐𝟎𝟐𝟕 𝐛𝐚𝐭𝐜𝐡 𝐬𝐭𝐮𝐝𝐞𝐧𝐭" — meaning this is likely a pre-placement or advance internship pipeline for students graduating in 2027, not current final-year students or recent graduates. If you're not part of the 2027 graduating batch specifically, this listing's stated eligibility suggests you may not qualify. Also worth noting: the posting appears to combine two distinct internship tracks — "Intern, Cloud Infra" and "Intern, Database Engineer" — under one listing, similar to a couple of other merged-role postings covered on this site; worth clarifying with the recruiter which track you'd actually be considered for.

Cvent's Cloud Operations internship is worth understanding as effectively two different specializations bundled into one posting. The 𝐂𝐥𝐨𝐮𝐝 𝐈𝐧𝐟𝐫𝐚 track focuses on AWS infrastructure automation and operations — supporting services like EC2, S3, CloudWatch, and IAM, writing scripts to reduce manual work, and helping investigate infrastructure issues under senior guidance. The 𝐃𝐚𝐭𝐚𝐛𝐚𝐬𝐞 𝐄𝐧𝐠𝐢𝐧𝐞𝐞𝐫 track is a genuinely different function — designing database objects, writing complex SQL, troubleshooting database performance issues, and supporting application developers with data management. These require meaningfully different skill emphases (infrastructure/DevOps versus database engineering), so it's worth clarifying which track you'd actually be placed into before assuming you know what the role involves.

Cvent itself is a well-established event and hospitality technology company serving a notably large client base (60% of the Fortune 500), giving this internship exposure to infrastructure supporting a genuinely large-scale, high-traffic platform. Worth flagging distinctly: Cvent's posting has an unusually explicit and repeated emphasis on 𝐀𝐈-𝐚𝐮𝐠𝐦𝐞𝐧𝐭𝐞𝐝 𝐰𝐨𝐫𝐤 as part of company culture — the listing states AI is "part of our DNA" and explicitly mentions the interview process will assess how candidates "use AI to learn, iterate, and amplify your impact." This is a genuinely direct signal that demonstrating thoughtful AI tool usage (not just familiarity, but examples of it improving your actual work) will matter in interviews here, more explicitly than in most other listings covered.

𝐎𝐮𝐫 𝐓𝐚𝐤𝐞:

- 𝐆𝐨𝐨𝐝 𝐟𝐨𝐫: 2027-batch B.Tech (CS/IT preferred) students from Tier I or II engineering colleges interested in either 𝐜𝐥𝐨𝐮𝐝 𝐢𝐧𝐟𝐫𝐚𝐬𝐭𝐫𝐮𝐜𝐭𝐮𝐫𝐞/𝐃𝐞𝐯𝐎𝐩𝐬 or 𝐝𝐚𝐭𝐚𝐛𝐚𝐬𝐞 𝐞𝐧𝐠𝐢𝐧𝐞𝐞𝐫𝐢𝐧𝐠, comfortable discussing genuine AI tool usage in their work.

- 𝐍𝐨𝐭 𝐢𝐝𝐞𝐚𝐥 𝐟𝐨𝐫: students outside the 2027 graduating batch, or those uninterested in infrastructure/database-focused work specifically (as opposed to application development).

- 𝐒𝐞𝐥𝐞𝐜𝐭𝐢𝐨𝐧 𝐝𝐢𝐟𝐟𝐢𝐜𝐮𝐥𝐭𝐲: 𝐌𝐨𝐝𝐞𝐫𝐚𝐭𝐞 — the Tier I/II college specification and 2027-batch-only eligibility narrow the pool, and the explicit AI-fluency expectation in interviews adds a distinctive evaluation dimension worth preparing for specifically.

- 𝐂𝐚𝐫𝐞𝐞𝐫 𝐭𝐫𝐚𝐣𝐞𝐜𝐭𝐨𝐫𝐲: Cloud Infra track could lead into 𝐂𝐥𝐨𝐮𝐝 𝐄𝐧𝐠𝐢𝐧𝐞𝐞𝐫, DevOps Engineer, or Site Reliability Engineer roles; Database Engineer track could lead into 𝐃𝐚𝐭𝐚𝐛𝐚𝐬𝐞 𝐀𝐝𝐦𝐢𝐧𝐢𝐬𝐭𝐫𝐚𝐭𝐨𝐫, Data Engineer, or Backend Developer roles — genuinely different paths depending on eventual placement.

𝐂𝐨𝐦𝐩𝐞𝐧𝐬𝐚𝐭𝐢𝐨𝐧 𝐂𝐨𝐧𝐭𝐞𝐱𝐭: Cvent hasn't disclosed a stipend for this role. Cloud/Database internships at established SaaS companies in Gurugram typically range around ₹20,000–₹35,000/month for pre-final-year student internships, based on general market data for comparable early-pipeline internships — this is an estimate only, and given this appears to be an advance/pipeline program for 2027 graduates, terms may differ from a standard final-year internship.

𝐀𝐩𝐩𝐥𝐢𝐜𝐚𝐭𝐢𝐨𝐧 𝐒𝐭𝐫𝐚𝐭𝐞𝐠𝐲: Given Cvent's explicit and repeated emphasis on AI-augmented work throughout the posting, prepare specific examples of how you've used 𝐀𝐈 𝐭𝐨𝐨𝐥𝐬 in your own projects or coursework — not generic familiarity, but concrete instances where AI tools helped you learn something faster or solve a problem more effectively, since the posting directly states this will be assessed during interviews; separately, clarify early which track (Cloud Infra vs. Database Engineer) you're being considered for, since your preparation should differ meaningfully between the two.

Roles & Responsibilities

Two distinct tracks are described in this posting — worth treating as separate role possibilities rather than one combined job.

Cloud Infra track:

- Develop and maintain tools for infrastructure deployment automation across on-premises and AWS

- Support core AWS services (EC2, EBS, CloudFront, S3, ECS, CloudWatch, Config, IAM) under guidance

- Contribute to AWS cost/usage reporting, tagging compliance, and infrastructure dashboards

- Write scripts (Python, Bash, PowerShell, Groovy) to reduce repetitive operational work

- Investigate low-complexity infrastructure issues, escalating clearly when needed

Database Engineer track:

- Design and develop database objects (tables, indexes, keys, stored procedures, views, functions, triggers)

- Automate workflows to reduce mundane database tasks

- Troubleshoot and resolve database bugs and performance issues

- Write complex SQL code and support query tuning

- Gather user requirements and implement new database features

Qualifications & Eligibility

A notably specific eligibility filter — worth confirming you meet this before applying.

- 2027 batch student

- Pursuing B.Tech, preferably in Computer Science or IT

- From a Tier I or II Engineering college

Skills Required

Skills vary significantly by track — Cloud Infra emphasizes AWS and scripting; Database Engineer emphasizes SQL and relational/NoSQL database concepts.

- Cloud Infra: AWS services knowledge, infrastructure-as-code (CloudFormation), scripting languages

- Database Engineer: Relational and NoSQL database understanding, complex SQL, hands-on AWS database services

- Both tracks: Genuine interest in demonstrating AI tool usage during the interview process