The most revealing thing about Notion's posting (ID: 22665940) isn't what it says about tech — it's who wrote it. The founder himself, Ivan Zhao, is manning the recruiting post. That single fact tells you more about Notion's stage in early 2020 than any org chart could.

The pitch, not the stack: Notice what's missing. There is no tech stack. No "React/TypeScript/Postgres." Instead, Zhao delivers a manifesto: "create the general purpose work tool for a post-file, post-MS Office world." He frames competitors dismissively — Google Docs and Dropbox Paper are "multiplayer WordPerfect"; SaaS apps are "forms + a table + some buttons." This is deliberate. Notion is selling vision to engineers who could work anywhere, betting that ambition beats comp packages.

The stage signal: Hiring across Engineer, Designer, Sales, Marketing, PM, Support in a single post means every function is understaffed. That's classic Series-B-to-C territory — product-market fit is proven, revenue is real, and now they need to scale every org simultaneously. The SF-only, onsite-only stance in an era when remote was already gaining traction reveals Zhao's bet that in-person collaboration was still a moat for creative product work.

What the framing highlights:

• Design-led engineering culture — putting "Designer" second in the role list (before Sales) is a tell about internal hierarchy.
• Founder-mode recruiting — the CEO reading HN comments is a proxy for how flat the org still is.
• Category creation, not feature competition — the "post-file" language positions them against a paradigm, not a product.

Green flags: Direct founder engagement, coherent thesis, willingness to name competitors by weakness rather than dodge them. The self-aware joke about knowledge-worker tools being "the hot startup topic of the 90s" signals intellectual honesty about how hard the problem is.

Red flags: The onsite-SF rigidity would age poorly within months (this posting is from March 2020, right as COVID hit). No mention of comp, equity, benefits, or seniority levels means candidates self-select on belief — great for culture, terrible for compensation transparency. The lack of any technical detail also means engineers can't evaluate whether the codebase matches the marketing.