Senior Infrastructure Solutions Engineer in Berlin

• A Senior Infrastructure Solutions Engineer makes Planet’s infrastructure easier to use
• Infra Solutions is a small, multi-disciplinary team: engineers who are as comfortable operating a system as building one, and as comfortable in a hard conversation as in a code review
• We sit between the teams who build Planet’s platform capabilities and the teams who need them, and our market is every engineering team at Planet, which we earn one engagement at a time
• Teams work with us because we make their week lighter, not because anyone told them to, and every team that lands on the platform is infrastructure Planet no longer has to duplicate, secure and pay for
• Most of what you do takes the shape of a hands-on engagement with a team that is blocked, mid-migration, or arriving on the platform for the first time
• They usually arrive with a proposed solution rather than the problem behind it, and working out the difference is where the engagement starts
• From there you own it end to end: the diagnosis, the hands-on fix, the argument for what should change upstream, and the durable artifact that stops the next team hitting the same wall
• This is a role driven by unreasonable hospitality (value out of proportion to what anyone asked us for) and backed by solid engineering and operator depth
• You have run things in production, and you write the code other engineers depend on
• Lead end-to-end technical engagements: Partner directly with engineering teams to diagnose, unblock, and resolve complex infrastructure challenges
• Execute critical migrations: Develop reference implementations, tooling, and guidance to transition teams off deprecated systems seamlessly
• Accelerate platform adoption: Act as the primary technical contact for new teams onboarding to Planet’s core infrastructure
• Establish standardized paths: Consolidate disparate solutions into well-supported, paved-road infrastructure offerings
• Build scalable, shared artifacts: Design re-usable libraries, Terraform modules, and Helm charts to solve recurring technical patterns across teams
• Enhance platform observability: Implement instrumentation and attribution tooling to provide visibility into infrastructure cost, usage, and adoption
• Inform platform strategy: Synthesize engineering feedback and common pain points to influence the broader infrastructure roadmap

Benefits

• Comprehensive health plan
• Wellness program and massages
• Flexible time off
• Recognition programs
• Commuter benefits
• Learning and tuition reimbursement
• Parental leave
• Offsites and happy hours
• Volunteering benefits

The ideal candidate is energized by other teams’ success: someone who would rather ship the thing that makes ten teams faster than own a system outright, and who does their best work in a room they don’t own, with people who are not yet convinced they need helpProficiency in software development using Go or PythonWorking knowledge of Google Cloud Platform (GCP) or other public cloud providers, including its compute, storage, quota, and capacity mode6+ years of professional experience in Platform Engineering, DevOps, or Site Reliability Engineering, including experience leading at least one cross-team project or migrationAbility to translate ambiguous requirements into structured, actionable engineering tasksDeep expertise with Kubernetes orchestration, including workload optimization and operationsHands-on experience operating and maintaining production infrastructure environmentsExperience with Infrastructure as Code (Terraform, Helm, ArgoCD) and CI/CD pipelinesBackground in technical enablement, developer experience, or solutions architecture with a focus on internal developer productivityExcellent written and verbal communication skills for technical documentation and cross-functional collaborationBachelor’s degree in a relevant fieldExperience driving large-scale migrations or deprecations that required buy-in from teams outside your reporting lineExperience with large-scale block storage (Persistent Disk, Hyperdisk, Ceph, SAN, or equivalent) operated at fleet scale rather than per-serviceExperience in a consulting-adjacent engineering role (solutions architecture, professional services, or technical account engineering) applied to an internal platformFamiliarity with workflow orchestration (e.g. Temporal), batch and job-execution systems, or large-scale data processing pipelinesExperience defining and measuring platform adoption: developer-productivity instrumentation, NPS, or internal marketshare

#J-18808-Ljbffr