Role Purpose

The Senior Engineer is responsible for
delivering end‑to‑end software engineering outcomes, including cloud
infrastructure, application development, CI/CD, and operational support,
within a DevOps and product‑centric delivery model. The role shifts away
from task‑based development toward full ownership of solutions in a modern
cloud environment.

Key Responsibilities

End‑to‑End Engineering

- Design,
build, deploy, and support cloud‑native applications across AWS and
Azure.

- Develop
and manage Infrastructure as Code (IaC) using Terraform.

- Build
and maintain application services using microservices and API‑first
architecture.

- Participate
in DevOps culture: engineers who build the solution also support it
in production.


Software Development

- Develop
backend services using modern .NET.

- Build
frontend components using ReactJS.

- Implement
cloud‑native services using AWS Lambda and/or Azure Functions.

- Apply
agreed design patterns, security standards, and architectural
principles.

- Write,
review, and maintain clean, secure, and scalable code.


CI/CD & Release

- Use
and operate GitLab CI/CD pipelines.

- Apply advanced Git workflows.

- Support
automated build, test, and deployment processes.

- Ensure




solutions are deployable across multi‑cloud environments.


Testing & Quality

- Implement unit, integration, and end‑to‑end testing.

- Use
testing frameworks such as xUnit, NUnit, Jest, Cypress.

- Integrate
testing into CI/CD pipelines.


Operations & Support

- Monitor
applications and infrastructure logs.

- Support
incident resolution and minor security vulnerabilities.

- Follow
cost, performance, and operational guidelines.

- Understand
service management tooling (e.g. ServiceNow).


Required Skills & Experience

- Strong
experience in cloud platforms (AWS and/or Azure).

- Proven
capability in Terraform and Infrastructure as Code.

- Solid
backend engineering skills in .NET.

- Solid
frontend skills in ReactJS.

- Hands‑on
experience with CI/CD pipelines and Git workflows.

- Understanding
of API‑first development, microservices, and security basics.

- Ability
to work independently with minimal reliance on client FTEs.


Key Expectations

- Must
be able to deliver end‑to‑end solutions without dependency on client
engineers.

- Must
demonstrate practical cloud engineering capability, not just conceptual
knowledge.

- Acts
as a technical contributor, not a people manager.