Part-Time Full-Stack Engineer — Own a Live, Growing Web App | Long-Term

We’re looking for a Full-Stack Engineer who actually enjoys owning a product after it ships, not just building features, merging a PR, and disappearing into the internet. Our web app is already live, already has paying/active users, and is continuing to grow. The foundation is there. What we need now is an experienced engineer who can learn the existing system, keep it healthy, solve the weird problems that inevitably show up in production, and help us scale without turning the codebase into a haunted house six months from now. We also work a little differently. Our development process is heavily AI-assisted. We use Claude along with a dedicated AI engineering agent that helps monitor the application, troubleshoot issues, and handle development work. We’re not looking for someone who feels threatened by that, or someone who blindly accepts whatever the AI spits out because “the tests passed.” We want the human in the loop who knows when the AI is right, when it’s confidently wrong, and when a problem needs actual engineering judgment. The Current Stack You’ll be working with: Supabase — database, authentication, and backend services Railway — deployment and production infrastructure Claude + AI engineering tools — development, debugging, and monitoring Whop — plus other third-party APIs and integrations A live production application with real users and real-world edge cases What You’ll Own You’ll become the technical owner and escalation point for the application. That means keeping production stable, investigating bugs, handling customer-reported technical issues, and stepping in when our AI engineering agent hits something it can’t reliably solve. You’ll review AI-generated code when needed, trace issues across the frontend, backend, database, authentication, APIs, and third-party integrations, and implement new features and improvements as the product evolves. We also want someone proactive enough to spot smoke before the kitchen is on fire. That includes monitoring performance and reliability, improving logging and observability, tightening testing and deployment processes, reviewing security and data integrity, checking backups and recovery processes, cleaning up technical debt, and recommending architecture changes when the current setup starts reaching its limits. Just as importantly, you should be able to explain what’s happening to a non-technical founder without requiring a 47-slide architecture deck. You’ll Probably Be a Great Fit If You... Have strong full-stack experience and have maintained real production applications with real users, not just demos or side projects. You should be comfortable jumping into an unfamiliar codebase and figuring out how the pieces connect without needing everything explained line by line. Strong experience with Supabase, SQL/databases, APIs, authentication, third-party integrations, deployments, debugging, and production troubleshooting is important. Experience with Railway is a big plus, although experience running applications on similar cloud platforms translates well. You should also be comfortable working with AI development tools such as Claude, Cursor, GitHub Copilot, or similar tools. The important part isn’t simply knowing how to prompt them. We want someone capable of reviewing AI-generated code critically, catching bad assumptions, identifying security or scalability problems, and deciding what should—and absolutely should not—make it into production. Experience with SaaS products, membership platforms, customer-facing applications, or startup environments is especially useful. Strong English communication matters too. You’ll be working directly with a non-technical founder, so being able to turn “something weird happens when customers do X” into a root cause and sensible solution is part of the job. Hours & Compensation This will start at approximately 20-30 hours per week, at $70-$90 USD/hour, with the intention of building a long-term working relationship. Most normal weeks will probably be closer to five hours. When we’re shipping a larger feature, improving infrastructure, or chasing down an especially stubborn production gremlin, additional hours will be available. We’re particularly interested in engineers based in Latin America because U.S. time-zone overlap makes collaboration easier, but location isn’t a hard requirement. If you’re excellent, reliable, and communicate well, we’re happy to hear from you wherever you’re based. As the product and customer base grow, there’s plenty of room for the role—and the number of hours—to grow with it. When You Apply Please keep it straightforward. Tell us about one live production application you’ve maintained or taken technical ownership of, what the stack looked like, and one difficult production issue you personally diagnosed and solved. Also tell us about your experience with Supabase/Railway and how you currently use Claude, Cursor, Copilot, or other AI coding tools in your development workflow. No need for a novel. We’d much rather hear about a messy production problem you actually solved than read another paragraph about being a “results-driven technology professional.”