Platform Engineer - Fintech/ Crypto
What engineering roles in crypto pay
243 salaries · our own dataMost engineering roles in crypto pay between $146k and $255k, with a median of $202k.
As a Platform Engineer at Incubly, you will work with a leading cryptocurrency and blockchain security company with over 400 professionals to improve developer experience and remove friction from the build, package, and deployment process. You will own and evolve developer tooling, self-service platforms, CI/CD infrastructure, artifact management, progressive delivery systems, and observability across the organization.
What you'll do
- Own and evolve the self-hosted GitHub Actions runner fleet, including Linux runners managed via Actions Runner Controller (ARC), self-hosted macOS runners, and Terraform modules that provision and scale self-hosted infrastructure.
- Right-size runner classes (CPU/memory/storage) against real workload profiles, balancing cost efficiency against engineering velocity.
- Support the migration away from GitHub-hosted runners, evaluating trade-offs between containerized and VM-based execution for workloads with special hardware requirements such as KVM access for Android emulators.
- Partner with embedded DevOps engineers on pipeline and dependency-graph optimizations (build triggers, job fan-out, monorepo change detection) to reduce queue times and CI spend.
- Investigate and resolve macOS virtualization performance issues (e.g. Tart) and evaluate alternative approaches such as remote simulator hosts.
- Administer the JFrog Platform (Artifactory, Xray, Curation) as the organization's primary artifact repository, including repository structure, access control, vulnerability scanning policies, and curation of upstream dependencies.
- Provide support for GitHub Container Registry (GHCR) and GitHub Packages where teams use them alongside JFrog.
- Operate and maintain ChartMuseum as the organization's Helm chart repository, hosted on S3, including storage lifecycle, access, and chart promotion workflows.
- Define and enforce container image ownership boundaries between platform-owned hardened/minimal base images and engineering-owned project extensions, and drive Dockerfile build and layer optimization best practices across teams.
- Operate ArgoCD and Argo Rollouts environments serving internal tooling and product workloads, supporting GitOps-based progressive delivery patterns (canary/blue-green) for engineering teams.
- Author, maintain, and support Helm charts and Kustomize overlays as the standard configuration management approach for Kubernetes workloads, providing golden-path templates that reduce boilerplate for product teams.
- Design, review, and evolve Terraform and Terragrunt modules for infrastructure-as-code, maintaining a public and internal module registry that product and platform teams can consume in a self-service manner.
- Improve and help unify the observability stack (Grafana, Prometheus, Alertmanager), fixing metric accuracy issues, building meaningful dashboards, and defining SLOs and alerting that reflect real platform and pipeline health.
- Work across Datadog and VictoriaLogs/VictoriaMetrics to reduce tool sprawl and help define a coherent strategy for where metrics, logs, and events should live.
- Provide platform-level telemetry (runner utilization, build queue times, artifact scan results, deployment health) that gives engineering teams and leadership a single, trustworthy view of pipeline and platform performance.
- Evaluate and help operate Crossplane as a control-plane layer for self-service, Kubernetes-native infrastructure provisioning, complementing the existing Terraform and Terragrunt IaC estate.
- Contribute to a developer portal and internal catalog strategy (e.g. Backstage, Cortex, or Port) so engineers have a single place to discover services, ownership, documentation, and golden-path templates.
- Implement and maintain policy-as-code guardrails using Kyverno and/or Open Policy Agent (OPA) across the Kubernetes and CI/CD estate (e.g. image provenance, resource limits, security baselines).
- Support Knative-based serverless and event-driven workloads on Kubernetes where teams need scale-to-zero or request-driven compute.
- Roll out OpenTelemetry instrumentation and pipelines to standardize traces, metrics, and logs across services, feeding the Grafana/Prometheus/Datadog/VictoriaLogs stack with consistent, correlated telemetry.
- Act as the platform's embedded point of contact for one or more product engineering teams: understand their day-to-day friction, prioritize platform work accordingly, and close the loop on delivery.
- Build self-service tooling, templates, and documentation (golden paths) so engineers can provision runners, publish artifacts, and deploy without needing deep platform expertise.
- Clearly document ownership boundaries between platform and product teams and help engineering teams operate confidently within them.
- Contribute to the platform roadmap, bringing a developer-experience lens to prioritization and measuring success in terms of engineer-facing outcomes such as build time, queue time, and self-service adoption.
What you bring
- 5+ years in a Platform Engineering, DevOps, SRE, or infrastructure engineering role, ideally supporting product engineering teams directly.
- Hands-on experience with GitHub Actions, including self-hosted runner architectures (Actions Runner Controller / Kubernetes-based Linux runners, self-hosted macOS runners) and provisioning them via Terraform.
- Practical knowledge of the JFrog Platform (Artifactory, Xray, and ideally Curation) for artifact management and dependency security.
- Familiarity with container registries beyond a single vendor (GHCR/GitHub Packages) and Helm chart repositories such as ChartMuseum on object storage (S3).
- Experience with GitOps continuous delivery using ArgoCD, and ideally Argo Rollouts for progressive delivery (canary/blue-green) across multiple clusters and environments.
- Strong Kubernetes configuration management skills with Helm and Kustomize.
- Solid Infrastructure-as-Code experience with Terraform and Terragrunt, including designing and consuming shared and reusable modules.
- Experience with Crossplane or a comparable Kubernetes-native control-plane approach for building self-service infrastructure APIs, alongside deep Terraform proficiency for the underlying IaC.
- Experience building or operating an internal developer portal or software catalog such as Backstage, Cortex, or Port, including modeling service ownership and scorecards.
- Hands-on experience with policy-as-code enforcement in Kubernetes using Kyverno and/or Open Policy Agent (OPA / Gatekeeper), for example image provenance, resource limits, and security baselines.
- Familiarity with Knative or similar Kubernetes-native serverless and eventing frameworks for scale-to-zero or request-driven workloads.
- Experience building, hardening, and optimizing container images (Dockerfile best practices, minimal and hardened base images such as Docker Hardened Images or Chainguard).
- Working knowledge of an observability stack (Grafana, Prometheus, Alertmanager) plus exposure to Datadog and/or VictoriaLogs/VictoriaMetrics, and practical experience instrumenting services and pipelines with OpenTelemetry (traces, metrics, logs).
- Comfort in Linux/Unix environments, with solid scripting ability (e.g. Bash, Python, or Go) and strong Git fundamentals.
- Genuine product mindset toward internal platforms: you think in terms of the engineer as a customer and seek out and act on their feedback.
- Strong cross-functional collaboration skills, comfortable embedding with a product engineering team and building trust with people who don't share your infrastructure background.
- Clear written and verbal communication, able to explain infrastructure concepts (e.g. Kubernetes, runner sizing, build performance) to engineers without a platform background and tailor the level of detail to the audience.
- Pragmatic and cost-conscious approach, able to balance reliability, security, developer speed, and infrastructure cost, and make and explain trade-offs rather than defaulting to "more resources."
- Ownership mindset with strong personal accountability; comfortable working autonomously and driving initiatives from discovery through to rollout.
- Curiosity and commitment to continuous improvement: proactively investigate root causes (e.g. inconsistent metrics, flaky runners) rather than just resolve symptoms.
- Comfort with ambiguity and evolving priorities, and ability to sequence and negotiate scope in a fast-moving environment.
- Empathetic and collaborative approach when defining ownership boundaries between platform and product teams, favoring clarity and shared documentation over friction.
Nice to have
- Experience supporting mobile and device-testing CI (e.g. Android emulator/KVM requirements, iOS simulators) in a self-hosted runner context.
- Experience developing platform APIs and CLIs for developers to consume blueprints and patterns using Kratix or Crossplane tooling.
- Experience with large Kubernetes cluster fleet automation from provisioning to upgrade to decommission.
- Experience operating in a large monorepo, including build-graph and dependency-aware CI triggering.
- Prior experience defining or operating SLOs/SLAs and error budgets for internal platform services.
- AWS cloud experience (compute, storage/S3, networking fundamentals).
What we offer
- Possibility to choose remote work or on-site work in Lodz, Poland.
- B2B or Employment Contract - you choose.
- Remuneration on B2B contract: 1,200-1,400 PLN net per day.
- Remuneration on Employment Agreement: 19,000-22,000 PLN gross per month.
- Agile and friendly atmosphere with non-violent communication and full respect for diversity.
About Incubly
Incubly supports tech companies and startups in scaling their teams quickly and with high quality, boosting product development, testing, and deployment. You will work with a leading cryptocurrency and blockchain security company with over 400 professionals developing products and services to safeguard cryptocurrency assets, including worldwide-leading hardware wallets.
