Questions to Ask Before Hiring Any Bubble Developer
Most Bubble developers cannot answer these questions. Architects can. Twelve technical questions that reveal in 20 minutes whether the person in front of you can architect a production SaaS — or just use the Bubble editor.
Most Bubble Developers Cannot Answer These Questions — Architects Can
We are often brought in after a client has already paid a developer who could not deliver what was promised. The developer built something that looked right but was architecturally broken: insecure, slow, or impossible to extend. These questions, asked before any contract is signed, reveal within 20 minutes whether the person in front of you is a Bubble user or a Bubble architect.
Twelve Questions That Separate Architects from Developers
How do you implement multi-tenant data isolation in Bubble?
Expected: Workspace data type, workspace field on every type, privacy rules checking membership, all searches scoped to current_workspace. Red flag: mentions UI-level hiding, page redirects, or ‘depends on the project.’ There is only one correct architectural answer to this question.
What is the difference between :filtered by and a search constraint, and which do you use?
Expected: Search constraints translate to SQL WHERE clauses (server-side, fast, scales). :filtered by loads all records client-side and filters in JavaScript (slow, breaks at scale, never acceptable in production). Red flag: uses them interchangeably or ‘chooses based on the situation.’
How do you handle Stripe subscription status updates?
Expected: Backend API workflow exposed as webhook endpoint, receives all 6 webhook events, validates workspace_id from metadata, updates Workspace billing fields. Never from redirect URL. Red flag: ‘I update status on the success page redirect’ or unfamiliarity with webhooks.
Where do you store user roles and how do you enforce them?
Expected: Role as Option Set on Membership record scoped to workspace. Privacy rules check membership role. Step 1 of sensitive workflows has Only when condition. Red flag: ‘I put the role on the User record’ or ‘I check on the page whether they are admin.’
How do you build a performant dashboard that stays fast as data grows?
Expected: Denormalised counters on Workspace updated by workflows. Dashboard reads stored numbers, not live counts. No :filtered by anywhere. Pre-loading states via page load workflow. Red flag: ‘I just search for everything on the dashboard’ or confusion about the question.
Show me a live Bubble application you built that has paying customers.
Expected: A live URL, a walk-through of the architecture, real users, real data, custom domain. Red flag: prototype, internal tool, personal project, or ‘I cannot share client work’ without offering any verifiable alternative evidence.
What happens to your app data when a Stripe subscription is cancelled?
Expected: subscription.deleted webhook sets status to Cancelled, data preserved, app goes read-only, reactivation prompt shown. Never delete data. Red flag: ‘I delete the workspace data’ or ‘nothing, we just stop the subscription.’
How do you prevent Workload Unit overages in a production app?
Expected: Minimise workflow steps, batch DB operations, use Option Sets for static data, avoid unnecessary API calls, use scheduled workflows for aggregation instead of real-time counts. Red flag: unfamiliarity with Workload Units or ‘I never think about that.’
What is your branching and deployment process?
Expected: All development in development branch. Never edit live directly. Pre-deployment checklist. Smoke test immediately post-deployment. Red flag: ‘I just build in the live app’ or no defined process.
How do you document the apps you build?
Expected: Architecture document, workflow dictionary, data model diagram, API integration notes, deployment guide, handover session. Red flag: ‘The client can ask me if they have questions’ or ‘I don’t really do documentation.’
Describe how you would architect a referral programme in Bubble.
Expected: referral_code on User generated at signup, Referral data type, workspace creation checks URL param for referral code, creates Referral record, checkout.completed webhook rewards referrer. Red flag: incomplete or demonstrates unfamiliarity with webhook-based event sourcing.
What privacy rule would you write for an audit log data type?
Expected: Allow Find and View for workspace members. Deny Edit and Delete for everyone including admins. This makes the audit trail architecturally immutable. Red flag: ‘I would allow admin to edit it’ or any answer that permits modification of audit records.
Work With a Bubble Architect
Most developers build Bubble apps. We architect them. Data models designed for scale, multi-tenant security built from day one, Stripe billing that never fails, and workflows engineered for performance. This is what a Bubble Architect delivers.
