Sessions

Produce a PRD for a content moderation system for a small online community platform with 500-2000 members.

Write a post-mortem for a production outage on a small SaaS platform. The outage lasted 4 hours, affected approximately 200 active users, and was caused by a database migration that passed staging tests but failed in production due to a data pattern that didn't exist in the staging environment. Two engineers were on call. One was on their second week at the company. The root cause was identified and resolved, but not before several users lost unsaved work. Write the post-mortem as an internal document the team will actually use.

Build a simple notification preferences system for a web app. Users should be able to subscribe to different notification types (email, in-app, SMS), set quiet hours during which no notifications are delivered, and have a single "mute all" toggle. Write the database schema, the API endpoints, and a brief implementation plan. Use PostgreSQL and a REST API. Keep it simple — this is for a team of two developers.

A mid-size accounting firm (40 employees) is losing junior staff at twice the industry average. Exit interviews cite three recurring themes: unclear promotion criteria, a perception that senior partners don't invest in mentorship, and compensation that is competitive at hire but falls behind within 18 months. The managing partner has asked you to write a retention strategy. The firm's annual budget for new initiatives is $50,000. Write the strategy as an internal document the partners will actually discuss at their next quarterly meeting.

Write documentation for a REST API endpoint that handles user account deletion. The endpoint is DELETE /api/v1/users/{user_id}. It requires admin authentication via Bearer token. It performs a soft delete (sets deleted_at timestamp, anonymizes PII, retains the record for 90 days before hard delete). It returns 200 on success, 401 if unauthorized, 403 if the requesting admin doesn't have delete permissions, 404 if the user doesn't exist, and 409 if the user has active subscriptions that must be cancelled first. Write the documentation as it would appear in the API reference, including request/response examples.

A user purchases a one-year subscription ($249) to a small SaaS product. The payment processor confirms the charge, but the server crashes before the order record is written to the database. The user sees a blank page. They check their bank account and see the charge. They have no confirmation email and no account access. The support team is two people. Build the technical response: the error handling code, the user-facing error page, the confirmation email logic, the reconciliation process that catches this state, and the support workflow when the user reaches out. Write it in Python as working code with comments. Structure the response however you think best serves the problem.

A user registers for a small B2B platform. The form collects their name, work email, phone, company, and a password. They click "Create Account." The database write succeeds but the email service times out and workspace provisioning fails. They never receive a welcome email. When they try to log in: "Account not found." When they try to register again: "Email already in use." Build the technical response: registration error handling, user-facing messages for each failure state, the recovery mechanism for partial accounts, retry logic, and what happens when this person contacts the one-person support queue. Write it in Python as working code with comments. Structure the response however you think best serves the problem.