About the role
Our clients are moving critical workloads to the cloud and need an architect who can make the hard decisions early: account structure, network design, identity, data residency, and how teams will actually ship on top of it.
You will be the senior technical voice on engagements, partnering with platform engineers, security and finance. You'll set direction, write the reference architecture, and stay close enough to the code to know it works.
Your team
You'll join a small cloud and platform group of senior engineers and architects, working across several client engagements with a shared playbook.
The impact you'll have
Foundations that last
Landing zones and guardrails that let teams move fast without creating audit debt.
Migrations without drama
Phased, reversible plans with clear cutover criteria and rollback paths.
Cost you can explain
Architecture and tagging that make spend visible and defensible.
What you'll do
- Lead architecture for multi-account cloud environments and migrations
- Define IaC, networking, identity and governance standards
- Run design reviews and mentor engineers on client teams
- Partner with security and FinOps on risk and cost guardrails
A typical week might include
- Morning design review with a client platform team
- Pairing on a Terraform module and its guardrails
- Writing an ADR for a networking decision
- Cost and reliability check-in with delivery lead
Technical scope and expected depth
The areas this role may cover. The exact environment and priorities are agreed for each engagement.
Cloud foundations and governance
Design account or subscription structures, environment separation, policy boundaries, resource organization, tagging, and platform ownership. Explain where a shared service improves consistency and where a product team needs autonomy.
Identity, networking, and security
Review federation, workload identities, privileged access, private connectivity, routing, DNS, segmentation, encryption, and secret management. Work with security partners to turn requirements into implementable architecture and documented exceptions.
Infrastructure and developer platforms
Evaluate infrastructure as code, reusable modules, build pipelines, artifact management, environment provisioning, and self-service workflows. Define how platform changes are tested, versioned, documented, and consumed by application teams.
Reliability and recovery
Connect business criticality to availability targets, recovery objectives, backup strategy, dependency failure, and incident response. Require evidence from recovery exercises and operational telemetry before calling a design resilient.
Migration and application modernization
Assess application dependencies and choose an appropriate path for each workload: retain, retire, rehost, replatform, or refactor. Define validation, rollback, cutover ownership, data movement, and retirement criteria for each migration wave.
Cost and capacity management
Establish allocation, budgets, forecasting, utilization review, and unit-cost discussions. Evaluate elasticity, commitments, storage lifecycle, and architecture choices against business demand; communicate the reliability and flexibility tradeoffs behind savings.
What you'll deliver
Architecture narrative
A leadership-ready story that connects platform choices to business outcomes, risk, sequencing, and investment.
Decision register
Explicit decisions, options, constraints, owners, and reversibility so the program can move without rediscovering the debate.
Transition roadmap
Migration waves, modernization choices, dependencies, cutover approach, and decommissioning plan.
Platform operating model
Ownership, standards, service boundaries, developer experience, reliability, security, and cost rhythms.
What you bring
- 8+ years in infrastructure or cloud engineering, 4+ in architecture
- Deep AWS or Azure expertise with a professional-level certification or equivalent
- Strong Terraform, Kubernetes and CI/CD experience
- Clear written and verbal communication with executives and engineers
Practical capabilities we will discuss
- Cloud provider depth
- Demonstrate detailed design experience with AWS, Microsoft Azure, or Google Cloud. Explain the identity, network, compute, storage, and governance services you selected, the alternatives you considered, and the operational consequences of that choice.
- Infrastructure delivery
- Be comfortable reviewing Terraform, CloudFormation, Bicep, or equivalent infrastructure definitions. Recognize module boundaries, state management, environment promotion, drift, permissions, and rollback concerns even when another team owns the implementation.
- Containers and runtime choices
- Evaluate when containers, managed application services, serverless execution, or virtual machines fit a workload. Discuss orchestration, scaling, runtime security, support burden, and the skills required to operate the chosen approach.
- Architecture evidence
- Bring an example of a significant architecture decision you led. Walk through the business constraint, discovery process, options, cost assumptions, risks, implementation sequence, and what changed after the recommendation was adopted.
Nice to have
- Multi-cloud or regulated-industry experience
- FinOps practice
- Public speaking or writing
How success is assessed
Success criteria are agreed at the start of the engagement and reviewed as the work progresses. Typical signals include:
- Leaders can explain the target state and why the sequence is responsible.
- Engineering teams adopt reusable platform patterns instead of recreating infrastructure.
- Migration and modernization decisions reduce risk without creating an unmanageable parallel estate.
- Cloud cost and reliability signals are visible to the teams that can change them.
- The client can continue architecture governance and platform improvement after handoff.
Your first 90 days
First 30 days
- Join an active engagement and learn the client's estate
- Review existing architecture decisions and open risks
- Meet security, finance and delivery counterparts
By day 60
- Own a design workstream end-to-end
- Publish or update a reference architecture
- Lead your first client design review
By day 90
- Run architecture for a full engagement phase
- Mentor two engineers
- Contribute a reusable module or pattern to our internal library
How we work with clients
- Prepare workshops with a clear decision, relevant evidence, and the people needed to act on the outcome.
- Document assumptions, alternatives, costs, dependencies, and risks so stakeholders can review your recommendation.
- Escalate delivery or quality concerns early with options and a recommended course of action.
- Protect confidential information and use approved collaboration and delivery environments.
- Transfer knowledge through pairing, practical documentation, and walkthroughs with the people taking ownership.
Tools you may use
- AWS
- Azure
- Terraform
- Kubernetes
- ArgoCD
- GitHub Actions
- OpenTelemetry
- Datadog
- Vault
Interview process
- 01
Apply
Share your background. A human reads every application.
- 02
Intro call
30 minutes on your goals, experience and what you want next.
- 03
Technical conversation
A practical discussion with a practitioner — no trick puzzles.
- Architecture deep-dive. Walk through a cloud design you led and the trade-offs you made.
- Design exercise. Collaboratively sketch a landing zone for a regulated workload.
- 04
Team & terms
Meet the people you'd work with, then agree scope and terms in writing.
Location, engagement and compensation
This is an expression-of-interest profile for client work we are shaping. A confirmed vacancy, employment arrangement, travel requirements and compensation range have not yet been published. Before an approved role proceeds, we agree client context, availability, duration, compensation or rate and any benefits in writing.
Telugu Technologies is an equal opportunity employer. We consider all qualified applicants regardless of race, color, religion, sex, sexual orientation, gender identity, national origin, age, disability or veteran status, and provide reasonable accommodations on request — email careers@telugutechnologies.com.