Engineering · Platform & DevOps

DevOps Engineer

CI/CD end to end — build, test, scan, deploy, roll back. Make deployment boring and repeatable across every environment.

Experience

3–5 years

Location

Bengaluru

Level

Experienced

01

About the Role

Our platform ships to banks and financial institutions across AWS and client on-premise estates, and every one of them has its own change window, its own approval chain and its own idea of what a deployment looks like. This role owns the pipeline that makes all of that repeatable.

You sit in the platform and DevOps cell with our existing infrastructure engineer, reporting to the Head of Engineering — who owns the DevOps practice and standards. This is deliberately separate from production support, which is run by the IT & Production Support function. You build and automate; they run and respond.

02

Key Responsibilities

1

Own the pipeline

CI/CD end to end — build, test, scan, deploy, roll back. Make deployment boring and repeatable across every environment.

2

Write the infrastructure

Terraform or equivalent IaC so environments are reproducible rather than remembered.

3

Run the container platform

Docker and Kubernetes — images, registries, manifests, resource limits and rollout strategy.

4

Make on-premise deployable

The same pipeline shape for client data centres as for AWS. This is where most deployment pain lives.

5

Build observability in

Structured logging, metrics, tracing and alerting wired at build time, not retrofitted after an incident.

6

Automate the toil

Turn repeated manual steps into pipeline stages or scripts so nobody does them by hand twice.

7

Wire the security gates

SAST, dependency and secret scanning in CI, to the specification the Information Security function sets.

8

Support the release

Environment provisioning, release mechanics and cutover support for client go-lives.

03

What You Bring

  • 3–5 years in a DevOps or platform engineering role on a product with real users.
  • CI/CD ownership — Jenkins, GitHub Actions or equivalent. You have built a pipeline, not just edited one.
  • Infrastructure as code in production — Terraform preferred, Ansible or CloudFormation acceptable.
  • Docker and Kubernetes hands-on: you can debug a failing pod without guessing.
  • AWS working knowledge — ECS or EKS, RDS, S3, IAM, VPC basics.
  • Linux administration and scripting in Python or shell.
  • Git branching strategy, artefact management and release versioning.
  • You think about failure modes and rollback before you think about the happy path.
04

What Would Be Great to Have

  • On-premise or air-gapped deployment at a client site.
  • Monitoring and alerting built from scratch — Prometheus, Grafana, centralised logging.
  • Secrets management (Vault or AWS Secrets Manager) and pipeline security tooling.
  • PostgreSQL operations — migrations, backup and restore.
  • Cost optimisation on AWS with evidence of what was saved.
  • Banking or financial-services deployment environments, including change-freeze discipline.

Sound like you?

Send your CV to careers@newstreettech.com. The subject line is filled in with the role code (NS-DVO-001) for you.