Sr. Software Engineer - Platform at Stacklok
$189,000–$231,000from the description
Jul 21, 2026
—
Jul 23, 2026
What this job asks for AI summary
A senior backend engineering role focused on designing and owning subsystems within an enterprise platform for running and governing AI agents via Model Context Protocol (MCP) servers on Kubernetes and private cloud infrastructure. The work involves end-to-end delivery of production-grade platform components — such as gateways, runtimes, and registries — written in Go, along with mentoring junior engineers and contributing to an open-source codebase. Best suited to engineers with a strong Kubernetes and Go background who have previously led technical projects from architecture through production.
Senior level · Remote · Full-time
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 22,500 people nationally plausibly meet what this posting asks for (software developers). range 13,500–33,800
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Rare in this occupation — lead with these, and say what you built with them.
What the occupation pays Median $138,970 (middle half $107,524–$175,762). This posting is about at that midpoint.
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (6)
No overall years-of-experience floor is stated; seniority is inferred from the role's scope (end-to-end subsystem ownership, tech-lead mentoring, production enterprise platform).
Go and Kubernetes are listed under 'Desired Skill & Experience' with firm language ('deep proficiency', 'proven track record') and are clearly the primary hard gates for this platform role.
Container technologies (operators, isolation, networking) are bundled with Kubernetes in the same requirement and are not broken out as a separate named tool.
Experience with platform services (gateways, registries, runtimes, deployment tooling) and reliability/observability design are described as required but name no specific technology, so they are omitted per the no-generic-concepts rule.
MCP (Model Context Protocol) is explicitly called 'a plus' in the posting.
The role is fully remote but the posting expresses a strong preference for the US Eastern Time Zone; no specific CBSA applies.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.