Of the ten postings, Khan Academy's is the most strategically revealing because it contains a quiet confession most companies bury: "Our site has been built on Python 2 and Google App Engine for its first 10 years of exis[tence]." That single clause is the entire teardown.

The stack tells a survival story. Python 2 reached end-of-life on January 1, 2020 — roughly three months before this posting. Khan Academy is openly hiring senior backend/fullstack engineers to do what is almost certainly a multi-year migration off a deprecated runtime and off classic Google App Engine (a platform Google itself has been steering customers away from in favor of GAE Standard 2nd gen, Cloud Run, and GKE). The fact that they lead with this in the posting — rather than hiding it — is a recruiting tactic: they're filtering for engineers who get excited about brownfield migrations on systems serving millions of students.

What it reveals about the company's stage. Khan Academy is 10+ years old, non-profit, and load-bearing for global education — and the timing (March/April 2020, school closures worldwide) means traffic just exploded. They explicitly mention being focused on "helping teachers working in their classrooms (and a lot of teachers and parents are using Khan away from their classrooms right now!)." So they're scaling demand and re-platforming and doing it as a non-profit. That's a brutal trifecta.

Skills/trends highlighted:

• Legacy migration expertise is back in demand — the industry is paying off a decade of GAE/Python 2 technical debt simultaneously.
• Remote USA/Canada hiring from a Mountain View company in March 2020 — early signal of the pandemic-driven remote-default shift that would reshape SF Bay hiring within months.
• Mission-driven hiring as compensation strategy — non-profits compete with FAANG salaries by selling impact, and "free education for anyone, anywhere" during a global school shutdown is the strongest version of that pitch they'll ever have.

Green flags: radical honesty about the stack, clear mission, remote-friendly, senior-level roles (no junior burnout fodder for the migration).

Red flags: a 10-year Python 2 / GAE codebase means significant coupling to deprecated APIs (ndb, the old taskqueue, webapp2). Whoever joins is signing up for years of 2to3, datastore migrations, and arguing about whether to go Cloud Run vs. GKE. The posting doesn't mention what target stack they've chosen — which suggests they may not have decided yet.