Principle
Clarity over theatrics
I like work that gets sharper as it gets simpler. The best systems make complex things feel understandable without pretending the complexity is not there.
Software engineer
15 years of software engineering experience.
Experience across real projects, real constraints, and the day-to-day work of building software.
Selected work, writing, and more on how I approach software engineering.
About
Quick introduction
A little context on who I am, what I work on, and the kind of engineering problems I tend to be pulled toward.
I currently work as a Staff Software Engineer for Janus Health. My work spans frontend and full-stack engineering, with an emphasis on building software that stays usable, maintainable, and clear as the product and the team around it grow.
Over the last 15 years, I have worked across interfaces, APIs, data flows, and operational systems. I tend to do my best work where the requirements are real, the constraints matter, and the job is to turn something ambiguous or high-friction into software that people can actually rely on.
Why this format
- A resume shows chronology. A site can show judgment, taste, and working style.
- It creates room for projects, writing, and context that would feel cramped on a single page.
- It also leaves room to grow into a publishing surface instead of staying a static artifact.
How I Work
A few instincts that shape the work.
These are the tendencies I come back to across engineering, systems design, and operational cleanup.
Principle
Useful beats impressive
I care more about whether a thing solves the right problem than whether it sounds exciting in a status update. Reliability, maintainability, and clarity matter.
Principle
Calm under ambiguity
Messy work is usually not blocked by effort. It is blocked by confusion. I do well when the job is to reduce noise, define the shape of the problem, and move things forward.
Stack
A working set of technologies.
A sample of the tools and platforms I have used across frontend, backend, data, and delivery work.
27 items
Frontend
Interfaces, state, and browser work
TypeScript
JavaScript
React
Angular
Redux
Material UI
Storybook
GraphQL
Tool
REST APIs
Backend
Services, APIs, and systems work
Node.js
PHP
Postgres
Python
Tool
AWS
Data
Pipelines, analytics, and platform tools
Databricks
SQL
SQL
Moodle
Tool
CI/CD
Tool
Testing
Jest
Tool
Playwright
SCSS
Tool
PHPUnit
Git
SHOWCASE
Selected work
These entries are intentionally written more like working notes than polished marketing copy. The important thing is what problem the project helps solve.
Realtime collaborative whiteboard
Built a collaborative whiteboard with React, canvas, websockets, Yjs, Node.js, Postgres, and AWS infrastructure for multi-user editing and presentation workflows.
Drawing on a canvas was only one part of the problem. The harder part was making multiple people share the same space, interact with it continuously, and still have the product behave in a stable way.
Once a product becomes realtime, people judge it by how reliably it responds. If another user draws, moves, or presents something, the system has to update in a way that stays consistent for everyone involved.
- Industry
- Educational Technology
- Role
- Lead Engineer
- Stack
- React, Yjs, WebSockets, Canvas, AWS
Reusable personal-site foundation
A shared website system that can support both a personal site and a future company site through themes, shared components, and site-specific content.
- Industry
- Personal publishing
- Role
- Design and implementation
- Stack
- Astro, React, Tailwind, design tokens
Operational cleanup
The kind of work I enjoy most: taking brittle, high-friction workflows and turning them into clear, dependable systems teams can trust.
- Industry
- Internal operations
- Role
- Process design, system cleanup, execution support
- Outcome
- Less decision fatigue, fewer handoff errors, lower maintenance drag
Writing
A place for notes, patterns, and sharper thinking.
Writing here should support the same goal as the rest of the site: to make the work and the way of thinking behind it easier to understand.
Draft topic
What good internal tools actually optimize for
A note on usefulness, trust, and why polished interfaces do not matter if the workflow underneath is brittle.
Draft topic
The difference between motion and progress
Thoughts on how teams get stuck performing productivity instead of reducing actual uncertainty.
Draft topic
Why compact interfaces often feel more confident
A short piece about density, pacing, and making room for substance without making the page feel cramped.
Contact
Useful conversations welcome.
If you are hiring for product-minded engineering, systems work, or thoughtful execution in ambiguous environments, this is the kind of work I want to do more of.
The current content is intentionally lightweight so the structure can harden first. From here we can replace the placeholder details with your real bio, project narratives, writing, and links.