About Kamino

Kamino's mission is to create liquidity and utility for every asset. We want the world's best investments to be available through the financial platforms people already trust, and we want investors to be able to borrow against what they own when they need liquidity, instead of having to sell.

Today, the most valuable assets in the world are often the least useful to own. Trillions of dollars sit in private markets, behind high minimums and holding periods that can run for years. Tokenization is starting to move these assets onto shared, programmable infrastructure, but putting an asset onchain is only the first step. To be useful, it still needs distribution, compliance, servicing, credit and liquidity.

Kamino already runs the credit and liquidity engine at scale. It is the largest credit protocol on Solana and the largest credit platform for real-world assets onchain, with more than $650 billion in cumulative transaction volume and more than $20 billion in loans originated.

Now we are building the rest of that system for institutions. Kamino recently named Yieldstreet co-founder Michael Weisz as CEO and is building a new HQ in New York, alongside the asset managers and financial platforms that will shape this market. Almost none of that market exists yet, and we intend to build it.

The Role

This is a hands-on infrastructure role focused on operating, automating, and securing the systems that run Kamino in production. You will own infrastructure end to end — from Kubernetes and CI/CD to observability and security — with clear reliability expectations.

The Ideal Kamino Engineer

We hire engineers who love their craft, work fluently with AI, and understand software deeply. Across every engineering role, we look for:

• Seniority: real judgment and high mileage — engineers who have seen many systems break, and know why.
• Strong fundamentals: types, memory, concurrency, distributed systems — and opinions about all of them.
• Builders: people who love to build and tinker, and who ship.
• Quality-oriented: unwilling to ship careless, fragile, or poorly understood code; pragmatic about balancing speed, maintainability, and security in production.
• AI-native: uses modern AI-assisted tooling effectively — to move faster, understand more code, and raise the quality of testing and review.

Must haves

• Strong software engineering and DevOps / infrastructure background.
• Production experience with Kubernetes, including deployments, upgrades, networking, ingress, secrets, resource management, and debugging.
• Strong Linux fundamentals, including processes, networking (iptables/nftables), filesystems, systemd, containers, cgroups, and namespaces.
• Experience operating production systems with clear reliability expectations: monitoring, alerting, incident response, on-call, and blameless postmortems.
• Experience with infrastructure-as-code and deployment automation using tools such as Terraform, Helm, ArgoCD, Flux, Ansible, or similar.
• Experience owning CI/CD pipelines end to end, including build, test, release, rollback, and deployment workflows.
• Understanding of cloud-native architecture patterns: service discovery, load balancing, horizontal scaling, stateless vs stateful workloads, and failure modes.
• Security-conscious approach to infrastructure: least privilege, secrets management, dependency hygiene, image scanning, access control, and auditability.
• Comfortable scripting or building tooling in at least one general-purpose language. Our main stack is Rust and TypeScript, but Python, Go, Bash, or similar experience is also relevant.

Good to have

• Experience running stateful workloads on Kubernetes, including databases, queues, persistent volumes, backup/restore, and upgrade strategies.
• Experience with bare-metal or hybrid infrastructure, and understanding the tradeoffs compared to managed cloud environments.
• Experience with observability stacks such as Prometheus, Grafana, Loki, OpenTelemetry, Jaeger, or similar.
• Experience with software supply-chain security: artifact signing, SBOMs, provenance, CI/CD hardening, dependency management, and container image security.
• Experience designing infrastructure for high-throughput, low-latency, or cost-sensitive systems.
• Experience building internal developer platforms, CLIs, SDKs, deployment tooling, or self-service infrastructure workflows.
• Interested in blockchain: no need to have spent a whole career in crypto, but a genuine interest in the domain.

Competitive advantage

• Experience operating blockchain infrastructure, especially Solana RPC nodes, indexers, Geyser/Yellowstone streams, validators, or high-throughput transaction systems.
• Experience supporting API-heavy products, including developer-facing APIs, SDKs, OpenAPI specs, client generation, API gateways, and rate limiting.

Kamino is an equal opportunity employer and is committed to building an inclusive workplace. Kamino does not discriminate on the basis of race, color, religion, sex, national origin, age, disability, veteran status or any other characteristic protected by applicable law.