Self-Taught • Finance Background • Product Thinking
Self-taught full stack developer who ships product, not just code.
I work across the stack — frontend, APIs, databases, AI integrations — and care about the parts most portfolios skip: edge cases, error states, and code a teammate can pick up six months later.
Capabilities
Where I'm strong
End-to-End Delivery
UI, API, schema, deploy
Next.js + TypeScript
Type-safe, production-grade code
Tailwind UI Systems
Responsive interfaces with a real design eye
APIs + Databases
Reliable data, clean contracts
LLM Integration
OpenAI inside real product flows, not chatbots
Production-Ready Code
Tested, typed, reviewed before it ships
Skills & Technologies
The tools I actually reach for
Grouped by where they live in a product — not by logo recognition.
Frontend
- Next.js
- React
- TypeScript
- JavaScript
- Tailwind CSS
- Responsive design
- Accessibility fundamentals
Backend
- Node.js
- Express
- REST APIs
- Server-side rendering
- Authentication flows
- Form handling & validation
Databases & Data
- PostgreSQL
- MySQL
- MongoDB
- Prisma
- Schema design
- CRUD workflows
UI / Product Development
- shadcn/ui
- Lucide React
- Framer Motion
- Component architecture
- Design implementation
- Dashboard UI
AI Integration
- OpenAI API integration
- LLM-powered features
- Prompt structuring
- AI-assisted workflows
- Cost-aware design
- Guardrails & AI UX
Tools & Workflow
- Git & GitHub
- Postman
- Vercel
- Cloudinary
- Figma
- VS Code
- Debugging workflows
About
Self-taught, product-minded, and ready to contribute on a full-time team
In finance, edge cases cost real money. That instinct — stress-test before you ship — carried straight into software. Technical skills came from the ground up through real projects, not theory, with every gap in knowledge treated as something to close rather than work around. The foundation matters more than the credential.
The work spans the full stack — frontend through deployment — and the focus is always on what happens after the demo. Architecture that anticipates the API timeout, the double-submit, the malformed response. What breaks matters as much as what works. Every project carries the same commitment: simplicity, clear naming, and code that holds up under review.
Knowing something works isn't the same as knowing why it works. Studying production applications — what was built, what was cut, which tradeoffs shaped the outcome — builds the kind of judgment that tutorials can't. The same rigor applies to AI integration: tools earn their place by solving real problems, not by being trendy. Document every decision. Explain the non-obvious. Code outlives the context that created it.
- Self-Taught Engineer
- Finance Background
- Owns Decisions
- Edge-Case Minded
- Writes Readable Code
- AI-Forward
Contact
Hiring for a full stack role?
I'm open to full stack roles where strong frontend instincts and practical AI work both matter. Email is fastest — usually a same-day reply.