What are the responsibilities and job description for the CIA - Cloud Architecture (Cloud Connectivity) position at ADDSOURCE?
Role: CIA - Cloud Architecture (Cloud Connectivity) - (Senior)
Location: US (remote)
Duration: 12 Months
Key Responsibilities
- Build and manage secure network architecture for 1,000s of AWS networks
- Build hybrid cloud networks linking local data centers to AWS regions
- Monitor network performance and fix latency or connectivity issues
- Automate network deployments using CDK Typescript
- Hands on experience implementing cross vpc and hybrid connectivity using AWS PrivateLink and Amazon VPC lattice service networks
Must Have
- AWS Network SME (Level 300-400).
- Transit Gateway
- CloudWAN
- VPC
- Network Monitoring
- Firewalls
- Proxy Solutions (explicit and transparent).
Should Have
- AWS CDK TypeScript (Level 300) - Ability to design CDK construct architectures, review constructs for best practices, and guide teams on CDK patterns for multi-account, multi-environment deployments.
- AWS Services (Level 300) - ECS Fargate, ELB, EC2, S3, IAM, VPC, VPC Lattice, SQS, RDS, DynamoDB, Aurora PostgreSQL, Lambda, API Gateway, KMS.
- ECS Fargate (Level 300) - Deep expertise in task definitions, service architecture, load balancer integration, auto-scaling, service discovery, and migration from VM/PCF to Fargate. This is a strategic compute platform.
- Multi-Region Architecture (Level 400) - Design of active-active (2-region) and active-passive particularly for multi-region events and RDS Aurora databases.
- Documentation (Level 400) - Must be able to clearly write, draw, and organize architectural decision records (ADRs), target-state architecture diagrams, blueprint documentation, and guidance for application teams on a weekly basis.
- Agile/Jira (Level 200) - On-daily basis you must be able to manage and report own Jira User Stories during the current sprint.
Nice to Have
- VPC Lattice (Level 200) - Understanding service-to-service connectivity patterns using VPC Lattice particularly service networks, resource configs, and producer/consumer concepts.