Backend & Cloud Infrastructure Team Lead (Node.js / AWS)
Free to start · No card · 5 credits the moment you sign up
Job description
Description
We are looking for Backend & Cloud Infrastructure Team Lead (Node.js / AWS). You'll lead the team that owns Questar's AWS cloud infrastructure and the backend microservices running on it. Hands-on leadership: roughly 60% people management, 40% staying close to architecture. You're accountable for how our microservices are designed, deployed, scaled and kept alive in production.
What You'll Do:
- Lead, mentor and grow a team of backend and infrastructure engineers: 1:1s, goals, performance reviews, career development
- Own the architecture of the AWS environment and the microservices platform on it, from design through rollout
- Break large initiatives into workstreams, delegate ownership, hold the team to delivery commitments without micromanaging
- Run agile ceremonies (sprint planning, retros, grooming) and align roadmap and priorities with product and other engineering leads
- Set and enforce engineering standards: code review, testing, observability, incident response, on-call rotation
- Drive cost, performance and reliability improvements across the platform
- Take part in hiring: interviewing, calibration, onboarding
Requirements
Must-Have:
- 8+ years of industry experience
- 5+ years as a people manager / team lead, leading engineering teams through full delivery cycles
- 3+ years of production backend development in TypeScript / Node.js (APIs, services, background processing, data flows). Frontend or frontend-leaning full-stack does not count
- Proven experience designing and leading AWS solutions at scale for distributed microservices — able to walk through a system you architected end to end and defend the trade-offs
- Deep hands-on knowledge of core AWS: ECS/EKS, Lambda, RDS, DynamoDB, SQS/SNS/EventBridge, API Gateway, VPC networking, IAM
- Containers and orchestration: Docker, Kubernetes or ECS
- Infrastructure as Code (Terraform, CDK or CloudFormation) and CI/CD pipeline ownership
- Production ownership: monitoring, alerting, on-call, post-incident reviews
- Strong grounding in agile, and the judgment to know when to bend it
- Excellent written and spoken English
Nice-to-Have:
- Kafka / event-driven architecture at scale
- Multi-region or multi-account AWS setups
- Database performance tuning at scale (Postgres, DynamoDB)
- Security and compliance exposure (SOC 2, ISO 27001)
Originally posted on Himalayas
Prepare your application
Use the description above to assess your fit for CommIT. This checklist is guidance from Resumize, rather than additional requirements from the employer. Imported listings can be shortened or change after collection, so confirm the complete description and current availability before sending an application.
Match requirements to evidence
Identify the responsibilities and skills the employer explicitly names. For each important requirement, choose one example from your work, education, training, or projects. Explain what you did, how you did it, and what changed as a result. Include a measurable outcome when you can support it. If you lack a requirement, describe related experience accurately instead of adding an unfamiliar skill to your resume.
Put the most relevant examples near the top of your resume. Keep job titles, dates, qualifications, and contact details consistent across your application materials. Use the employer’s terminology when it describes your experience accurately; a copied list of keywords does not explain your contribution. A short, specific bullet is easier to review than a paragraph that mixes several unrelated duties.
Check the working arrangement
Confirm the location, schedule, employment type, and any eligibility requirements on the employer’s site. A remote label does not establish worldwide eligibility or flexible hours. If compensation, benefits, equipment, travel, or contract duration are missing from this listing, write down your questions for the recruiter. Do not assume details from another opening at the same company apply to this role.
Review before submitting
Follow the employer’s requested file format and application instructions. Open your exported resume and check that its text is selectable, its sections read in order, and its links work. Proofread names, dates, and contact information. Share confidential work samples only when you have permission, and use an anonymized example when necessary.
Submit through a trusted employer or recruiting destination. If the original listing has disappeared, search the employer’s careers page for the title rather than assuming the vacancy remains open. Save the application date, job reference, and the version of your resume you sent. Those details help you prepare for a later conversation and avoid submitting conflicting information through several job boards.
Review your resume for writing and readability feedback, or browse other openings if this opportunity is unavailable.