Shan PadayhagSoftware engineerI turn demanding systems into reliable software — from the data underneath to the experience on top.
Step into my workspaceScroll to explore the computer, TV, and notebook.
Opening workspace
// Selected personal projects
Personal projects that put the hard parts first: trust, data integrity, and software that works offline.
// Identity & access
name:A production-shaped authentication vertical slice: Argon2id password hashing, email verification, JWT access tokens, revocable opaque refresh tokens, contract-first APIs, and end-to-end tests.
stack: ["Rust", "Axum", "AWS Lambda", "PostgreSQL", "sqlx", "OpenAPI"]
viewSource()// Local-first finance
name:A local-first finance application built around transactional ledgers, reconciliation, reports and denormalized read models.
stack: ["Next.js", "React", "TypeScript", "IndexedDB"]
viewSource()// Learning, offline
name:An offline study tool with rich cards, attachment management, backups, migrations and an FSRS scheduling integration.
stack: ["Astro", "SolidJS", "TypeScript", "IndexedDB"]
viewSource()// End of projects. Next: experience on the TV.
Tuning in
SP THE EXPERIENCE REEL
Professional experience making calculation-heavy systems faster, more reliable, and more efficient.
THE RESULTS / 01
3 s → 300 msSelected basic API calls after eliminating unnecessary database work.
THE RESULTS / 02
90%Database-load reduction through targeted performance remediation.
THE RESULTS / 03
99.9%Uptime maintained for a system used by 1,300+ daily operators.
BEHIND THE WORK
Sep 2022 — Jul 2024
Software Engineer
Primarily optimized slow existing production features in a calculation-heavy Laravel web and mobile application, while continuing to deliver across the full stack.
May 2021 — Sep 2022
Lead Developer
Provided technical direction for a small delivery team while building Laravel backend services and frontend features for web and mobile applications.
Up next: a few personal notes.
From my desk
My strongest work is in performance-minded systems. I build across backend, frontend, data, and production operations, and I’m learning Rust to broaden that toolkit.
How I work
I plan the work before I write it: understand what’s needed, shape the approach, then build in clear, testable steps. AI tooling speeds up implementation; the thinking, standards, review, and tests stay mine. Every line I ship is one I can explain and defend.
Worth keeping
An early lesson in engineering, mentorship, and learning through real work.
Read the noteKeep learning. Keep making.