DevOps Engineer

NewStreet is an award-winning fintech building AI-powered platforms that transform
how financial institutions operate. Established in 2017 and ISO 9001 & ISO 27001
certified, we serve 170,000+ customers across lending, trade finance and payments,
partnering with leading banks across India, the GCC and Southeast Asia.
*
Financial Times — 7th Fastest-Growing Fintech, Asia Pacific · Deloitte Technology Fast 50 · Aegis Graham Bell Award · World Fintech Awards 2025 · FICCI IBA Best Emerging Technology Platform*

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.

Key Responsibilities

• Own the pipeline. CI/CD end to end — build, test, scan, deploy, roll back. Make
• deployment boring and repeatable across every environment.
• Write the infrastructure. Terraform or equivalent IaC so environments are
• reproducible rather than remembered.
• Run the container platform. Docker and Kubernetes — images, registries,
• manifests, resource limits and rollout strategy.
• Make on-premise deployable. The same pipeline shape for client data centres
• as for AWS. This is where most deployment pain lives.
• Build observability in. Structured logging, metrics, tracing and alerting wired at
• build time, not retrofitted after an incident.
• Automate the toil. Turn repeated manual steps into pipeline stages or scripts so
• nobody does them by hand twice.
• Wire the security gates. SAST, dependency and secret scanning in CI, to the
• specification the Information Security function sets.
• Support the release. Environment provisioning, release mechanics and cutover
• support for client go-lives.

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.

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.

Tech Stack

• CI/CD: Jenkins, GitHub Actions, artefact registries, automated rollback
• Infrastructure as code: Terraform, Ansible, environment templating
• Containers: Docker, Kubernetes, Helm, image scanning
• Cloud: AWS (ECS / EKS, RDS, ElastiCache, S3, IAM, VPC), plus on-premise Linux
• estates
• Observability: Prometheus, Grafana, centralised logging, distributed tracing,
• alerting
• Security in pipeline: SAST, SCA, dependency and secret scanning, SBOM
• Languages: Python, shell; enough Python to read the application code you
• deploy

Apply: [email protected]