Open to new work

Tech Lead & AI Product Engineer

I lead teams building software for healthcare and other regulated industries, where getting the details right really matters. Lately I've been bringing AI into those products with React, Next.js, and the Vercel AI SDK.

Remote · UTC-3 · overlapping US business hours

Fern frond in soft light — botanical photography by Lara Mateo
Bougainvillea blossoms against the sky — botanical photography by Lara Mateo
Lush green foliage — botanical photography by Lara Mateo
OPEN TO NEW WORK ✦ REMOTE · UTC-3 ✦

About meGrowing ideas into meaningful experiences

I'm a Tech Lead and AI Product Engineer with 6 years of experience, currently at Clarity RCM. I joined as a Senior Engineer and became Tech Lead about six months later, and I now lead a team of up to six. We build HIPAA-compliant healthcare software, an internal tool and a client-facing app, used by more than 200 medical practices. I like owning things end to end, from working out requirements and proposing designs to building them, keeping them fast, and spotting privacy and compliance issues before they reach users. I studied Software Engineering at the National Technological University of Argentina and before Clarity I built high-performance interfaces at ReflexAI, Mercado Libre, and GlobalLogic.

I care deeply about technology that includes everyone and doesn't compromise on privacy, and lately I've been drawn to figuring out where AI actually helps and where it just gets in the way. Outside of work I keep building things I believe in, like LLM-powered tools and an open-source Markdown editor.

ReactNext.jsTypeScriptNode.jsLLM IntegrationVercel AI SDKRAGPrompt EngineeringTechnical LeadershipObservability (Datadog)Web PerformanceSecurity / OWASP
  • Rooted in Buenos Aires
  • Shipping worldwide
  • React & Next.js
  • AI product engineering
  • Accessible by default
  • Open to new work

Case studiesSelected work

Some of the work I'm most proud of, with the problem, the constraints, and what I actually did about it.

Tech LeadHealthcare · Regulated

Catching a HIPAA risk before it shipped

I found a HIPAA compliance gap on a platform that handled health data for more than 200 medical practices, and led the work to re-architect around it.

200+
medical practices served
HIPAA
compliance safeguarded
1
risk caught & re-architected

Problem

The platform handled protected health information (PHI) for over 200 practices, and one of our architecture decisions meant we were handling that data in a way HIPAA doesn't allow. Nobody had caught it yet.

Constraints

There was no room for error with PHI, the system was already live with real practices depending on it, and the rest of the team was still shipping features. The fix couldn't slow everyone down.

What I did

  • Followed the data to find exactly where PHI was ending up where it shouldn't
  • Designed a focused re-architecture instead of a risky full rewrite
  • Planned the migration so live practices wouldn't feel it
  • Got product, engineering, and compliance on the same page about the trade-offs

Outcome

We closed the gap, and the approach we used became how the team handled PHI from then on.

Strategic considerations

The hard part wasn't really the code. It was noticing a risk no one else had flagged, then fixing it without stopping the roadmap or worrying 200+ customers. That kind of judgment is the part of security work I care about most.

HIPAASecurity / OWASPArchitectureHealthcareTechnical Leadership
Senior Engineer → Tech LeadHealthcare · Team leadership

Senior to Tech Lead in six months, and a team of six

I went from Senior Engineer to Tech Lead in about six months, then led a team of up to six building two healthcare products at the same time.

6
engineers led
~6 mo
Senior → Tech Lead
2
products shipped at once

Problem

We needed to ship an internal operations tool and a client-facing app at once, on a regulated platform where quality and compliance weren't negotiable.

Constraints

Two products, one team, and me learning how to lead while still writing a lot of the code myself.

What I did

  • Owned features from requirements and design all the way to shipping
  • Set up how the team handled code review, testing, and monitoring
  • Mentored the engineers and helped grow the team to six
  • Kept product and engineering on the same page about scope and trade-offs

Outcome

Both products shipped, the team grew, and I got the promotion based on what I delivered rather than how long I'd been there.

Strategic considerations

I hadn't been there long, but the promotion came from what I actually shipped. For me, leading meant being responsible for the whole outcome: the product, the compliance side, and a team that was still growing.

Technical LeadershipMentoringObservability (Datadog)CI/CDHealthcare
Senior Frontend EngineerLarge-scale web · Performance

High-performance interfaces at scale

I built and tuned interfaces for large products at ReflexAI, Mercado Libre, and GlobalLogic, focusing on Core Web Vitals, load time, and how fast things actually feel.

Faster
LCP, CLS & INP improved
In CI
perf budgets on every PR
Lighter
less JS, images & hydration

Problem

At that scale, performance really matters. Slow loads and weak Core Web Vitals quietly cost you engagement, conversions, and search ranking.

Constraints

Real production traffic, big shared codebases, and a lot of teams shipping at the same time.

What I did

  • Profiled and fixed the slow parts: bundle size, images, hydration
  • Improved Core Web Vitals across LCP, CLS, and INP
  • Built reusable, accessible components that stayed fast under load
  • Added performance checks so regressions got caught in CI

Outcome

Faster, more accessible interfaces, with Core Web Vitals improvements I could actually measure.

Strategic considerations

I treat performance as a real feature. The win that lasts is putting the checks into CI, so speed and accessibility hold up as the product keeps growing.

Web PerformanceCore Web VitalsAccessibilityReactCI/CD

Off the clockSide projects

Smaller things I've built for fun outside of work: open-source tools, experiments, and a few coding challenges.

Marksight, an open source Markdown editor

Marksight, an open source Markdown editor

Challenge

Writers needed a fast, modern Markdown editor with real-time preview.

Solution

Built an OSS editor with React, Next.js, TypeScript, CodeMirror, and react-markdown.

Result

A snappy, responsive editor with live preview, syntax highlighting, and smooth UX.

ReactNext.jsTypescriptreact-markdowncodemirrormotion.devTailwindShadcn
AI ChatBot

AI ChatBot

Challenge

Users wanted to chat with an AI in a fun and interactive way, with some admin control over content.

Solution

Built a chatbot using Google Generative AI, React, Next.js, and Typescript with an admin panel and theme support.

Result

Created a responsive, interactive AI chat experience with full admin oversight and real-time responses.

Google Generative AIReactNext.jsTypescriptShadcnClerkMongoDBNext-themesTailwind
AI Need an Idea

AI Need an Idea

Challenge

Developers struggled to find personalized programming project ideas suited to their skill level.

Solution

Built an app that generates tailored project ideas using Google Generative AI, React, Next.js, and Typescript with animations and UI enhancements.

Result

Helped users quickly find project ideas to improve skills and learn new technologies, all in a free, interactive app.

Google Generative AIReactNext.jsTypescriptFramer MotionTailwindRadix UIZod
Words of Encouragement

Words of Encouragement

Challenge

People wanted to share and receive encouraging messages anonymously without creating accounts.

Solution

Developed a web app using React, Next.js, and Typescript allowing users to post and view anonymous messages with animations.

Result

Created a safe and positive space for users to send and receive encouragement, improving user mood and engagement.

ReactNext.jsTypescriptFramer MotionCSS Modules
Basement

Basement

Challenge

Build an immersive e‑commerce with rich animations and interactions.

Solution

Created a Next.js PWA with drag-to-cart, custom cursors, marquees, and confetti.

Result

Responsive, installable app with interactive displays and smooth checkout.

Next.jsReactTypeScriptESLintFramer MotionTailwind CSSNext PWANext SEOUUIDClsx
Paisanos NFT

Paisanos NFT

Challenge

Build an accessible NFT marketplace with strong filtering and performance.

Solution

Implemented filtering, sorting, animations, sounds, tests, and PWA in Next.js.

Result

90+ Lighthouse scores with immersive interactions and solid coverage.

Next.jsReactTypeScriptReact Testing LibraryJestESLintFramer MotionReact SelectCSS ModulesNext PWA

ProcessHow I work, from idea to shipped

The way I actually work, end to end: figuring out what to build, building it well, and staying with it after it ships. I borrow the botanical names because that's roughly how it grows.

Step 1

Seed

Discovery & Strategy

I start by getting the problem straight: who it's for, what success looks like, and where the real constraints are. Then I map out the technical shape of it, so the build rests on something solid instead of guesswork.

  • Working out requirements and goals
  • Technical architecture and trade-offs
  • Accessibility, privacy, and performance from day one
  • A timeline and milestones I can stand behind
Step 2

Grow

Design & Development

This is where I'm most at home: turning the plan into a real, working interface. I build it component by component, keep it fast and accessible as it grows, and test as I go so quality stays high.

  • Component-driven build in React and Next.js
  • Responsive, accessible implementation
  • Performance kept in check, with checks in CI
  • Continuous testing and iteration
Step 3

Flourish

Launch & Evolution

Launching is just the beginning. I handle a clean deploy, watch how it behaves with real usage, and keep improving from there, fixing what the data shows and planning what comes next.

  • Clean deployment and monitoring
  • Analytics and real user feedback
  • Ongoing maintenance and improvements
  • Planning for scale and what's next

Want to talk about working together? Let's chat.

ValuesValues that root everything I do

A few principles that show up in everything I build, and in how I work with a team.

Security & compliance first

I tend to catch privacy, security, and compliance risks before they ship. That comes from working on HIPAA-compliant healthcare and knowing the OWASP Top 10 well.

Accessible & human-first

I build interfaces that are accessible and genuinely easy to use. Technology should work for everyone, not just the average user.

Performance as a feature

I keep things fast and well-tested, with performance checks in CI so quality doesn't slip as the product grows.

Honest about new tech

I try to be clear-eyed about when AI or extra complexity actually helps, and when a simpler approach is the better call.

Get in touchLet's Plant the Seed of Your Next Idea

Every great digital experience starts with a conversation. Whether you're launching a startup or transforming an enterprise, I'd love to help your vision flourish.

Prefer email?

laramateoco@gmail.com→