The goal is to dismantle current complexities and replace them with an "industrial-grade" self-service platform that enables independent operation for application teams. You'll be working on industrialization of software production - the customer wants to move to a model where infrastructure is an invisible enabler.

Start: Q2 (flexible)
Duration: 6 months, extension possible
Location: Espoo (2–3 days a week on-site)
Language: English

The current challenges:

• The current infrastructure has become a bottleneck, where fragmentation and manual work slow down product development.
• Massive Fragmentation: Deploying a single new service (e.g., fire-archive-service) requires managing 33–38 files across two different repositories (data-platform and analytics-deployment-configurations).
• Cognitive Load: Developers must master at least five different technologies: Terraform (HCL), Kubernetes (YAML), Helm, FluxCD, and GitHub Actions.
• Dependency Locks: Infrastructure changes require multiple sequential PR processes and coordination between different teams, turning simple updates into multi-day efforts.
• Lack of Standardization: Manual configuration leads to "configuration drift," where security controls (IAM policies, network settings) and monitoring may be forgotten or vary between services.

Vision & Goals for the Infra Platform Architect:

• "One Touch" Service Deployment: Create a self-service platform that automatically generates all necessary configurations in the background. The goal is to have a new prototype up and running in a single day.
• All-in-One Repository: Transition to a model where infrastructure and application configurations reside in the same place, reducing context switching and the need for coordination.
• Higher Abstraction: Minimize Kubernetes and deployment configurations to a level where the application team manages the entity via a single file.
• Migration Path: Develop a tool to move existing projects into the new structure (including backup and revert capabilities) and demonstrate functionality by migrating three current applications.
• Automated Platform Tools: Enable Atlantis, Flux, Helm charts, and GitHub Actions workflows directly within application repositories.

Technical expertise:

• The expert is expected to look beyond the technology stack (AWS, EKS, RDS, S3) and build sustainable architectural models.
• Strong Terraform expertise (including state management with S3/DynamoDB locking).
• GitOps & CI/CD: Experience with FluxCD (ECR polling, Helm updates) and Atlantis (automated project generation, OPA policy checks).
• Deep understanding of Kubernetes, Helm templates, and Kustomize overlay structures.
• Ability to build IDP (Internal Developer Platform) solutions that abstract complexity without sacrificing flexibility.

Desired consultant profile:

• Pragmatic Approach: Preference for "boring" but functional solutions. Understanding how to keep the Total Cost of Ownership (TCO) of a solution under control.
• Courage to challenge current practices and the ability to mentor the team even during a chaotic growth phase.
• Courage to provide direct, honest feedback and challenge the status quo. You don't just point out problems; you take ownership of the solutions.
• You are comfortable working in a high-growth "startup-to-scaleup" phase where processes are still being built, and you can maintain focus despite a bit of chaos.
• You are a senior peer who is eager to share knowledge, coach others (mentor), and learn from your teammates. You value the best idea over the highest rank.
• "Boring is Beautiful": You prioritize stability, maintainability, and simplicity over "shiny" new tools.
• A background in actual software development (not just Ops) is a major plus. It helps you understand the "developer experience" you are building and allows you to build better abstractions.
• Experience from sectors like FinTech, Insurance, or Defense—where data integrity, security, and "clean data" are paramount—is highly beneficial.
• Product-Led Growth: Experience in product-centric organizations where you have seen how infrastructure scales (or breaks) during rapid global expansion.
• The client values "scars"—experience from past failures and migrations that didn't go as planned. You know what pitfalls to avoid because you’ve seen them before.

Interested in a new challenge? Please contact Lisa_Witted in Slack or lisa.sandstrom@witted.com asap.