Rob Rose
Engineering Leader · Strategy, Delivery & Team Development

I build things
to understand them.

20+ years building, scaling, and leading high-performing engineering organizations across healthcare modernization, financial services, and cloud architecture. This site started as a serverless resume and turned into a learning lab — every layer is something I wanted to take apart and rebuild.

Experience
20+ years
Currently
Engineering Manager · Bellese
Cloud
AWS Serverless
Domain
Healthcare · FinServ
The Journey

A static page would have taken
an afternoon. So I kept going.

Each layer of this site exists because I wanted to understand something. Here's how a resume page became a serverless platform.

01

The Resume Site

Serverless from the ground up

Started as a serverless portfolio — FastAPI on Lambda, DynamoDB, Terraform, the works. One codebase that runs the same locally and in production.

Could have been a static page. Wasn't the point.

02

RobbAI

The chat widget

Added an AI assistant to the resume. "What does Rob do?" felt more interesting than a bullet list. That experiment turned into something bigger.

Try the chat bubble in the bottom right — that's RobbAI.

03

Bot Factory

A platform falls out of the experiment

The chatbot code was reusable, so I extracted it into Bot Factory — a platform where you define a bot with YAML and deploy it to serverless AWS.

RobbAI is one bot running on it. Anyone else's bot can be too.

04

The Fret Detective

First real product on the platform

An AI guitar teacher built on Bot Factory. Proof the platform works for more than just my resume.

Same infrastructure, different domain. That's the point of a platform — and the point of building this way.

The AI Journey

How I learned
to build this way.

What started as curiosity turned into a different way of working. Here's how, and what I'd pass along to another senior engineer.

How I got here
Curious
Played with it on my own time before any of it was for work. I wanted to see what was actually there, not what someone else's demo showed me.
User
Started bringing it into specific work problems — the ones where the answer was already clear but the path was tedious. Low-stakes places to learn the shape of the tool.
Builder
Stopped just using it and started building with it. RobbAI began as a feature on this site. It turned into Bot Factory, which turned into The Fret Detective. Each one taught me more than the last.
Daily collaborator
Claude Code and agent loops changed everything. Once the loop tightened — write, test, fix, repeat — it stopped feeling like a tool I reached for and started feeling like a teammate I worked with.
What stuck

Vibe Design, then code.

Once the shape of the work is right, let AI do the doing — but in small steps, with check-ins between. Then one more checkpoint than you think you need.

The agent loop is the unlock.

Chat is useful. Agents tighten the loop. That's when AI moved from neat toy to "this changes how I work" — and where the ceiling of what I could build went up.

Verify everything.

Confident-but-wrong is the real failure mode. The trust comes from the feedback loop, not from the model. If I can't see the output failing, I'm not actually evaluating it.

It doesn't replace understanding.

I still have to know the system. AI accelerates the building; the judgment about what to build, and why, stays mine.

Experience

Two decades of building
in regulated industries.

Healthcare, financial services, and the AWS work that ties them together.

Loading experience…
Skills

What I reach for.

The stack I keep coming back to, grouped by purpose.

Loading skills…
System Architecture

This site, drawn honestly.

A request from your browser to the byte stream coming back — every box is a real piece running in AWS.

CLIENT EDGE COMPUTE DATA & AI robrose.info Visitor browser R RobbAI embedded CloudFront CDN · TLS · cache API Gateway REST · auth · throttle S3 static assets Lambda · FastAPI resume · contact · health Lambda · RobbAI bot-factory DynamoDB resume content Amazon Bedrock Claude via Bedrock TERRAFORM All boxes on the left are declared as code. One module per env. Stage = prod, locally. "It runs the same locally and in prod." HTTPS origin direct call
FrontendStatic HTML, served from S3 via CloudFront
APIFastAPI on Lambda behind API Gateway
StateDynamoDB for resume content
IaCTerraform — every box, every env
Education & Contact

Education

Loading education…
Get in touch

Hiring, collaborating, or just curious — say hi.

Easiest is the chat. If you'd rather email, this form runs through the FastAPI Lambda behind the rest of the site.