Cloud Application Developer II

Cloud Application Developer IIs build the services and systems that organizations depend on, on cloud infrastructure that they also help manage. They are full-stack in the cloud sense: they write application logic, define the infrastructure that application runs on, build the deployment pipeline that gets code to production, and maintain the observability that makes the service debuggable when something goes wrong.

The software engineering work is straightforward to describe: implementing features, fixing bugs, writing tests, reviewing code. What distinguishes a Developer II from more junior developers is judgment. When should this be a Lambda function and when should it be a long-running container? Does this data access pattern work at 10x current load? Is the API design clean enough that another team can integrate against it without confusion? What's the failure behavior of this service when the database is slow? These questions require both technical knowledge and experience — the experience to know which problems look simple but aren't, and which apparent complexities can be safely ignored.

Cloud infrastructure ownership is genuinely part of the job at this level. The services a Developer II owns come with cloud resources — a database, a message queue, an S3 bucket, IAM roles for the service accounts. The developer writes the Terraform or CDK that provisions those resources, defines the backup schedule, sets the retention policy, and configures the alerting. Treating cloud infrastructure as someone else's problem produces services that are expensive, insecurely configured, and painful to operate.

Mentoring is a new responsibility at this level. Developer IIs are the people code reviewing the work of Developer Is, catching problems that would otherwise reach production, and explaining the reasoning behind corrections rather than just making them. The quality of that feedback loop is a significant determinant of how fast the junior engineers on the team develop.

On-call rotation is typically where Developer IIs develop the operational intuition that makes them effective architects and senior engineers. Debugging a production incident under pressure — reading unfamiliar logs, tracing a failure through distributed systems, communicating status to stakeholders while fixing the problem — builds judgment that no design exercise can replicate.

Education:

• Bachelor's degree in computer science, software engineering, or a related field
• Many strong Cloud Application Developers are self-taught or bootcamp-trained; portfolios and demonstrated skills carry significant weight
• Graduate degrees in computer science are uncommon in cloud development roles; the premium is on practical engineering experience

Experience:

• 4–7 years of software development experience with at least 2–3 years working primarily in cloud environments
• Production ownership of at least one cloud-hosted service from design through ongoing operation
• Experience with at least one cloud provider's core services at a level beyond basic provisioning

Application development skills:

• Primary language depth: Python, Java, Go, Node.js/TypeScript, or C# at an intermediate-to-senior level
• RESTful API design: resource modeling, versioning, error response conventions, OpenAPI specification
• Testing: unit, integration, and contract testing; test pyramid application; mocking cloud services for local development
• Database design: SQL and at least one NoSQL option; query optimization; schema migration strategies
• Concurrency and asynchronous programming: async/await, event loops, message queue consumption

Cloud platform skills:

• Serverless: Lambda/Azure Functions/GCF — cold start, timeout, and concurrency trade-offs
• Container orchestration: Docker, Kubernetes basics, ECS/AKS/GKE deployment configuration
• Event/messaging: SQS/SNS/EventBridge, Kafka, Azure Service Bus — producer/consumer patterns, DLQ handling
• IaC: Terraform or AWS CDK — writing modules, managing state, environment promotion

DevOps practices:

• CI/CD: GitHub Actions, Jenkins, GitLab CI — pipeline design for multi-stage deployments
• Observability: OpenTelemetry instrumentation, CloudWatch/Azure Monitor/GCP Monitoring dashboards
• Release patterns: feature flags, canary deployment, blue/green — when each is appropriate

Cloud Application Developer II is one of the most actively hired levels in software engineering. Organizations with cloud-native development ambitions need senior-enough developers to work independently and mentor junior team members, but the supply of engineers who combine application development depth with genuine cloud infrastructure fluency remains tight.

The BLS projects 25% growth in software developer roles through 2032, and cloud-native development skills are disproportionately represented in that projection. Companies building greenfield applications on cloud platforms, enterprises migrating legacy applications to cloud-native architectures, and technology companies expanding their product capabilities all need Developer IIs who can own services end-to-end.

AI integration is creating new demand specifically. The majority of software teams are now building AI-augmented features — calling LLM APIs, building recommendation systems, implementing semantic search, or automating workflows that previously required human judgment. Developer IIs who understand how to build reliable, observable, and cost-efficient AI-integrated systems are in shorter supply than general cloud developers and command corresponding premiums.

The cloud platform landscape is stable enough that deep specialization in AWS, Azure, or GCP produces durable value. AWS maintains its market share lead, making AWS-specialist developers the most broadly in-demand. Azure specialization is highly valued at Microsoft-ecosystem enterprises. Multi-cloud fluency is increasingly valued but typically develops after establishing depth in one platform.

Career progression from Developer II moves toward Senior Developer (III or equivalent), Staff Engineer, or Principal Engineer for those who want to stay technical. Architecture-focused developers progress toward Application Architect or Solutions Architect. Engineering management is a distinct branch for those who want to lead teams rather than own technical systems. Each path offers meaningful compensation growth, with Staff and Principal Engineer tracks at large tech companies reaching $200K–$300K+ in total compensation.

Dear Hiring Manager,

I'm applying for the Cloud Application Developer II position at [Company]. I've been building cloud-native services at [Company] for four years, the last two as a mid-level developer owning three microservices in our payments platform — a Python/FastAPI application deployed on ECS with Aurora PostgreSQL.

The service I'm most often asked about is our payment reconciliation service. When I inherited it, it had no structured logging, a test coverage rate below 40%, and a production incident every two weeks caused by a race condition in the reconciliation logic that nobody had fully understood. I rewrote the critical path — replacing the database-level locking with an idempotency key pattern using DynamoDB — and brought test coverage above 85% over two sprints. We've had zero reconciliation incidents in the 14 months since. The service now handles about 200K transactions per day.

I write the Terraform for all infrastructure my services own — RDS parameter groups, SQS queues and DLQs, IAM execution roles, CloudWatch alarms. I don't consider it someone else's job. I also built out our OpenTelemetry instrumentation for the payments domain last year, which gave us distributed traces that now make debugging cross-service issues dramatically faster than reading individual CloudWatch logs.

I'm looking for a role with more architectural responsibility — specifically the opportunity to be involved in service design decisions earlier in the process, and to work in an environment building AI-augmented features. The AI integration work in your job description is exactly the kind of problem I want to develop experience with.

I'd welcome the chance to talk.

[Your Name]