Why I organized my projects around Healthcare, AI Quality, Automation, and Full Stack Engineering.
That question matters. Projects can be hard to evaluate when they are scattered across GitHub repositories, demo links, and generic portfolio pages.
A recruiter may only have a few minutes. An engineering team wants to understand how I think, not just what tools I used.
These areas are not random. They reflect my background, my strengths, and the kind of software engineering work I want to keep doing.
RCM analytics, medical coding validation, and healthcare coordination.
Data annotation workflows, edge cases, and human review systems.
Voice-to-task tools, API pipelines, and reducing manual friction.
React, Tailwind, dashboards, local-first storage, and architecture.
Before focusing deeply on software engineering, I worked with healthcare operations, RCM, and medical billing workflows.
In healthcare, a small workflow gap creates a real problem. That experience changed the way I think about building software.
I don't only think about the interface. I think about the workflow behind it.
I believe AI systems are only useful when the workflow around them is strong.
AI quality is not only about the model. It is about the data, the labeling rules, the edge cases, the validation process, and the human review step.
I want my AI projects to show practical AI thinking, not generic AI excitement.
Many real business problems begin with repeated manual work.
In healthcare operations, I saw how much time is lost to repetitive steps, duplicate entry, and disconnected tools.
That experience made automation feel practical to me. Not trendy. Practical.
I want recruiters to see that I can connect different parts of a software system.
The UI matters. The data model matters. The API matters. The storage decision matters. A project is strongest when these pieces work together.
I care about both implementation and usability.
I could have grouped everything by React, Python, APIs, SQL, or AI. But technology matters just as much as problem context.
The lesson learned: A portfolio should not make people work hard to understand your value. It should reduce friction. It should guide the reviewer. It should make the signal clear.
If you are a recruiter, hiring manager, engineer, or healthcare technology team looking for a Software Engineer with healthcare workflow experience and practical project work, I would be happy to connect.
Engineering Case Studies Hub:
https://tabitha-dev.github.io/Engineering-Case-Studies-Hub/Portfolio:
https://code.tabitha.dev/GitHub:
https://github.com/tabitha-dev