Prep RoomSign inStart free
Code RoomRegistration validation global names
HardPrep Room Coding #4455

Registration validation global names

Vibe & agenticAlgorithms & data structuresMid–Senior~17 min

You asked an AI agent to 'add validation to the user registration form' for a global SaaS product. It returned regexes that reject names with non-letters, require a two-part name, validate emails against a strict pattern, and require phone numbers in a US format. The tests pass. What's wrong with these 'sensible' defaults, and who gets locked out?

Implement
check_registration_field(field_kind: str, value: str) → str
Examples
in["name","O'Brien"]out"ok"
in["email","ada+news@example.co.uk"]out"ok"
in["phone","+91 98765 43210"]out"ok"
What a strong answer looks like

Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it (tests, edge cases, reading critically), and how you’d re-prompt or decompose to get it right.

0:00 of about 17 min

Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.

Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.