Fictional sample role — Glasspine Logistics is not a real company and this is not a real job opening.

Idynic publishes this posting so anyone can see exactly what our product reads when it analyzes a role. No application is collected and no one is hiring.

Staff Platform Engineer, Developer Infrastructure

Glasspine Logistics. Freight coordination software for regional carriers.

Location
Remote (United States) — optional office in Denver, CO
Employment type
Full-time
Team
Platform Engineering (9 engineers across compute, delivery, and developer experience)
Compensation
$185,000 – $225,000 base, plus equity and a 10% target bonus. We publish the band and we do not negotiate off it based on your current salary.

About Glasspine Logistics

Glasspine Logistics builds the coordination layer that regional freight carriers use to plan loads, route drivers, and settle payments. Roughly 240 carriers move about 1.1 million shipments a month through our platform.

We are 180 people, about 70 of them in engineering, and we have been profitable since 2023. We are remote-first across the United States with an optional office in Denver.

About the role

Our engineering organization has tripled in three years and our internal platform has not kept up. Teams ship through a mix of inherited pipelines and one-off scripts, our Kubernetes footprint has grown to four clusters that were each configured by a different person in a different year, and a routine infrastructure change still routes through a ticket.

We are hiring a staff platform engineer to own the paved road: the path an engineer takes from a merged pull request to serving production traffic, and everything that makes that path safe. This is a hands-on individual-contributor role with real scope — you will set the technical direction for developer infrastructure and you will write the code.

The honest version of this job: the first year is consolidation work. There is a real mess to clean up, the teams are friendly, and nobody is going to mandate adoption on your behalf. If you like earning migrations rather than ordering them, you will like it here.

What you'll do

  • Own the internal deployment platform end to end — the service manifest, the delivery pipeline, and the progressive-rollout tooling that sits in front of production traffic.
  • Consolidate four independently grown Kubernetes clusters into a coherent, multi-cluster topology with a documented and tested regional failover story.
  • Extend and maintain the control-plane services that back our developer tooling. These are Go services and you will be a primary owner of them.
  • Lead the Terraform estate out of a large shared root module into versioned, reviewable modules that product teams can adopt self-service.
  • Reduce CI wall-clock time and flakiness for roughly 70 engineers; own build caching, test sharding, and the merge queue.
  • Set the observability standard — SLOs, alert budgets, and an on-call model the platform team itself carries.
  • Partner with our compliance function on the controls that keep us PCI-DSS compliant as a payments-adjacent platform.
  • Mentor mid-level and senior engineers and grow the team's platform capability; run design review for infrastructure changes.

What we require

  • 7+ years in infrastructure, SRE, or platform engineering, including time carrying production on-call.
  • Deep production Kubernetes experience — you have operated multi-cluster environments, not just deployed to one.
  • Expert-level infrastructure as code with Terraform, including module design and a real migration off a monolithic root module.
  • You have owned a CI/CD system that other teams depended on, and you have measurably improved its speed or reliability.
  • Production Go — you have shipped and operated at least one Go service that other people relied on. Our control plane is Go and you will own parts of it.
  • Strong observability practice: SLOs, meaningful alerting, and incident response you have led rather than participated in.
  • A track record of driving platform adoption across teams you do not manage.

Nice to have

  • Experience operating under PCI-DSS, or another payments or financial compliance regime.
  • Service mesh in production (Linkerd, Istio, or equivalent).
  • Open-source maintainership — you have run a project with outside contributors.
  • Meaningful infrastructure cost-optimization work with numbers attached.
  • Google Cloud Platform depth; we have a small GCP footprint we would like to run properly.
  • Logistics, supply chain, or another domain where the physical world constrains the software.

Benefits

  • Remote-first across the US, with a quarterly team on-site.
  • Fully covered medical, dental, and vision for you and dependents.
  • $3,000 annual learning budget and conference travel.
  • 16 weeks paid parental leave, all parents.
  • Four weeks of vacation with a two-week minimum we actually enforce.

How we hire

We read every application ourselves. Our process is a 45-minute conversation with the hiring manager, a 90-minute paid technical session on a real problem from our backlog, and a team conversation. We give a decision within five business days of the final round.

Fictional sample role — Glasspine Logistics is not a real company and this is not a real job opening.

Idynic uses this posting as a fixed, public input so our product demonstrations run against the same pipeline our customers do. Nothing on our examples is staged or mocked up.