Of the ten postings in this thread, Trello's SRE listing is the most strategically revealing because it exposes the operational tension inside a maturing Atlassian acquisition. The posting is short, but every sentence is loaded.

The scale math is the whole story. Trello openly states it supports "over 35 million users today" and is targeting "100 million users" while holding 99.99% uptime. That's a ~3x growth ambition against a four-nines SLO — roughly 52 minutes of downtime per year. Hiring an SRE (singular, from the title) rather than an SRE team suggests they are either understaffed for that goal or building out a discipline that historically lived inside product engineering.

What the tech stack signals. The posting doesn't name languages, which itself is a tell — Trello's public engineering brand has long been Node.js, MongoDB, and CoffeeScript-turned-TypeScript, and the omission suggests they're recruiting on reliability practice rather than stack fluency. For an SRE role, that's the right emphasis: they want someone who thinks in error budgets, incident response, and capacity planning, not someone who wants to rewrite services in Go.

The org-culture pitch is doing heavy lifting. Two lines stand out:

• "Our engineers and designers run the show with management existing to support, not dictate."
• "We're strongly against separations of responsibility and throwing work [over the wall]" (sentence cut off, but the anti-silo message is clear).

This is a direct recruiting jab at post-acquisition Atlassian bureaucracy fears. Trello was acquired by Atlassian in 2017, and by 2020 candidates would reasonably worry about being absorbed into a larger, more process-heavy org. The posting is preemptively defending against that.

Green flags: Remote-friendly (NYC / Remote) years before that was the default, a concrete uptime target that gives the role measurable success, and honest scale numbers instead of vanity metrics.

Red flags: A single SRE hire against a 3x growth target is a workload risk — whoever takes this job will either build the practice from scratch or inherit oncall for a system they didn't design. The lack of stack detail also means candidates can't self-filter, which usually means more recruiter screens.

Skills highlighted: reliability engineering as a distinct discipline from backend eng, capacity planning at tens-of-millions scale, and the growing expectation that SREs operate autonomously rather than as a ticket-taking ops team.