01
Frontend
Semantic HTML, custom CSS, and JavaScript keep the site fast, understandable, and easy to maintain without unnecessary framework overhead.
Software engineering · systems · AI/ML
I build software that stays clear under pressure.
I work where software engineering, systems thinking, and real-world operations meet — building backend services, automation, technical workflows, and AI/ML foundations that are maintainable, understandable, and useful.
JavaPythonNode.jsC++SQLLinuxAzureGit
engineering_profile.json
20+
Healthcare facilities supported
40%
Reported performance improvement
35%
Reduction in bug density
95%
Platform adoption achieved
20+
Healthcare facilities across enterprise engagements
40%
Performance improvement highlighted in implementation work
35%
Bug-density reduction through code-quality practices
95%
Software-platform adoption through training and guidance
Selected work
Projects that reveal how I think.
Not just technologies — these projects show business rules, architecture choices, data modeling, UI workflows, collaboration, and the discipline to turn requirements into working software.
01 / FEATURED↗
Airline Reservation System
C# · WPF · .NET · ADO.NET
Desktop reservation software with seat-allocation logic, passenger workflows, validation, relational persistence, and clear separation between interface and data responsibilities.
02 / WEB↗
Word Association App
Node.js · Express · EJS
Server-rendered application covering routing, forms, role-aware workflows, browser debugging, and an architecture designed to grow toward persistent storage.
03 / SYSTEM DESIGN↗
MOAB Family RV Park
Node.js · Express · MySQL · Bootstrap
Team-led reservation-system design replacing paper and phone workflows with online booking, Stripe payments, role-based operations, reporting, auditability, UML models, an ER design, and UI mockups.
Engineering case study
How I built this portfolio.
The portfolio itself is a software project: a static-first interface, responsive component system, interactive portfolio assistant, deliberate deployment choices, and an architecture designed to grow into a secure AI-backed experience.
Current architecture
LIVE ON GITHUB PAGES
Fast in the browser. Simple to deploy. Ready to evolve.
I kept the current site intentionally lightweight. The interface, animations, responsive behavior, and portfolio concierge all run in the browser, while GitHub provides version control and static deployment.
01
Visitor
Desktop or mobile browser
02
HTML + CSS
Semantic structure and responsive visual system
03
JavaScript
Interactions, animation, and local portfolio knowledge
04
GitHub Pages
Versioned static hosting and deployment
Static-first
Responsive
Accessible focus states
Reduced-motion support
No AI secret in the browser
02
Portfolio assistant
The current concierge uses curated knowledge, streamed-looking replies, conversation state, lead capture, and a direct email handoff experience.
03
Security decisions
I do not place model API credentials in public GitHub Pages code. The real AI version is designed around a server-side secret and a controlled API boundary.
04
Responsive UX
Layouts collapse intentionally across breakpoints, navigation becomes mobile-friendly, interactive targets stay usable, and reduced-motion preferences are respected.
05
Deployment
GitHub is the source of truth. Each portfolio change is versioned in the repository and published through the GitHub Pages workflow.
06
Engineering challenges
The interesting work is balancing visual polish, mobile behavior, truthful AI capability, public-repository security, maintainability, and fast loading.
//
Built to stay truthful: the site labels the current assistant as a local knowledge experience instead of pretending it is already connected to a live AI model. When the secure backend goes live, this architecture section can evolve with it.
Experience signal
Engineering shaped by production reality.
My background spans software production, infrastructure, healthcare technology, deployment readiness, APIs, databases, automation, and hands-on troubleshooting.
2025 — Present
Healthcare Technology Solution Analyst
TruBridge / CPSIEnterprise healthcare engagements, implementation readiness, technical evaluation, deployment coordination, workflow improvement, software adoption, and client training.
2024 — 2025
Software Production Engineer
OneSourceREST APIs, SQL, Git workflows, Python/C++ tooling, code quality, automation, debugging, release discipline, and cross-functional Agile delivery.
2021 — 2024
Project Lead
Dubuque County CourthouseEnterprise deployments, Azure identity, networking, endpoints, disaster recovery, patch management, troubleshooting, and technical leadership across departments.
AI + engineering
AI curiosity, grounded in software fundamentals.
I’m interested in AI-enabled software that is explainable, maintainable, and connected to solid engineering: clean inputs, reproducible environments, evaluation, APIs, data, and dependable user experience.
AI/ML foundation
Python environments, data preparation, model training and evaluation — connected to a broader systems mindset.
Python + environmentsConda, venv, reproducible setups
Model workflowPreparation, training, evaluation
Engineering contextAPIs, data, reliability, automation
Portfolio Intelligence
Interactive profile guide
local knowledge demo
Your details stay in this browser until you choose to email Suresh.
Connect
Looking for someone who can think across code and systems?
Explore the projects and experience, then reach out if my mix of software engineering, automation, systems work, and AI/ML foundations fits what your team is building.