Technical User Support Intern

About Readdy

\n

\n

Readdy is an AI website builder that turns a conversation into a live, working website — pages, forms, bookings, payments, and custom domains included. Tens of thousands of freelancers, agencies, and small business owners sign up every month, and our community is where they come when something breaks or they get stuck.

\n

\n

That means when a US user hits a problem at 2pm Pacific, they currently wait overnight for an answer. Your job is to close that gap.

\n

\n

What you'll do

\n

\n

• \n
• Be the first responder for technical questions in our user community (Discord, social channels, and support inbox) during US hours — most questions get a real answer from you, not a "we'll look into it"
• \n
• Troubleshoot the issues our users actually hit, including:
• \n
• Custom domain and DNS setup (A/CNAME records across GoDaddy, Namecheap, Cloudflare, etc.), SSL, and propagation issues
• \n
• Forms and bookings: submissions not arriving, notifications not firing, connecting to email/CRM
• \n
• Third-party scripts on published sites: Google Analytics, GTM, pixels, embeds, and the CSP issues that block them
• \n
• Publish failures, broken images, social preview cards, and "where did my site go" panics
• \n
• Database-backed features (Supabase) — auth, data not saving, API errors
• \n
• Hop on calls with users when async back-and-forth isn't cutting it: screen-share, debug the problem live, and either fix it on the spot or walk away with everything engineering needs to fix it
• \n
• Reproduce real bugs and write clean handoff reports for the engineering team (steps to reproduce, expected vs. actual, screenshots/console logs) so they can fix things during their day without a second round of back-and-forth
• \n
• Turn recurring questions into reusable answers: FAQ entries, help doc drafts, and short troubleshooting guides
• \n
• Flag patterns: if 10 people hit the same wall this week, we want to know it's a problem, not 10 support tickets
• \n
• Support our biweekly live webinar (Readdy Live) — field technical questions in the chat during the session, help run the live Q&A, and follow up afterward with attendees whose problems need a deeper look
• \n

\n

\n

What we're looking for

\n

\n

• \n
• You understand how websites actually work: DNS, hosting, what happens between "publish" and "live on my domain"
• \n
• Comfortable in browser dev tools — you can read a console error and a network tab and form a hypothesis
• \n
• Working knowledge of HTML/CSS/JS. You don't need to be a developer, but you need to not be afraid of code
• \n
• You write clearly. Most of this job is explaining technical things to non-technical people without making them feel dumb
• \n
• Comfortable on camera and on calls — you can debug live with a stressed user watching your screen and keep them calm while you work
• \n
• Self-directed: you'll often be the only Readdy person awake, and you're comfortable making the call on "I can solve this now" vs. "this needs engineering"
• \n
• Available during US business hours (any US timezone)
• \n

\n

\n

Nice to have

\n

\n

• \n
• Hands-on experience with Supabase, or any backend-as-a-service
• \n
• You've used AI website builders or no-code tools (Readdy, Framer, Webflow, v0, Lovable, any of them)
• \n
• Experience moderating or supporting an online community
• \n
• Mandarin Chinese (our engineering team works in Chinese — helpful for handoffs, not required)
• \n
• Based in the SF Bay Area and able to meet in person 2–3 times a week, we occasionally do on-site work together (user meetups, content shoots, working sessions)
• \n

\n

\n

Details

\n

\n

• \n
• Located in the Bay Area (Close to Palo Alto).
• \n
• Flexible schedule within US business hours; exact hours/week to be agreed
• \n
• You'll work directly with our Community Manager and have a direct line to the founding engineering team
• \n
• Strong performers will help shape our support playbook from scratch: this role is the first of its kind at Readdy
• \n

\n