01
Application ownership for an event-booking MVP
Concurrent role · MVP v1 under development
I lead application architecture and development across TheEventa's Next.js frontend, NestJS backend, internal admin panel and Playwright E2E project.
Outcome: Most of the MVP is built (authentication and SSO, organizations, event spaces, pricing, calendar and reservations) by a deliberately small team working with AI agents.
- Lead development spanning authentication and SSO, event objects and their related spaces, organizations, image management, and pricing that recalculates as selected options change.
- Own frontend wizard forms, the frontend design system and Storybook, alongside the landing page and blog.
- Review code, feature implementations, and manual and automated tests, with personal oversight of agent-assisted workflows.
Technologies: Next.js, NestJS, TypeScript, Playwright, Storybook
Application ownership for an event-booking MVP: Scope and approach
- Agent-assisted workflows cover design preparation, implementation, and review of code, design, business analysis, and architecture.
- Infrastructure, monitoring, and server administration are handled by a separate DevOps collaborator.
Read the case study about One tech lead, AI agents and an MVP rebuilt from almost zero
