> Markdown version of [/jobs/ext/3055904-staff-software-engineer-platform-engineering](https://www.wearedevelopers.com/jobs/ext/3055904-staff-software-engineer-platform-engineering). 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). --- # Staff Software Engineer, Platform Engineering - **Company:** IREN LLC - **Location:** Seattle, WA, United States - **Experience:** Expert - **Salary:** $184,000.0 - $276,000.0 - **Contract:** Permanent contract - **Skills:** Code Review, Databases, Information Engineering, Software Debugging, Software Design Documents, Distributed Systems, Machine Learning, Open Source Technology, Software Engineering, Large Language Models, Stream Processing, Data Pipelines - **Published:** September 24, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=6eb42a7e1c2ea268 ## About the Role * 10 or more years of professional software engineering experience, several of them at senior level or beyond. * Deep expertise in at least one domain, for example distributed systems, databases and storage, networking, data engineering, or applied AI systems, at the level where you are the person others come to. * A record of technical influence beyond your own team, where the outcome depended on people you did not manage. * Coaching at scale. Be ready to name engineers who grew because of you, and to describe what changed in how they work. * Evidence of multi-year technical judgement: a direction you set, why you set it, and how it held up afterwards. * Excellent written communication. Your design documents persuade people who were not in the room, and remain useful a year later. * Experience owning systems in production, including operations, on-call, and incident response. * A customer centric approach, and the discipline to check that a design makes someone's work easier rather than assuming it does. * Comfort with ambiguity, including the judgement to say that something should not be built. Nice to have: * Experience at a company scaling quickly, where the architecture had to change as it grew. * Experience with high volume data pipelines, streaming systems, or telemetry and time series data. * Experience putting machine learning or LLM systems into production. * Experience working close to physical infrastructure, where the software must account for hardware that fails. * Open source contributions, published work, or talks in your domain. ## Description * Own the technical direction of an area spanning several teams, on a horizon measured in years rather than quarters. * Raise the level of engineers across the organisation: design and architecture review beyond your own team, pairing on hard problems, and writing that teaches. * Deliver large pieces of work by growing the engineers who build them, rather than building everything yourself. * Take on the problems that cross team boundaries and that no single team owns, including the ones nobody has escalated yet. * Write the design documents and technical standards other teams build against. * Be the company's depth in your domain, and make that depth available rather than holding it. * Prototype to settle open questions, so decisions rest on evidence rather than on argument. * Stay hands on. Write and review code, debug production problems, and carry the pager for what you own. * Find where the organisation is slow, and fix the technical causes of it. * Work with engineering managers and product on planning and sequencing, including what the organisation should stop doing., IE US Operations, Inc. "IREN" participates in E-Verify and will provide the federal government with your Form I-9 information to confirm that you are authorized to work in the United States. By applying for this position and submitting your resume and application materials, you consent to the processing of your personal information in accordance with our Job Applicant Privacy Statement available on our website at www.iren.com. ## Related Videos - [Kubernetes and Microservices with Multi-Model Databases](https://www.wearedevelopers.com/videos/382-kubernetes-and-microservices-with-multi-model-databases) - [Are Code Reviews Worth It? Insights from 16 Years of Review Data](https://www.wearedevelopers.com/videos/1135-are-code-reviews-worth-it-insights-from-16-years-of-review-data) - [Why and when should we consider Stream Processing frameworks in our solutions](https://www.wearedevelopers.com/videos/1085-why-and-when-should-we-consider-stream-processing-frameworks-in-our-solutions) - [Platform Engineering vs. DevOps Why not both?](https://www.wearedevelopers.com/videos/885-platform-engineering-vs-devops-why-not-both) - [Fault Tolerance and Consistency at Scale: Harnessing the Power of Distributed SQL Databases](https://www.wearedevelopers.com/videos/1146-fault-tolerance-and-consistency-at-scale-harnessing-the-power-of-distributed-sql-databases) - [Navigating the Corporate Jungle: Life as a Developer in a large Company](https://www.wearedevelopers.com/videos/621-navigating-the-corporate-jungle-life-as-a-developer-in-a-large-company) ## Related Articles - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [Top Characteristics of a Software Engineer](https://www.wearedevelopers.com/magazine/166-top-characteristics-of-a-software-engineer) - [What is Software Engineering?](https://www.wearedevelopers.com/magazine/289-what-is-software-engineering) - [How to Answer the Interview Question: “Why Do You Want to Be a Software Engineer?”](https://www.wearedevelopers.com/magazine/392-how-to-answer-the-interview-question-why-do-you-want-to-be-a-software-engineer) - [Is Software Engineering Hard?](https://www.wearedevelopers.com/magazine/448-is-software-engineering-hard) - [The Best Software Developer Blogs to Read](https://www.wearedevelopers.com/magazine/156-the-best-software-developer-blogs-to-read)