Ask Kanaan

Product-minded frontend work, with AI where it actually helps.

I build practical web apps with clean React interfaces, thoughtful user flows, and real project context: sports insights, marketplace booking, and AI-assisted health tracking.

The AI assistant acts as a grounded portfolio guide for recruiters, clients, and anyone allergic to opening six tabs just to answer one question.

Portfolio AI

Grounded in resume, project notes, and actual portfolio context.

Ask Kanaan

Ask about projects, product thinking, AI work, fit, or the occasional personal curveball. I will keep it useful and grounded.

Concise by default. Professional when it matters. A little warmer when you ask.

Who this helps

Built for the people doing the real evaluation.

Recruiters get a quick fit check. Clients get signal on product judgment and execution. Collaborators get a sense of how I work, not just what stack I used.

Recruiters

Get the fast read on fit, project depth, and how I think about frontend product work.

Clients

See how I approach useful workflows, clear execution, and the details that make software feel trustworthy.

Collaborators

Understand my working style, what I care about, and where I add the most value on a team.

Curious visitors

Ask the practical question, the unexpected one, or both. The assistant has range. Within reason.

Featured Projects

Real apps with product decisions behind them.

Start with the three projects that best show practical AI integration, user workflow thinking, and deployed frontend work.

View all projects
Quick reads

Prefer skimming to chatting? Sensible.

These cover the questions people usually ask before they open LinkedIn, schedule a call, or test the robot with something unexpected.

Read the full FAQ

What kind of work fits you best?

Frontend or full-stack product work where clean UI, practical systems, and user experience all matter. I am especially interested in junior or internship roles where I can build real features, learn quickly, and contribute to polished user-facing products.

What stands out about how you build?

I care about whether the product is actually useful, not just whether the feature technically exists. That shows up in clearer hierarchy, thoughtful flows, practical AI integration, and fewer rough edges between the idea and the real user experience.

How do you approach projects?

I start with the user workflow, choose a stack that fits the scope, then refine the interface and implementation until the product feels intentional. I try to keep the architecture simple enough to maintain and the UX clear enough to trust.

Open to the right work

If the answers sound right and the work backs them up, let's talk.

I am especially interested in internships, junior frontend roles, and product-focused teams that care about clear communication, useful UX, and shipping work that feels finished.