Claro helps experienced professionals see where they fit
I created Claro to help people with complex career histories understand how their experience connects to a specific role. I led the product strategy, brand, design, and iteration, using AI to turn those decisions into a working application.
My role:
Product strategy, brand, UX/UI, and AI implementation direction
Timeline:
2025–2026 · Ongoing
Stack:
Next.js · Supabase · Claude API · Vercel
Live product:
claroapp.co
My Jobs brings saved opportunities into one view, with a profile match score, recommendation, and a brief for each role.
It started with one person's search
My wife had a strong background and was applying to jobs without hearing back. The difficult part was knowing what to change. Which roles made sense for her? What experience should she lead with? What might a hiring team need her to explain?
Her career spanned several kinds of work. The experience was there, but the connection to a particular opening wasn't always obvious. Job boards gave her more listings. Generic AI advice left her with much of the same translation work.
I started Claro around that problem: helping someone make sense of their experience in the context of a real opportunity.
The central question became: what does this role need, and what in your background supports it?
Build the product around a decision
That question gave Claro its focus. Add a resume, compare it with a job description, and get a clear view of the match. Then use that assessment to decide what to emphasize and how to approach the application.
The profile gives users a starting point: strengths, role suggestions, and details worth clarifying. Each job gets a profile match score with supporting reasons and a recommendation to Pursue, Consider, or treat it as Lower priority.
The application brief connects that assessment to the next step. It brings together relevant experience, requirements to review, a question to prepare for, and suggested framing. Users can draft email or LinkedIn outreach, get resume suggestions, and copy or email the brief into their own workflow.
Every output earns its place by helping with the same decision: is this opportunity worth pursuing, and how should I approach it?
The profile turns a saved resume into a clear summary of the user's experience—the starting point for assessing each opportunity.
Give every opportunity a workspace
The first version exposed the feature list in the navigation: My Jobs, Profile, Discover, Job Fit, and Prep. As the product grew, that structure asked users to understand the tools before they could use them.
I simplified the experience around two destinations: My Jobs and My Profile. A saved role opens its own brief, where the assessment and application guidance sit together. Users can review the match, add context, and prepare what to say without moving between separate tools.
The hierarchy follows the work. The recommendation and immediate next steps come first. Supporting score details expand when needed. Outreach and resume suggestions are generated when the user is ready for them.
The brief became the main workspace for a role.
The brief opens with the recommendation, its reasoning, and the next steps to consider before applying.
Farther down the same brief, relevant experience sits alongside requirements to review and a question the candidate should be ready to answer.
Make the assessment open to correction
A resume is an incomplete account of a person's experience. If it doesn't mention a skill, the product needs to leave room for the person to supply that context.
I built that distinction into the assessment: what the resume demonstrates, what it doesn't show, what needs clarification, and where there appears to be a genuine gap. Users can inspect the reasoning behind the score and the evidence attached to individual findings.
They can also add experience or correct a detail. Claro uses the accumulated context to reassess the role and update the brief. The score can move in either direction, depending on the evidence. If an existing outreach draft or resume suggestion needs refreshing, the interface flags it.
The language became more precise, too. “Profile match” describes what the score measures. “Requirements to review” gives users something to investigate. A question a hiring team might raise becomes something to prepare for. The page states that the assessment doesn't predict whether someone will get an interview.
Those choices define how much authority the product should have, and where the user needs to stay in control.
Users can add experience their resume leaves out and ask Claro to reconsider the assessment with that context.
A visual identity that evolved with the product
Claro means “clear” in Spanish. That idea shaped the name, the writing, and the interface: make the important information easy to find and the next action easy to understand.
The visual system went through several versions. An early editorial direction used warm off-white surfaces and serif typography. A later version introduced a stricter geometric system, a dark navy landing page, and a white working interface.
The current design keeps the navy foundation and clear hierarchy, pairing Google Sans Flex interface type with serif summaries, softer surfaces, and subtle warm color. The job list uses a table for comparison. The brief gives longer analysis room to breathe. Muted status colors carry the recommendation without dominating the page.
Earlier: five sidebar destinations and separate job cards reflected the growing feature set.
Current: two main destinations, a table for comparing roles, and direct access to each job's brief.
Direct the build, then question the result
I used AI to move quickly from decisions to working product, but I didn't treat the output as the answer. Once something worked, I stepped back and asked whether it was actually the right solution.
Early design exploration: comparing dark and light versions of the same layout made the surface direction easier to evaluate.
Some of the most consequential decisions were small. Analysis addresses the user as “you”; sendable drafts use “I.” A writing sample helps calibrate the voice. Resume suggestions have explicit instructions against inventing metrics. The brief and its drafts use the established assessment so that later outputs have the same starting point.
The work kept moving between strategy and detail: deciding what Claro should do, using it, finding where it fell short, and changing the system behind that behavior.
What real use changed
Early feedback made the product more focused. Showing seven preparation tools at once felt overwhelming. I first organized them by application stage, then continued simplifying toward the current brief for each role.
The email brief came from a practical need: the guidance had to be available where the user was actually writing. Feedback also exposed invented numbers in suggested resume bullets, which led to explicit prompt guardrails against fabricated metrics.
Claro is live, and early testing has produced specific changes to the workflow and output. One early tester said she'd pay for it. That is an encouraging signal; willingness to pay and repeat use across a wider range of professionals still need validation.
The roadmap now comes from what people actually do, not what I imagined they might need.