Staff Engineer, Internal Platform and APIs - Greenstep Espoo

Tiivistelmä työpaikkailmoituksesta: You will own Greenstep's internal platform architecture and build centralized, versioned APIs on AKS while leading internal developers and deciding what to consolidate, rewrite or delete. The role requires 7+ years in software and cloud engineering with strong Python backend skills, production Kubernetes and Azure experience, Terraform proficiency, event-driven scaling knowledge, and technical leadership without a management title. The position is based in Espoo with a hybrid model (minimum 50% on-site) and requires a full-time work permit as Greenstep does not sponsor visas. Greenstep offers a salary model that matches responsibilities and experience, participation in a "Together" bonus sharing 10% of annual profit, and benefits for well‑being and professional development. Tämä tiivistelmä on luotu tekoälyn avulla. Have you ever looked at a sprawling internal IT estate and known exactly how much smaller and safer it could be? We have one. Hundreds of repositories and thousands of Azure Functions, Logic Apps and low-code flows, built by many hands over many years. We are looking for one person to own turning it into a small number of well-designed, centralized APIs running on Kubernetes. Greenstep is a Finnish, family-owned growth company founded in 2010 that provides high-quality technology and back-office services to support its clients' growth and success. Today we are a community of more than 800 experts working in the Nordics and across Europe. We have grown organically, and today Greenstep has people in Finland, Åland, Sweden, Norway, Estonia, Denmark and the Netherlands. We share one goal: to help growth companies become leaders in their fields. Our internal automation grew as fast as the company did. It works, mostly, and nobody can see all of it. That is the problem you will solve. The Role You own the target architecture for Greenstep's internal platform and you build a large part of it yourself. You lead our internal developers technically, and you decide what gets consolidated, what gets rewritten and what gets deleted. Deleting is a big part of the job. What will you do as a Staff Engineer: Set and own the target architecture and build most of it. A handful of centralized, versioned APIs with clear ownership, running on AKS, with authentication, observability and access control solved once instead of in every repo. Inventory the estate, then shrink it. You map what exists, decide what gets consolidated, what gets rewritten and what gets deleted. Deleting is a big part of the job. Design the migration so it is boring. Functions and Kubernetes run side by side while traffic shifts incrementally. No big-bang cutover, no weekend where payroll stops. Move business logic out of low-code. HR, payroll, finance and client onboarding flows become services that can be tested, versioned and reused. Build the platform, not just the services. Service templates, CI/CD, GitOps, infrastructure as code, secrets handling, API gateway, tracing and metrics. You set the standard by shipping it first. Make agentic development normal here. Migrating thousands of functions by hand is not realistic. You design the workflow, the review gates and the guardrails that keep AI-generated code safe to put in front of payroll data, and you use these tools heavily yourself. Lead the internal developers technically. Architecture reviews, pairing, code review, and a roadmap business stakeholders can actually follow. Partner with the App Factory staff engineer, who owns the internal applications, so those apps consume your APIs instead of talking to source systems directly. What we're looking for You have taken a sprawling estate and made it smaller and safer before. You can describe what you kept, what you killed, and how you got people to agree. You are as comfortable in a design review as you are explaining to a payroll team why their flow is being replaced and what they gain. What you bring: 7+ years in software and cloud engineering , including several years leading platform or API consolidation at scale. You can describe an estate you made smaller: what you kept, what you killed, and how you got people to agree. Deep Python backend experience, and the judgment to know when a service should not be Python at all. Production Kubernetes you have operated, not just deployed: Helm, GitOps, ingress, secrets, resource limits, upgrades. Event-driven workloads on Kubernetes, specifically KEDA or equivalent. You know why scale-to-zero and queue-depth scaling decide whether this migration saves money or costs it. Azure fluency: networking, security, Entra ID, Workload Identity, Key Vault, API Management, Functions and Logic Apps, including how to migrate off the parts that should not be there. Terraform , as the single source of truth for infrastructure. State management, modules, drift, and a review process that treats infrastructure changes like code changes. Security as a default, not a review stage