> Markdown version of [/jobs/ext/4281928-platform-engineer](https://www.wearedevelopers.com/jobs/ext/4281928-platform-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Platform Engineer - **Company:** ELDER SWAMP CLUB, INC. - **Location:** United States (Remote available) - **Salary:** $175,000 - $235,000 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Continuous Integration, Data Stores, Software Deployment - **Published:** October 31, 2026 - **Apply:** https://www.builtincolorado.com/auth/login?destination=/job/platform-engineer/11999278 ## About the Role * Software Operations fluency: You're comfortable with infrastructure as code, CI/CD, containers, networking, operating systems, cloud platforms, and observability. You don't need to know our exact stack on day one, but you should be able to reason about how its parts fit together, where ownership belongs, and what might break when something changes. You value clear boundaries and explicit contracts between systems and teams. Experience managing a wide range of stacks is a plus. * Collaborating across the organization: You enjoy working with people across engineering, product, security, finance, and beyond. You ask good questions, take each team's needs seriously, and explain technical issues without talking down to anyone. You can challenge a proposal with empathy, explain the trade-offs, and offer a practical way forward. You'd rather build a process that helps people work independently than become a gate they have to pass through. * Reliability: People can depend on your work and trust what you tell them. You follow through on commitments, flag problems early, and are honest about uncertainty or mistakes. You bring the same care to reporting: dashboards, compliance evidence, CI metrics, and cost breakdowns should be accurate, traceable to systems of record, and useful to decision-makers. * Production experience: You've operated production systems, been on call when they broke, and taken part in incident response. You know how to restore service, communicate clearly under pressure, and contribute to a postmortem that leads to meaningful improvements. That experience shapes how you build: you ask how a system will be monitored, maintained, recovered, and supported before it goes live. * Performance instincts: You've profiled real systems, investigated bottlenecks across compute, memory, disk I/O, networking, and service boundaries, and considered capacity before it became a problem. You know when the available telemetry doesn't tell the whole story and add the missing traces or instrumentation to establish what's actually happening. You use that evidence to guide trade-offs between speed, reliability, complexity, and cost. When reviewing a design, you naturally ask where it would struggle at 10x the load and how you would test that. * Grasp on security: You have a working understanding of software supply-chain integrity, including signing, provenance and dependency trust, alongside authentication, authorization, secrets management and isolation for untrusted code. You can work through the threats in a proposed feature, explain the risks clearly to someone who isn't a security specialist, and recommend proportionate safeguards. Experience with SOC 2 or a similar compliance framework is a plus. * AI fluency: You use AI effectively in engineering work: breaking problems into tasks agents can handle, giving them appropriate context, and reviewing their output critically. You can turn security, performance, and operational knowledge into instructions, checks, and tooling that help agents work reliably without constant supervision. You also understand the risks of agent-driven systems, including prompt injection, over-privileged tools, and untrusted context, and can reason about how to contain them. ## Description Platform at Swamp Club is a linchpin of the organization's success. Outside of managing and running swamp-club.com and all its supporting services, it provides the systems and architecture for: * Engineering to ship as quickly, safely, and quietly as possible. * Financial operations to have access to the data they need for analysis and reporting. * Understanding system health and error patterns, including CI, flake, and performance reporting. * Providing compliance reporting evidence outputs and processes. Here are two articles by John Watson, Head of Platform & Co-Founder and hiring leader for this role, that describe how we have approached Platform at Swamp Club. * Alert Triage @ Swamp Club * Architecture @ Swamp Club What You'd Do on a Given Day The Platform team owns the performance and security of the organization and its products, and is embedded in how they're built rather than bolted on afterward. We've built structured workflows that help agents produce code following our architecture conventions. Your job is to make sure those workflows, and the platform underneath them, hold up. A typical day might include: * Catch the scaling cliff in a plan. An agent's plan to fan workflows out across more workers has passed adversarial review. You spot that each job opens its own datastore connection: fine today, but at 10x load it exhausts the pool and takes swamp serve down. You send it back with two sentences on why, and the revised plan arrives in minutes. * Shape decisions, not just outcomes. Product wants extensions to call remote services mid-workflow. Before anyone writes an issue, you work through the trust chain, credential exposure, and isolation with the product engineer. It ships with a security model, not a patch three weeks later. * Make the safe path the fast path. CI time has crept up 20% in a month and two acceptance scenarios flake, but no single PR did it. Your reporting shows where the time and retries go, performance budgets block regressions automatically, and agents get pointed at the worst offenders. * Turn a finding into a convention. An agent handles secrets inconsistently across two production deployments. You fix the underlying vault misimplementation and encode the convention as a skill reference, review check, or acceptance test, so the next 500 agent sessions get it right. * Make SOC 2 evidence a by-product. No screenshots. Proof that every change was reviewed and every dependency patched within policy is wired out of systems we already run, so the auditor can self-serve any day of the year. * Keep an eye on spend. Automated checks flag anomalies in any bill across every provider. Finance never has to ask why the cloud bill jumped. * Keep a clean house. The business depends on a platform that is well understood, documented, performant, and reliable. * Keep the platform healthy. You own alerting, patching, and first response: first in when an alert fires, critical CVEs patched the same day. We don't expect every rollout to succeed, so risky changes ship with a plan for failure, and every postmortem becomes a better alert, guardrail, skill, or workflow. You build the guardrails into the machine that builds the machine.