Project 03 · Full-Stack · FastAPI · Claude API
Simployee —
AI Job Simulation Platform
A full-stack web app where candidates practice real work tasks at a fictional company, evaluated by an AI manager. Built with FastAPI, Supabase, DuckDB, and the Anthropic Claude API. Deployed on Railway and GitHub Pages.
App Preview
In-App View — Progress Dashboard
Project Highlights
Highlight 01
AI-Powered Job Simulation
Claude generates realistic weekly tasks and evaluates candidate submissions as a virtual
manager named Sophie Chen — providing structured feedback that mirrors a real workplace
performance review.
Highlight 02
Full-Stack Production App
FastAPI backend deployed on Railway, PostgreSQL database on Supabase, and a vanilla
HTML/CSS/JS frontend served via GitHub Pages. JWT authentication, environment-based config,
and a clean REST API surface throughout.
Highlight 03
In-Platform SQL Runner
Users run queries directly against real NovaRetail datasets using DuckDB embedded in the
backend — simulating the kind of ad-hoc data work a junior analyst would do on the job,
without leaving the platform.
How It Was Built
Requirements
Defined the core simulation loop: task generation, submission, AI evaluation, and feedback display. Mapped out user roles, auth flow, and the fictional NovaRetail company context.
Supabase Schema Design
Designed the PostgreSQL schema on Supabase — users, tasks, submissions, and evaluations tables. Schema-first approach so the API contract was clear before writing a single endpoint.
FastAPI Backend
Built REST endpoints for auth (JWT), task management, submission handling, and the DuckDB SQL runner. Deployed to Railway with environment variable configuration for secrets.
Claude API Integration
Integrated the Anthropic Claude API to power Sophie Chen — generating contextual weekly tasks and evaluating submissions with structured scoring and written feedback.
HTML/CSS/JS Frontend
Built the frontend in vanilla HTML, CSS, and JavaScript — no framework dependencies. Designed around the same dark-theme system used across this portfolio.
GitHub Pages + Railway Deploy
Frontend served statically via GitHub Pages; backend runs as a persistent Railway service. Both environments use separate config and point to the production Supabase instance.