Full-Stack Developer Needed for Stanford Social Wellness Platform Prototype (Web App)

Description We are building Cardinal Hearts, a Stanford-centered digital wellness and anonymous peer support platform designed to help students navigate romantic relationships--share experiences, seek support, access personalized resources, and foster meaningful reflection in a psychologically safe environment. The platform will be fully accessible across both mobile and desktop devices, with a seamless, intuitive experience on each. We are looking for a talented full-stack developer to build a high-resolution functional MVP/prototype with scalable frontend and backend architecture. This is not a traditional social media platform — the interaction model should feel intentional, supportive, privacy-conscious, and community-centered. --- Core Features Frontend Development We need a modern, clean, responsive application that works seamlessly across: * Mobile devices * Tablets * Desktop/laptop browsers Key features include: * Anonymous posting feed * Post creation flow * Stanford-inspired branding/aesthetic * Tagging/filter system: * “Seeking Advice” * “Just Wanted to Share” * User onboarding/login flow * Saved/bookmarked posts * Ability to “follow/save” posts for later viewing * Personal Diary feature (see below) * Responsive UI optimized for both mobile and desktop --- Community Interaction Features We want engagement to feel emotionally supportive rather than performative social media. Features include: * “I Resonated” reaction button on posts * Anonymous resonance counts visible publicly * Optional sorting/filtering by most resonated posts * Private “This Didn’t Resonate” feedback option (not visible to other users; used only for internal analytics and personalization) * Aggregate engagement signals used to improve content surfacing and recommendations --- Diary Feature (Personal Reflection System) Each user will have a **Diary**, which serves as their personal timeline of activity and reflection. Core functionality: * All public posts automatically appear in the user’s Diary, organized by date * Users can also write **private diary entries** that are never shared publicly * Clear distinction between: * Public posts (community-visible + stored in diary) * Private reflections (personal only) Diary capabilities: * Chronological timeline view of all entries * Ability to filter between public and private entries * Optional tagging of entries (e.g., reflection, advice-seeking, personal note) * Centralized place to revisit personal experiences over time --- Mood & Reflection Calendar Feature We also want a reflective mood tracking system inspired by apps like *Natural Cycles*. When users reflect or write in their diary, they can optionally select a **mood using an emoji-based system** (e.g., “Anxious 😟”, “Sad 😔”, “Calm 🙂”, etc.). Core functionality: * Users can attach a mood to each entry (optional) * Mood input should be fast and lightweight (emoji + label selection) Visualization: Users can view their data in: * Daily view (mood + associated entries) * Weekly trends * Monthly calendar or heatmap visualization of mood patterns Purpose: This feature helps users identify emotional patterns over time by connecting: * Mood states * Life events/reflections * Written posts Example: A user may notice repeated “anxious” moods on days involving a specific relationship dynamic, enabling deeper self-awareness and reflection over time. The goal is to support insight, not diagnosis — helping users better understand emotional patterns and triggers. --- Resource Library + Personalized Recommendations We are also building a curated **digital resource library** populated with materials from Stanford’s SHARE (Sexual Harassment/Assault Response & Education) office. Library may include: * Books * Articles * PDFs * Support resources * Educational materials Features: * Admin upload and management system * Categorization/tagging of resources * Personalized recommendations based on: * User posts * Diary entries * Mood data * Tag usage Recommendation system: Can initially be rules-based (no need for full AI at MVP stage) Examples: * Users expressing loneliness may be shown community/support resources * Users seeking relationship advice may receive relevant reading materials Privacy and sensitivity are critical to design. --- Analytics Dashboard (Admin/Internal) We need a basic analytics dashboard including: * Total users * Daily/weekly active users * Posts over time * Most-used tags * Most resonated-with posts * Resource engagement metrics * Repeat visitor tracking Advanced visualization requests: * Calendar view of engagement activity * Heatmap-style visualization for user engagement over time * Trend tracking for usage patterns (daily/weekly/monthly) We are open to recommendations for the best charting libraries/tools. --- Backend Development Requirements * Secure Stanford-only login/authentication * Stanford SSO preferred if feasible * Otherwise .edu-based restriction system * Database architecture and setup * Anonymous posting logic (ensuring privacy separation from identity) * User accounts and diary storage system * Saved posts/bookmarking system * Tag and category management * Moderation/reporting tools (basic MVP) * Scalable backend structure for future expansion --- Preferred Tech Stack Open to recommendations, but currently considering: * React / Next.js * Node.js * Firebase or Supabase * PostgreSQL --- Ideal Candidate * Strong full-stack web development experience * Experience building social or community platforms * Strong UI/UX instincts * Experience with authentication and secure systems * Comfortable building privacy-first products * Strong communication and fast execution mindset * Product/design thinking is a plus Bonus if you have experience with: * Anonymous social platforms * Mental wellness or student-facing products * Recommendation systems * Data visualization dashboards --- Deliverables * Functional high-fidelity MVP/prototype * Clean, documented codebase * GitHub repository handoff * Deployed staging/testing environment --- To Apply Please include: 1. Relevant portfolio/projects 2. Recommended tech stack for this build 3. Estimated timeline 4. Estimated budget range 5. Your approach to: * Anonymous posting architecture * Diary + mood tracking system * Personalized recommendation system 6. Any suggestions or improvements based on your experience We are aiming to move quickly and begin development ASAP.