Skip to content
Cleo (India)

Principal Software Engineer

Bangalore; Bangalore, India - OfficeIndia
Principal · Engineering
POSTED 6 OCTVERIFIED 1D AGO
Apply Ask
Role
34 days opentrue age
Posted 6 Oct
Pay
₹84.3L–₹98.5Lno pay posted
Market p25–p75
₹84.3L–₹98.5L
Bengaluru · n=3 · 365d to 4 Nov
CompanyCleo (India) →
15open roles
Opened · 30d
+0
Closed · 30d
−0
2d of snapshots · 30d window
Market
2,604open · Principal Software engineering
Opened · 7d
+1335% of open
All software engineering
74,905open
All tracked boards · live 9 Nov · n=2,604
PythonGoAWSDocker

Principal Software Engineer (DevOps)

Department: Engineering

Level: IC – Senior

Location: Bangalore

Type: Full-Time

Reports To: Senior Engineering Manager

About Cleo

Cleo is the AI-native supply chain orchestration company built on modern EDI. We help businesses orchestrate EDI, API, MFT, applications, and trading partner ecosystems with the visibility, intelligence, and control needed to keep business-critical supply chain transactions moving — from order to cash, procure to pay, and everywhere in between.

Our platform, Cleo Integration Cloud, brings together integration, workflow automation, real-time monitoring, and Agentic AI intelligence so supply chain, operations, and IT teams can launch partners faster, automate transactions across business systems, resolve exceptions before they become disruptions, and gain actionable insight across the end-to-end supply chain.

Trusted by 5,000+ customers across manufacturing, retail, logistics, and distribution, Cleo is headquartered in Rockford, Illinois, with offices in Chicago and Bangalore. We are a team united by one mission: to make supply chains smarter. Cleo Never Stops.

About the Role

We are looking for a Principal Software Engineer to shape how our AWS-based SaaS products are built, deployed, and operated. This is a hands-on technical leadership role for an engineer with prior software development experience and deep expertise in AWS, infrastructure as code, CI/CD, automation, and observability.

You will partner with application, platform, product, and security teams to improve the full software delivery lifecycle. You will modernize existing applications by reducing unnecessary coupling and enabling components to be built, tested, released, and deployed independently where the architecture supports it. You will also set technical direction across teams, lead complex modernization initiatives, and mentor engineers in the Bangalore organization.

What You Will Do

DevOps Strategy and Technical Leadership

  • Define DevOps and platform engineering standards, reference architectures, delivery patterns, and operational practices.
  • Lead cross-team initiatives that improve delivery speed, reliability, security, and maintainability.
  • Make and communicate technical decisions that balance modernization, customer impact, and service continuity.
  • Mentor engineers, lead knowledge-sharing sessions, and contribute to hiring and technical interviews.

Application Modernization and Software Engineering

  • Apply software development experience to understand application architecture, dependencies, build systems, runtime behavior, and operational risks.
  • Assess existing applications and reduce tight coupling between components, services, shared libraries, and deployment units where practical.
  • Enable components to be built, tested, versioned, and deployed independently
  • Improve configuration, secrets handling, health checks, logging, metrics, and graceful startup and shutdown behavior.
  • Build automation and engineering tools using a programming or scripting language such as Python, Go, Groovy, or shell.

CI/CD and Developer Experience

  • Design, implement, and operate CI/CD platforms using GitHub Actions and Jenkins.
  • Build and maintain reusable workflows, pipeline templates, and shared components using pipeline-as-code.
  • Create reliable workflows for builds, automated tests, code quality checks, container creation, artifact management, deployment, and environment promotion.
  • Integrate appropriate security and quality checks, including dependency and container scanning and secrets detection.
  • Manage workflow permissions and credentials using least privilege and short-lived credentials or federated identity where supported.
  • Improve build and deployment reliability through caching, parallel execution, consistent toolchains, and clear failure diagnostics.
  • Modernize existing Jenkins pipelines and integrate them with GitHub repositories and Actions where appropriate.
  • Improve developer experience with self-service workflows, standard templates, documentation, and actionable pipeline feedback.
Source · Cleo (India) First seen 4 NovOriginal ↗