Vet a Base44 developer in 32 verifiable steps across five categories: portfolio verification, platform-specific knowledge probes, code-sample review, reference checks, and contractual readiness. The full checklist takes 60-90 minutes per finalist and screens out generalists before you sign a contract. Skipping it is the fastest path to a $1,500 sprint that ships nothing — and the cheapest path back is ordering a $497 audit from a different vendor for independent verification. Compiled by the lead engineer at Base44Devs.
Why this matters
The base44 hiring market is filled with marketplace listings claiming senior expertise on a young platform. Without a structured vetting process, you will sign a contract with a generalist charging specialist rates and discover the gap at week two. The 32-point checklist below is the verification battery we run on every Base44Devs hire and recommend to teams hiring elsewhere. The alternative to running this loop yourself is hiring a vetted Base44 team.
Who this is for
- Hiring managers screening freelance or contract base44 developers
- Founders who got burned by a previous hire and need a structured next round
- Procurement teams writing a vendor evaluation rubric
- Technical leads making the final hire/no-hire call after recruiter screening
- Operators running a final round on candidates that already cleared a recruiter screen
How to use this checklist
Print it. Run through it in order. A candidate must clear all 32 items at the "must-have" level to be hireable. "Nice-to-have" items are differentiators between two candidates who both clear the must-haves. If a candidate fails three or more must-haves, walk away — they are not the right fit at any price. The walk-away red flags for Base44 hires cover what each failure mode tells you.
Section A — portfolio verification (items 1-7)
The candidate must produce evidence of base44 work. "I have worked on base44 projects" without artifacts is not evidence.
- Live URL of a base44 app shipped in the last 12 months. Must-have. Must be publicly accessible or accessible via a credential the candidate provides for the call. Screenshots are not URLs.
- A second live URL. Must-have. One app is luck; two is a pattern.
- GitHub or repository access for one shipped app. Must-have for any engagement over $3,000. Read-only access is acceptable. "I cannot share the code, it is under NDA" is acceptable for one app, not all of them.
- A LinkedIn profile with consistent dates. Must-have. Profile dates must match the candidate's claims. Gaps and inconsistencies are red flags.
- A portfolio site or case study. Nice-to-have. The case study quality is the diagnostic — vague before/after screenshots without architecture or scope context are a tell.
- A non-base44 portfolio piece. Nice-to-have. Demonstrates the candidate has shipped beyond one platform, which matters for migration work.
- Public blog posts, talks, or open-source contributions on base44. Nice-to-have, but a strong differentiator. Engineers who teach in public know more than engineers who only do client work.
Section B — platform-specific knowledge interview (items 8-15)
A 30-minute interview covering documented base44 failure modes. The candidate should answer unprompted with specifics, not generalities — this section is where you do most of the work of telling a true Base44 specialist from a general dev.
- Describe the function-routing 404 failure mode. Must-have. Specialist answer references the routing fix. Generalist answer is "I would check the logs."
- Describe credit-burn loops on the platform. Must-have. Specialist references AI-agent re-prompting and loop detection. Generalist has not heard of credit-burn.
- Describe the July 2025 SSO bypass. Must-have. Specialist references Wiz's disclosure and the registration-vs-login path divergence. Generalist has no recollection.
- Describe AI-agent regression patterns. Must-have. Specialist describes how prompt drift breaks shipped features.
- Describe a Stripe-integration failure mode after a platform update. Nice-to-have. Specialist describes the webhook-signature drift pattern.
- Describe rate-limiting behavior on base44 functions. Nice-to-have. Specialist knows the per-app and per-user limits.
- Describe data-export options off the platform. Nice-to-have, critical if migration is a future possibility.
- Describe at least one platform-update breakage they personally fixed. Must-have. Specialist has a story; generalist does not.
Section C — code samples (items 16-22)
A short review of one code sample the candidate provides.
- Code is provided unprompted. Must-have. A senior candidate volunteers a sample without being asked.
- Code includes error handling, not just happy-path. Must-have. Look for try/catch, validation, edge-case checks.
- Code includes tests or a regression note. Nice-to-have for freelance, must-have for production work.
- Naming and structure are consistent. Must-have. Inconsistent naming is the leading indicator of inconsistent thinking.
- Comments explain why, not what. Nice-to-have. Diagnostic of seniority.
- No obvious anti-patterns. Must-have. Hardcoded credentials, plaintext PII, unsanitized SQL — any of these and you walk.
- Candidate can explain the code in their own words. Must-have. Engineers who cannot explain their own code did not write it.
Section D — references (items 23-28)
Two reference checks, 15-20 minutes each.
- Reference is reachable. Must-have. If the email bounces or the LinkedIn does not match, the reference is fabricated.
- Reference confirms the engagement happened. Must-have. Date range, scope, and deliverables match the candidate's claims.
- Reference confirms the candidate shipped on time. Must-have. "Delivered late" is acceptable if the reference explains why and the candidate's account matches.
- Reference confirms low rework rate. Must-have. "We had to redo most of the work" disqualifies regardless of the candidate's story.
- Reference would hire the candidate again. Must-have. Vague "they were fine" answers are red flags. Specifics or a clean "yes" pass.
- Reference offers a third reference unprompted. Nice-to-have. Strong differentiator. References who recommend other references are signaling confidence.
Section E — contractual readiness (items 29-32)
The final five-minute check before the SOW.
- Will sign a mutual NDA. Must-have. Refusal is a walk-away.
- Will provide a written SOW with milestones. Must-have for engagements over $1,500. See the SOW structure for a Base44 contract.
- IP assignment on payment, not on delivery. Must-have. Non-negotiable for production work.
- 30-day or shorter notice period in any retainer clause. Must-have for agency-shaped work.
Trade-offs and pitfalls
The first pitfall is skipping platform-knowledge probes because they feel adversarial. They are. That is the point. A candidate who gets defensive when asked to describe credit-burn is signaling they cannot describe it. The interview is a filter; if it does not filter anyone, it is not working.
The second pitfall is over-weighting portfolio polish. A candidate with a beautiful portfolio site and no platform-knowledge depth is selling design, not engineering. Conversely, a candidate with a sparse portfolio but who can describe four documented platform failure modes unprompted is shipping more than the polished candidate.
The third pitfall is one-reference vetting. One reference is curated. Two is verified. Always insist on two.
How Base44Devs fits in
Base44Devs runs this checklist against every internal hire. We also publish the longer-form vetting guide for teams hiring elsewhere. If you want to skip the hiring loop entirely, order a $497 audit — you get senior platform expertise without running an in-house hiring cycle.
Related options
- 12 red flags when hiring a base44 developer — what each checklist failure tells you
- Hire a base44 freelancer — engagement structure once vetting is clear
- Base44 developer JD template — the role spec that drives the checklist