DevOps Engineer

Azure + AWS | Data & Integrations | Compliance | SRE Growth Track

Location: Noida (On-Site)

Employment Type: Full-Time (FTE)

About the Role

Crenovent is looking for an early-career Cloud DevOps & Platform Operations Engineer who wants to build a career across cloud engineering, DevOps, platform operations, data integration, security, compliance, and eventually Site Reliability Engineering (SRE).

We are not looking for an experienced DevOps specialist.

We are looking for someone with strong technical fundamentals, hands-on curiosity, structured problem-solving ability, and the capacity to learn quickly while working on real production systems across Microsoft Azure and AWS.

This is deliberately a broader role than traditional DevOps.

The engineer will work across four interconnected areas:

Cloud & DevOps → Data & Enterprise Integrations → Security/Compliance → Reliability Engineering

The person joining this role should therefore be comfortable learning across disciplines rather than restricting themselves to infrastructure deployment alone.

What You Will Work On1. Microsoft Azure & AWS

You will learn to deploy, configure, operate, and troubleshoot cloud infrastructure across both Azure and AWS.

Your work may include:

• Azure App Service
• Azure Functions
• Azure Storage
• Azure PostgreSQL and other managed databases
• Azure Key Vault
• Azure Monitor and Application Insights
• Microsoft Entra ID
• Azure Virtual Networks
• Azure Container Registry
• AWS EC2
• AWS RDS
• AWS S3
• AWS Lambda
• AWS IAM
• AWS VPC
• AWS CloudWatch
• AWS Secrets Manager
• Containerized workloads using Docker

You are not expected to know all of these on Day 1. Strong fundamentals and demonstrated ability to learn cloud technologies are more important.

2. DevOps & CI/CD

You will help engineering teams move code safely and consistently from development into deployed environments.

This will include:

• Git and GitHub
• GitHub Actions
• CI/CD pipelines
• Development, staging, UAT and production environments
• Environment configuration
• Deployment automation
• Infrastructure as Code
• Terraform fundamentals
• Docker
• Secrets and configuration management
• Release management
• Deployment verification
• Backup and recovery procedures
• Basic infrastructure troubleshooting

You will gradually learn how to make deployments repeatable, observable, secure and auditable, rather than relying on manual operations.

3. Data, Demo Environments & CRM Integrations

An important part of this role is understanding that infrastructure exists to support applications and data.

Crenovent works with enterprise systems and CRM data. You will therefore develop practical knowledge of how data enters, moves through and is maintained within an enterprise application.

You may work with platforms such as:

• Microsoft Dynamics 365
• Salesforce
• HubSpot
• Other CRM and enterprise applications
• APIs and webhooks
• CSV/Excel/JSON datasets
• SQL databases
• REST APIs
• Data import/export mechanisms

Typical assignments may include:

• Creating realistic synthetic/demo datasets
• Preparing demo CRM accounts, contacts, leads and opportunities
• Populating demonstration environments
• Importing and exporting CRM data
• Understanding CRM schemas and relationships
• Mapping fields between source and destination systems
• Moving data from CRM systems into Crenovent environments
• Validating data after migration or ingestion
• Identifying duplicate, malformed or missing records
• Supporting API-based integrations
• Understanding basic ETL/ELT concepts
• Creating repeatable processes for resetting or rebuilding demo environments

You should develop the ability to understand not only where an application is deployed, but also where its data comes from, where it goes, and how it can be validated.

4. Security, Compliance & Audit Readiness

This role will progressively develop into a combination of DevOps + Cloud Governance + Compliance Engineering.

You will learn how enterprise software companies demonstrate that their technology and operational processes are secure and controlled.

You may support activities related to:

• Access-control reviews
• User and privileged-access management
• IAM and RBAC
• Secrets management
• Environment separation
• Audit logging
• Infrastructure inventories
• Configuration documentation
• Security evidence collection
• Backup verification
• Vulnerability-management processes
• Patch-management tracking
• Change-management evidence
• Incident documentation
• Business continuity and disaster recovery
• Security policies and operating procedures
• Cloud security posture
• Compliance evidence repositories

Over time, you will develop familiarity with frameworks and concepts such as:

• SOC 2
• ISO 27001
• GDPR
• Data privacy and protection
• Security controls
• Risk registers
• Audit evidence
• Control testing
• Vendor/security assessments

You will not be expected to be a compliance specialist when you join. The expectation is that you can learn how technical systems, operational controls and compliance requirements connect.

5. Monitoring, Reliability & Future SRE Responsibilities

As your technical capability develops, the role will progressively move toward Site Reliability Engineering (SRE).

You will learn:

• Infrastructure monitoring
• Application monitoring
• Centralized logging
• Alerting
• Health checks
• Incident management
• Root Cause Analysis (RCA)
• Availability and uptime measurement
• Performance monitoring
• Capacity management
• Automated recovery
• Production readiness
• SLIs and SLOs
• Reliability engineering

The long-term objective is to develop an engineer who understands the complete operational lifecycle:

Build → Deploy → Secure → Observe → Audit → Operate → Recover → Improve

What We Expect You to Know

For this 0–1 year role, we are looking for fundamentals rather than mastery.

You should have basic knowledge of several of the following:

• Linux
• Cloud computing concepts
• Microsoft Azure and/or AWS
• Git/GitHub
• CI/CD concepts
• Docker
• Networking fundamentals
• DNS, HTTP/HTTPS and APIs
• SQL
• Databases
• JSON and CSV
• REST APIs
• Python or another scripting language
• Basic information-security concepts

Exposure through internships, personal projects, college projects, certifications, labs or self-learning is acceptable.

What We Do Not Expect

You do not need:

• 3–5 years of DevOps experience
• Expert-level Kubernetes knowledge
• Deep multi-cloud architecture experience
• Existing SOC 2 or ISO 27001 implementation experience
• Advanced SRE experience
• Expert knowledge of Salesforce or Dynamics 365
• Experience managing very large production infrastructure

Those are capabilities that can be developed progressively within the role.

What matters more is whether you understand the fundamentals and can systematically learn unfamiliar systems.

The Candidate We Are Looking For

A strong candidate for this role is someone who:

• Has strong computer-science and engineering fundamentals
• Has experimented with Azure, AWS or both
• Can work comfortably with Linux and command-line tools
• Understands basic databases and APIs
• Can write simple scripts to automate repetitive work
• Is interested in understanding how systems work end-to-end
• Can investigate technical problems rather than waiting for exact instructions
• Documents work systematically
• Pays attention to configuration, permissions and security
• Can work with checklists, evidence and operational procedures
• Is comfortable moving between infrastructure, application, data and security problems
• Wants to develop broad engineering depth early in their career

A Typical Problem You Might Solve

A Crenovent demonstration environment needs data from a CRM.

Instead of simply receiving a narrowly defined infrastructure task, you may need to:

Understand the CRM → identify the relevant entities and fields → prepare synthetic demo data → configure credentials securely → connect through an API → move the data → validate it in the destination → configure the application environment → deploy the relevant service → verify logs → troubleshoot failures → document the setup → ensure credentials are not exposed → preserve the evidence required for audit.

That end-to-end ownership is what makes this role different from a conventional entry-level DevOps position.

How This Role Can Evolve

This role provides multiple potential development paths.

DevOps / Platform Engineering

Cloud Infrastructure → CI/CD → Infrastructure as Code → Containers → Platform Engineering

Site Reliability Engineering

Monitoring → Incident Management → Observability → SLOs → Reliability Automation → SRE

Cloud Security & Compliance

IAM → Cloud Governance → Security Controls → Audit Readiness → SOC 2 / ISO 27001 → Cloud Compliance Engineering

Data & Integration Operations

CRM Data → APIs → Data Pipelines → Integration Operations → Enterprise Data Platforms

The likely long-term profile at Crenovent is a combination of:

DevOps + SRE + Cloud Governance + Compliance Engineering

with sufficient data and integration knowledge to operate enterprise environments effectively.

Qualifications

• B.Tech/B.E./BCA/MCA/B.Sc. Computer Science or equivalent technical background
• 0–1 year of professional experience
• Fresh graduates with strong hands-on projects are encouraged to apply
• Azure or AWS certifications are useful but not mandatory
• Relevant internships, GitHub projects, cloud labs or independently built systems will be considered positively

What We Will Evaluate

We are less interested in how many cloud-service names you can memorize and more interested in whether you can reason through technical systems.

The selection process may evaluate:

• Linux fundamentals
• Cloud fundamentals
• Azure/AWS concepts
• Networking basics
• Git
• CI/CD concepts
• Docker fundamentals
• SQL and databases
• APIs and JSON
• Basic scripting
• Troubleshooting approach
• Security awareness
• Ability to understand data movement
• Ability to learn an unfamiliar technical system
• Documentation discipline

Candidates may also be given a practical assignment involving a small cloud deployment, API/data integration or DevOps automation problem.