Selected work

What I build.
And the decisions behind it.

A team project in AI infrastructure and a personal product for a very practical decision.

01 / Memori Labs

Memori

Persistent memory for AI applications.

Staff Software Engineer · Team project

  • Python SDKs
  • Retrieval pipelines
  • AWS
  • MCP
Memori / integration overview
  1. 01
    Your applicationExisting LLM client & agent tools
  2. 02
    MemoriCapture, recall & augment
  3. 03
    SQL memoryContext that persists across interactions

Useful context. Familiar infrastructure.

The problem

AI applications need useful context across interactions. Adding memory should fit the application’s existing clients, data, and infrastructure while keeping irrelevant context out of the prompt.

My contribution

I own core engineering for the async-first Python SDK and memory platform. My work spans retrieval pipelines, provider integrations, MCP and Claude Code workflows, and production AWS infrastructure.

A key design choice

Combine embeddings, vector search, graph context, and reranking to select useful memories before augmentation. A pluggable provider architecture lets integrations fit different LLM ecosystems.

The result

An open-source SDK and memory platform with documented agent integrations and production deployment paths. I also own release quality through automated tests, type checks, CI, and the infrastructure behind Memori Cloud.

02 / Personal project

DwellingDiff

A clearer way to compare renting and buying.

Product design, backend, frontend & deployment

  • Python / FastAPI
  • Svelte
  • Vercel
Try the calculator
DwellingDiff / comparison model
Your assumptions
RENTRent + invest

Rent growth
Invested down payment
Monthly cost difference

BUYBuy + build equity

Mortgage & ownership costs
Home appreciation
Selling costs

Compare net worth over time

Inspect the calculation. Change the assumptions.

The problem

A mortgage payment and a rent payment tell only part of the story. Maintenance, transaction costs, home equity, rent growth, and investing the difference can all change the comparison.

What I built

A FastAPI calculation service and a Svelte interface that model both paths over time. I built the product around editable assumptions, shareable scenarios, and calculation receipts that explain where the numbers come from.

A key design choice

Keep the calculation service stateless and the model inspectable. Saved scenarios stay in the browser; share links encode assumptions. Sensitivity analysis helps users see which assumptions change the result.

The result

A working public calculator with scenario comparisons, cash-flow summaries, net-worth projections, and inflation-adjusted views. Users can explore the tradeoffs and inspect the calculation before trusting a headline result.

Earlier impact / Two Story

Performance people notice.

30+ s → 1.5 s

PDF generation time after optimizing the pipeline.

99.99% uptime

After migrating a low-code application to an AWS stack.

As engineering manager, I worked across roadmap delivery, mentoring, FastAPI services, AWS infrastructure, and multi-agent applications.

View my experience

Want to talk through a problem?

I’m happy to compare notes on backends, developer tools, and AI systems.

Get in touch