This is an update to my last job post. Based on additional consultations, I’ve fine-tuned the solicitation in hope of having more fulsome and refined responses. I hope to schedule interviews with the top three candidates by week’s end
Real-Time Collaboration Required (6–9pm EST overlap)
I am building a governance-driven introductions platform (ages 22–29) on Bubble and seeking a senior Bubble product builder to lead a structured UX definition sprint and implement directly in Bubble.
This is not a design-only role.
This is not a Figma handoff project.
You must be able to define flows and implement them in Bubble.
Collaboration Requirements
• Must be available for live collaboration between 6–9pm EST at least 2–3 days per week
• Available for weekly live video working sessions
• Strong verbal English fluency required
You do NOT need to be U.S.-based.
However, strong familiarity with U.S. cultural norms, communication styles, and family dynamics is essential. This product initially serves U.S. families — cultural nuance and tone sensitivity matter.
Product Overview
This is NOT a swipe-based dating app.
It is a structured, governance-driven system including:
• Household accounts
• Role-based permissions (Platform Admin / Household Admin / Young Adult)
• Big Five (OCEAN) personality onboarding
• Rule-based compatibility filtering
• AI-assisted compatibility summaries (admin-facing only)
• Human review before match delivery
• Bilateral approval before messaging unlock
• Stripe subscription integration
Trust, structure, and clarity are core product values.
The application will be built in Bubble, with some system components (data storage and/or logic) handled through an external backend service (likely Supabase) via API.
Engagement Structure
Phase 1 – UX Definition & Architecture Sprint (Approx. 2 Weeks)
You will:
• Translate founder vision into structured user journeys
• Define onboarding psychology and flow logic
• Map role-based permissions and match lifecycle states
• Identify trust moments and friction points
• Produce low-fidelity wireframes
• Define a clean data model for a multi-role household system
Deliverables:
• Flow diagrams
• Screen map
• Clickable wireframes (low fidelity)
• Defined MVP scope freeze
• Initial data architecture outline
Phase 1 budget: $3,000
Phase 2 – Implementation (Milestone-Based)
• Implement approved flows directly in Bubble
• Build mobile-first responsive layouts
• Integrate external APIs where required (payments, messaging, backend services)
• Validate governance logic
• Conduct usability refinement
• Prepare for beta readiness
Phase 2 budget: $9,000–$12,000 (milestone-based)
Total Contract Value: $12,000–$15,000
Technical Expectations
The developer should be comfortable with:
• Connecting Bubble to external APIs or backend services
• Structuring relational data models for multi-role systems
• Managing Bubble performance and workload unit efficiency
• Minimizing unnecessary plugin dependencies
• Using Bubble staging/versioning practices responsibly
Experience integrating with services such as:
• Stripe
• Twilio
• External APIs / backend platforms (Supabase, Xano, Firebase, etc.)
is strongly preferred.
The system should be structured and documented clearly enough that basic troubleshooting can occur without heavy developer dependency.
Documentation should include:
• core data model
• API integrations
• key workflows and state transitions
Ideal Experience
• Senior-level Bubble product builds (not junior execution)
• SaaS / marketplace UX
• State-based systems
• Admin dashboards
• Experience translating abstract founder vision into structured UX
• Experience building for U.S.-based users
• Experience building two-sided or trust-based platforms is strongly preferred
To Be Considered, Please Include:
· Your timezone
· Confirmation of availability during 6–9pm EST
2 live Bubble apps you personally implemented (links)
A brief example of how you improved a product’s user flow beyond the original founder request
Experience designing for U.S. family, trust-based, or governance-adjacent audiences
If applicable, please include examples of Bubble apps integrating external APIs or backend services.
Architecture Questions (Required)
1. Household System Design
Briefly describe how you would structure a multi-role household account in Bubble where one household contains both:
• a Parent (Household Admin)
• a Young Adult (Member)
Each role should have different views and permissions, with data connected to an external backend database via API.
2. State-Based Workflow Design
Briefly describe how you typically manage state-based workflows in Bubble.
Example lifecycle:
pending approval → approved → match delivered → messaging unlocked
3. Match Visibility Logic (Quick Architecture Prompt)
In 2–3 sentences, describe how you would prevent young adults from seeing a match until both households approve the introduction.
Optional
A short Loom video (under 3 minutes) walking through one of your submitted apps is welcome.
This helps demonstrate communication style and your role in the build.
Application Note
To confirm that you’ve read this post carefully, please begin your response with the phrase:
“Household-first architecture.”
Proposals that do not include this phrase may not be considered.
Ideal Candidate
You are someone who:
• Thinks like a product builder, not just a coder
• Can simplify UX to reduce development complexity
• Understands relational data architecture early in a project
• Has built real Bubble apps with external integrations
