JOIN WORKERS

Founder

I designed and built Join Workers from scratch — a privacy-first professional community platform connecting people across industries with peer discussion, workplace news, and career resources.

As a solo founder, I owned every layer: product strategy, UX design, frontend and backend engineering, infrastructure, and deployment. The project gave me end-to-end experience shipping a production application where every decision — from authentication flow to data architecture — was mine to make and justify.


What I Built

The platform is a full-stack React/Node.js application with a PostgreSQL database, Redis caching, and AI-powered features, deployed on DigitalOcean.

The core product includes daily AI-generated news briefings, discussion forums organized by industry, direct messaging, a professional directory, and community moderation tools — roughly 150+ components, 30 API route files, and full mobile/desktop parity.

Key Design & Architecture Decisions

- Privacy as a product decision, not just a feature. I designed the platform around data minimization from day one — no IP logging, no analytics tracking, no third-party scripts. I built a custom analytics system that tracks aggregate patterns without capturing individual user behavior. This wasn't just an engineering constraint; it shaped the entire UX. Every feature had to earn the data it collected.

- Email-first authentication. I designed a single-entry-point auth flow where one input determines whether a user is signing in or registering. This reduced friction for new users while keeping the codebase simple — one flow instead of two parallel paths to maintain.

- Non-blocking AI briefing generation. The daily news briefings use Claude's API to ingest articles from multiple sources, analyze trends against BLS economic data, and produce editorial-quality summaries. The design challenge was latency: AI generation takes 30+ seconds, so I built the API to read from cache only, return a loading state if cold, and generate in the background. The frontend polls with localStorage caching. Users never wait.

Technical Stack

Frontend: React 18, Vite, Tailwind CSS, Framer Motion. Lazy-loaded routes, scroll-aware navigation, animated UI.

Backend: Node.js/Express REST API, PostgreSQL, Redis/Bull job queues. Magic link authentication, rate limiting, content moderation pipeline.

Infrastructure: DigitalOcean App Platform with staging environment, Cloudflare CDN, Twilio SMS integration, Telegram bot for anonymous community tips.

Security: bcrypt hashing, JWT auth with magic link fallback, Twilio signature validation, rate limiting on all auth endpoints, content quality filtering, API spend caps.

What I Took Away

Building a product solo — from initial concept through production deployment — sharpened how I think about scope, sequencing, and tradeoffs. When you're responsible for both the design and the code, you learn quickly where to invest in polish and where to ship the simpler version. That instinct carries into every team environment I work in.

Next Project