Cloud Developer

We’re looking for an Intermediate Cloud Developer to join our POSSE Cloud 3 (aka PC3) team.

PC3 is the cloud platform behind solutions our clients depend on. The team works across Azure infrastructure, Kubernetes, infrastructure as code, deployment automation, networking, monitoring, security and operational reliability.

This is a hands-on role for someone who already has solid infrastructure fundamentals and wants to keep growing as a Cloud Developer.

You won’t be expected to know everything on day one. We do expect you to be curious, take ownership of your work, investigate problems carefully, ask for help when you need it, and leave things better than you found them.

What you’ll be working on:

• Build and maintain cloud infrastructure. PC3 takes a code-first approach to infrastructure. You'll work with technologies such as Microsoft Azure, Terraform, Kubernetes/AKS, Helm, containers, Git and CI/CD pipelines.

• Modernize the foundation. PC3 isn’t new, and we don’t expect the platform to stand still. There’s plenty to improve, from cloud security vendor integrations, new feature integration, keeping our technology current, reducing noise in monitoring, and making the platform easier to operate.

• Participate and contribute as we continue to navigate the changes AI presents to our development and work

• Keep production systems reliable. You'll investigate alerts and incidents, troubleshoot infrastructure problems, participate in upgrades and maintenance, and help improve monitoring and operational practices.

• Treat internal integration teams as customers of the platform. They're the people developing, deploying and supporting client solutions on our cloud platform PC3. Their experience matters. When something is confusing, slow or difficult to troubleshoot, look for ways to improve the platform rather than simply teaching people to live with it.

• Write and expect clarity in documentation, knowledge transfer, process, and standards. Good documentation shouldn't depend on knowing the person who built the system. Produce documentation that provides clear and valuable information to the variety of audiences it serves.

• Automate work that shouldn't need to be manual. Repeated provisioning, deployment, validation and maintenance tasks are opportunities for improvement. If people keep doing the same thing by hand, it's reasonable to ask, “Why are we still doing this manually?”

• Fix problems, not just tickets. Slow and flaky bothers you. So does solving the same problem repeatedly. Fix the immediate issue, but also look to address the entire class of problem.

• Get useful work in front of people. Not every solution needs to emerge fully formed. Sometimes the right approach is to build something useful, get feedback from the people using it, and improve it from there.

• Work within real-world constraints. Time and budget matter, as do reliability, security and maintainability. Good engineering means understanding those constraints and making sensible trade-offs. The goal isn't technical perfection. It's the best solution we can responsibly deliver with the resources available.

What we’re looking for:

We're more interested in what you can do and how you approach problems than whether your résumé contains every technology we use. You probably have experience with several of these:

• supporting or engineering production infrastructure;

• Microsoft Azure or another major public cloud;

• infrastructure as code;

• networking, DNS, identity, compute and storage;

• Git and source-controlled change;

• containers and Kubernetes;

• CI/CD and deployment automation;

• PowerShell, Python, Bash or other scripting;

• monitoring and troubleshooting production systems; and

• infrastructure security and vulnerability remediation.

Experience with Azure, Terraform, Kubernetes/AKS and Helm would be particularly useful, but we don't expect every candidate to arrive knowing our entire environment.

Just as important, we're looking for someone who:

• investigates rather than guesses;

• can explain what they've tried and what they've learned;

• knows when to keep digging and when to involve someone else;

• notices recurring friction and wants to improve it;

• cares about the people who have to use and support what they build;

• can balance quality against time, cost and risk;

• is comfortable using modern AI tools to investigate problems, understand unfamiliar systems, improve documentation and reduce repetitive work; and

• enjoys understanding why systems behave the way they do.

What “intermediate” means to us:

Intermediate doesn't mean knowing everything or never needing help.

It means you're moving beyond simply completing assigned tasks and becoming someone who can own increasingly significant pieces of a system.

You should be comfortable taking a well-defined piece of technical work and carrying it through with reasonable independence. You can investigate many infrastructure problems yourself, recognize when you're going beyond your depth, and bring in others before it becomes a problem.

We also expect judgment to develop alongside technical skill. That includes thinking about how a change will behave in production, considering the Client Services engineers who will use it, and deciding when a more sophisticated solution is worth the additional time and cost.

Over time, we'd expect you to take on more complex problems and design work, share what you've learned with others, and need less direction about how to get something done.

You might enjoy this role if...

You hold strong opinions, loosely. You know how to develop a solution, but you lean on your team to make it even better.

You like building infrastructure, but you also enjoy figuring out why it broke.

Slow, flaky and unnecessarily manual systems bother you.

You'd rather remove recurring friction than become really good at working around it.

You're interested in how tools such as automation and AI can make engineers more effective, but you're pragmatic about using them where they actually help.

You want to keep growing toward deeper expertise in cloud infrastructure, platform engineering, DevOps or site reliability engineering.

Very few people will match everything above. If the role sounds like a good fit and you meet most of what we're looking for, we'd encourage you to apply.

What you can expect:

• A competitive pay scale commensurate with your skills and expertise.

• A generous medical, dental, and vision benefits plan, along with retirement plans.

• An opportunity to grow both personally and professionally through our CX Academy.

• Freedom to present solutions and ideas in an environment that fosters trust, respect, and service.

• We're committed to work/life balance, not just something we talk about.

• A commitment to corporate transparency with quarterly all-company meetings

Our Interview Process:

• Phone Interview

• Technical Assessment
• Technical Phone Screen

• Technical Interview

• Leadership Team Interview