Cloud Engineer

Times are changing. Fast. And we want you to transform the Cloud space with us!

This is why we have created a whole new genre of devs who'll bring us to the next level and beyond.

We want to grow with a low-ego, collaborative and backend-focused cloud developer who acts as a force multiplier for the engineering team. The connective "spider in the web" (sorry) that makes everyone else ship faster, more safely, and more consistently. Rather than adding to a product backlog, you will build the internal tooling, shared services, and paved roads the rest of the team builds on, smooths the path from code to production, and brings engineering discipline to teams now moving fast with AI-assisted development.

Sounds like the role you've been searching for?

Your role:

This is a developer-productivity role at heart. On assignment, the Cloud Developer is the person who makes a client's engineering team faster and more effective: building the internal services, libraries, and tooling the rest of the team relies on, and the paved roads that make shipping fast, safe, and repeatable. They are the connective tissue across product code, tooling, and infrastructure. Less the person shipping the next feature, more the person who makes shipping anything easier for everyone else.

The cloud is the substrate they work in; developer experience is the product. The forward-looking angle is where the need is coming from. Client engineering teams are now moving fast with AI coding tools, and that speed only pays off if the surrounding machinery keeps up, the guardrails and tooling, that let a team ship AI-assisted code safely and consistently. This role is that someone: raising the bar on how an organisation builds, now that much of the building is AI-accelerated.

What this role is:

• Building the internal services, libraries, and developer tooling — primarily in Go — that the rest of a client's engineers build on
• Smoothing the path from code to production: CI/CD, build and release tooling, and the paved roads that make shipping fast, safe, and consistent
• Reducing friction and toil across the engineering workflow — the connective work that lifts a whole team's output
• Bringing discipline to AI-accelerated development: the guardrails, patterns, harnesses, and tooling that let a team move fast with AI without shipping a mess

What this role is not:

• Not a "vanilla" product developer. This isn't about churning out business logic and enduser features; the value is in multiplying a team's output, not adding to its backlog
• Not a frontend, data-engineering, or ML/Data Science career path. This person integrates and consumes AI services, they don't build data pipelines or train models as their craft

Your temperament matters as much as your stack and ambitions. You'll join a team with traits that are strikingly consistent: a curious, low-ego builder who takes real ownership of quality and reliability, communicates clearly, and is happiest making both the work and the people around them better.

Concretely, that means someone collaborative and unterritorial — focused on lifting the team around them rather than guarding turf — and pragmatic and outcome-oriented, bridging technical work and business goals and comfortable with product and stakeholders

Skils & Background

• 5+ years as a developer/SW engineer/programmer/cloud engineer, who enjoys building for builders
• Go (Golang) is your home turf + you have depth and feel comfortable in at least one other, modern, language like, C#, Python, Java, or Typescript
• AWS, Azure, or GCP — any one, or a combination, heck even onpremises counts
• Any infrastructure-as-code — Pulumi or Terraform are preferred
• Demonstrable interest in AI is required, hands-on experience a plus*
• Managed or self-managed Kubernetes (Bonus, not a requirement)
• Fluency in Swedish and English, as most of our collaborations and client projects are conducted in Swedish

*Interest in AI is a requirement for this role; hands-on AI experience is a strong plus but not a prerequisite. The bar, though, is evidenced curiosity rather than a bare claim of interest — we want someone who can actually show something.

Required: genuine, demonstrable engagement with AI tooling — a side project, real use of AI coding assistants, or a considered first-hand opinion formed from building with them.

A strong plus: hands-on experience with AI/LLM infrastructure and frameworks — AWS Bedrock / AgentCore, Vertex AI, agentic frameworks, Claude Code, and similar.

Applying to us is a breeze!

• Upload your resumé or use your Linkedin profile
• Answer the choice-questions (no "please-rewrite-your-resume" nonsense, promise)
• Feel free to include links to your portfolio, GitHub or similar if you have stuff you're proud of that you want to share with us