FrudgeCare AI
Available · Summer and Fall 2026Portfolio · 026/Lake Charles, LA · CST2026
PRINCEPUDASAINI
About this folio
I design and ship software end to end. From the interface and APIs down to the infrastructure, I build products that actually work for the people using them.
- Role
- Full-Stack Developer · CS Student
- Stack
- Next.js · TypeScript · Python · FastAPI
- Studying
- B.S. Computer Science, McNeese State
- Building
- LetterLab Pro · FrudgeCare AI
FOLIO 026
P. PUDASAINI · 20264 × 5
SHOT · APRIL 2026036 / 064 EXP
Selected work
Now building · LetterLab Pro v1.0Open to Summer and Fall 2026 engineering internshipsStack · Next.js · TypeScript · Python · FastAPI · PostgresBased in Lake Charles, LA · Central Standard TimeWriting · short notes on building software people actually use
01Selected work · Case studies
Case studies, not screenshots.
Six builds. Two flagship case studies up front, four supporting projects below. Tap any card to read the full case study in place.
Featured projects
LetterLab.Pro
Supporting work
- Stock Price Trend Predictor
- Voice Language Translator
- Tweet Sentiment Analyzer
- Marks Calculator
02Stack ledger · Real tooling
Technologies I ship with.
Every brand below is a tool I've used in production or in a shipped project. Hover any specimen on desktop or tap it on mobile to reveal its official brand color.
Technology stack
- Tools
- 40
- Categories
- 7
- Focused
- None
Frontend
Type, motion, and state. The surface humans actually touch.
Backend & Runtime
APIs, business logic, and the predictable defaults underneath the UI.
Databases
Where state lives. Auth-aware, schema-honest, and transactional.
AI & ML
Model APIs, structured outputs, and the safety rails around them.
Auth & Integrations
Identity, OAuth, and the third-party surfaces my products live inside.
Cloud & Deploy
From local commit to live URL. Hosting, CI, and the platforms that ship the bits.
SEO & Analytics
How the work gets found. Crawlable surface, attribution, and behavior insight.
03Engineering Mindset
How I think as an engineer.
Six principles that show up in how I design systems, work with AI, and ship to production. Each one is paired with a small live demonstration.
- Principles
- 06
- Format
- Live diagrams
- Animation
- In-view loops
- Source
- Production work
01Product
Product-first engineering
I think from user workflow first, then design the system around it.
User journey → system
I figure out how a real person will actually use the thing first, then build the system around that, so the product ends up shaped like the journey it needs to serve.
02Integration
API and integration thinking
I build around real APIs, auth flows, tokens, and production edge cases.
Client ↔ API · token round-trip
Most products are stitched together from other people's services, so I think carefully about how those pieces talk to each other and what should happen when one of them is slow or breaks.
03AI
AI as a tool, not as magic
When I use AI in a product, I design a clear fallback path, structured outputs, and visible system states the user can actually trust.
Primary path + dotted fallback
AI can have an off day, so I always plan a safer fallback the product can switch to, which means users never hit a broken screen when the model gets it wrong.
04Interface
UI systems
I care about layout, spacing, visual hierarchy, and interaction clarity.
Layout grid · hierarchy
A clean, well-organised layout is what turns a working app into one people actually enjoy using, so the look and feel get the same level of care as the code underneath.
05Operations
Deployment reality
I debug real production issues across frontend, backend, OAuth, environment variables, and hosting.
Three-tier deploy pulse
Most real-world bugs only show up once the product is live, so I care just as much about what happens after the deploy button as the work that came before it.
06Narrative
Documentation and storytelling
I explain systems through architecture, case studies, and clear technical writing.
Sketch → annotated architecture
If I can't explain a system in plain words, it probably isn't designed well yet, which is why writing and clear diagrams are part of the engineering for me, not paperwork added at the end.
04About
Engineering at the intersection of product and people.
I'm Prince Pudasaini, a Computer Science student at McNeese State University. I build practical software products across the full stack: frontend, backend, APIs, and the product design that ties them together. My work focuses on turning rough ideas into usable systems. Email assistants, healthcare coordination prototypes, and data-driven dashboards.
I enjoy building at the intersection of engineering, design, and real-world workflows. I care about systems that are not only functional, but understandable, safe, and useful for the people who actually use them.
05Career · Selected involvements
A timeline, not a CV.
Six chapters across academic work, founding projects, engineering leadership, and recognition. Navigate with arrows, clicks, or your keyboard.
202420252026
◇ EducationCH · 01
Year
2024 – Present
Computer Science Student
McNeese State University
Lake Charles, LA
Building foundations across data structures, systems, and software engineering while shipping side projects in parallel.
- Coursework spanning algorithms, OS, databases, and software engineering
- Active in the engineering community and faculty research conversations
- Keeping a parallel portfolio of shipped software work outside of class
- Stack
- PythonC++SQLLinuxGit
01/06
Contact sheet · all chapters
6 entries
06Contact
Let's build something useful.
Currently open to Summer and Fall 2026 internships. Happy to share my resume, walk through case studies, or jump on a call.
Availability
Looking for full-stack and software engineering internships.
Based in Lake Charles, LA. Remote friendly. References and case studies available on request.