Outschool's posting (ID 22672707) is the most revealing in this thread because it captures a specific moment: a YC W16 marketplace pivoting from "nice-to-have enrichment" to "essential infrastructure" overnight as schools close. Every word choice matters here.

The stack tells a clear story. They're running TypeScript + React + Apollo GraphQL + Node/Express + PostgreSQL. This is the canonical 2020 "boring-but-modern" stack — no exotic choices, no Rust rewrites, no microservices brag. Apollo GraphQL is the only opinionated pick, and it makes sense for a marketplace: teachers, parents, kids, and classes all have deeply nested relational queries (a class has a teacher who has reviews who have parents who have other enrolled kids). REST would force them into N+1 hell or bespoke endpoints per screen. They're optimizing for iteration speed on a complex domain model, not raw throughput.

What "scaling rapidly to support parents and teachers affected by school closures" actually means. This is a company experiencing involuntary hypergrowth. They didn't plan for COVID; COVID arrived and now their Zoom-based marketplace is suddenly the only game in town. The fact that they're hiring Senior Fullstack — not platform engineers, not SRE, not a VP — signals they still need feature velocity more than they need scalability rescue. The fires haven't reached the database yet.

Cultural tells worth flagging:

• Green flag: "pairing (over Tuple these days)" — they were pairing before remote, and they invested in Tuple specifically rather than defaulting to generic screenshare. That's a team that takes collaboration seriously as a practice, not a perk.
• Green flag: "pragmatic engineers" and "build high-impact product features end-to-end" — no front/back silo, no ticket factory.
• Subtle flag: One role, senior only. They can't afford to train juniors right now. The growth is faster than their ability to mentor.

The trends this highlights: (1) Zoom-as-infrastructure became a load-bearing dependency for entire business models in weeks. (2) Marketplace companies in education are absorbing demand that public institutions can't serve. (3) GraphQL has graduated from "trendy" to "default for product-heavy startups" — no one feels they need to justify it anymore. (4) "Onsite SF" in this posting will age poorly within months; the implicit assumption that offices return is the only dated thing here.