Of the ten postings in this thread, Osmind's is the most strategically revealing — a two-person founding team from Stanford (med school + business school) hiring their first two engineers to build software for FDA-approved psychedelic medicine. Almost every word of that sentence is doing work.

Stack signals (by omission): Notice what's absent — no mention of specific languages, frameworks, databases, or cloud providers. They're hiring a "Lead Engineer" for full-stack web and a separate "iOS Engineer." That's not laziness; that's a founding team who knows they don't yet know. The Lead Engineer will pick the stack. For an ambitious founder, that's the deal: equity + technical autonomy in exchange for building the entire foundation. Expect whoever takes this role to reach for boring, fast-shipping choices — likely Rails, Django, or Node with Postgres, plus native Swift for iOS given HIPAA/PHI constraints on cross-platform frameworks.

Company stage: Pre-product, pre-team, post-thesis. The scope described — booking platform, patient-facing app, provider tools, and a community — is at least three separate products. Two founders and two engineers cannot build all of that. This posting is really about hiring one person who can decide what not to build.

What it reveals about the industry:

• Psychedelic medicine has crossed the investability line. Stanford grad students are now willing to bet careers (and presumably tapped their network for seed capital) on ketamine/MDMA/psilocybin therapy infrastructure. That's a leading indicator.
• The regulated-healthcare SaaS wedge is repeating. Same playbook as Ro, Hims, Cerebral — pick a stigmatized condition, build the whole care journey vertically, own the patient relationship.
• "Onsite [all remote for now]" — dated March 2020 language. The company will have to make a real remote/onsite decision within 18 months, and their instinct is Bay Area onsite. Worth asking about in the interview.

Green flags: Founder credentials fit the problem (med school co-founder = FDA/clinical credibility; business school co-founder = fundraising/GTM). The mission is concrete and defensible. First engineers usually get meaningful equity.

Red flags: No stack, no funding disclosed, no team size beyond "two," no salary band, and no interview process outlined (which the very next commenter, jamespollack, specifically calls out as table stakes). Building a HIPAA-covered patient app with two founders and two engineers is a lot of compliance work per capita. The "community" component in a mental-health app is a moderation and liability minefield.