Healthcare Systems
Navigate prescription, claims, benefit, refill, and order systems to investigate member issues and understand what is happening across the healthcare workflow.
Healthcare experience × Software engineering
Building technology that makes healthcare easier to navigate.
I combine software engineering with firsthand experience as a Customer Service Advocate to understand healthcare problems from both sides: the technology behind the system and the people who rely on it.
Experience portfolio
Real conversations. Real pressure. Real customer advocacy.
This portfolio goes beyond job duties and metrics to showcase the real moments that define strong customer service — de-escalating difficult conversations, solving complex prescription issues, supporting teammates, and creating trust when people need clarity the most.
Systems Thinking
Look beyond the immediate member question to understand how processes, information, technology, and different parts of the healthcare system connect.
Problem Analysis
Investigate claim activity, benefit information, prescription history, and workflow details to identify what happened, where friction exists, and what needs to happen next.
Quality Mindset
Pay close attention to accuracy, system outcomes, process consistency, and the difference between what should happen and what actually happens.
Engineering Perspective
Combine firsthand healthcare experience with software engineering knowledge to think about how technology can reduce friction, improve workflows, and create more reliable solutions.
Healthcare Systems
Navigate prescription, claims, benefit, refill, and order systems to investigate member issues and understand what is happening across the healthcare workflow.
Systems Thinking
Look beyond the immediate member question to understand how processes, information, technology, and different parts of the healthcare system connect.
Problem Analysis
Investigate claim activity, benefit information, prescription history, and workflow details to identify what happened, where friction exists, and what needs to happen next.
Quality Mindset
Pay close attention to accuracy, system outcomes, process consistency, and the difference between what should happen and what actually happens.
Engineering Perspective
Combine firsthand healthcare experience with software engineering knowledge to think about how technology can reduce friction, improve workflows, and create more reliable solutions.
Where healthcare experience meets technology
Working directly with members has shown me where healthcare systems create friction, confusion, and unnecessary complexity — and it has shaped how I think about building better technology.
As a Customer Service Advocate, I work directly with people navigating prescription benefits, claims, refills, prior authorizations, coverage questions, and other parts of the healthcare experience. Every interaction gives me a closer look at how technology, processes, and benefit systems affect people in the real world.
That experience has taught me that many healthcare challenges are not simply people problems. They are often systems problems: information can be difficult to find, processes can be disconnected, and small points of friction can create significant stress for the person trying to get care.
My role has therefore strengthened the way I approach software engineering. I naturally look beyond the immediate problem and start thinking about how the underlying system could work better: what information should be surfaced, what steps could be simplified, what could be automated, and how technology could help people reach the right outcome more efficiently.
Combining my frontline healthcare experience with my software engineering background gives me a perspective that extends beyond writing code. I understand the human impact behind the requirements and can think about how technical solutions translate into better experiences for members, advocates, providers, and healthcare teams.
I want to use that perspective to build technology that makes healthcare more accessible, intelligent, efficient, and human-centered.
Real-world healthcare insight
Working directly with members gives me firsthand knowledge of the challenges people encounter across prescriptions, claims, benefits, coverage, and healthcare workflows.
Identifying system friction
I pay attention to recurring problems and patterns, asking how technology, better information flow, automation, or improved interfaces could reduce unnecessary complexity.
Engineering with empathy
My customer-facing experience helps me think about software from the perspective of the person actually using it—not just how the system is designed technically.
Building toward better healthcare
My goal is to combine healthcare knowledge, software engineering, problem-solving, and continuous learning to build solutions that improve both operational efficiency and the member experience.
The journey
From using healthcare technology to understanding how to improve it.
My experience as a Customer Service Advocate has given me firsthand insight into how healthcare technology, business processes, and member needs intersect—and has prepared me to contribute as a Business Analyst, Quality Analyst, or Software Engineer.
Era 01
Learning How Healthcare Technology Serves Members
I began developing my healthcare foundation by working directly with members and using the systems that support their prescription benefits. I learned how to interpret benefit information, explain coverage clearly, and translate complex system information into answers that members could actually understand.
Era 02
Connecting Benefits, Refills, and Order Logistics
As my experience grew, I developed a stronger understanding of how different parts of the prescription process connect. I assist members with refills, order status, timing, benefit questions, and logistical barriers while navigating multiple systems to determine what is happening and what needs to happen next.
Era 03
Seeing the Patterns Behind the Problems
Working with members has taught me to look beyond individual interactions and recognize recurring patterns. When the same questions, process gaps, system limitations, or points of confusion appear repeatedly, I naturally start thinking about the underlying workflow and how better processes or technology could reduce that friction.
Next Step
Turning Healthcare Experience Into Technical Impact
My goal is to bring together what I have learned on the front lines of healthcare with my software engineering background. Whether I am analyzing business requirements, testing and improving quality, investigating system behavior, or building software, I want to help create technology that makes healthcare processes more accurate, efficient, and easier for members and the people who support them.
Technology in action
Using healthcare systems to solve member problems—and learning to think beyond the immediate issue.
As a Customer Service Advocate, technology is central to how I investigate and resolve prescription problems. I work with prescription history, claim activity, benefit information, refill requirements, order status, and other system information to understand what is happening behind the member's question.
That experience has also changed the way I think about problems. I have learned to look beyond the immediate interaction and ask questions that connect directly to the work of a Business Analyst, Quality Analyst, and Software Engineer.
Member problem
“Where is my prescription?”
A member calls after waiting for a prescription that has not arrived. Their doctor believes the prescription was sent, while the member does not know whether the issue is related to the prescription, pharmacy processing, shipping, or something else in the workflow.
Systems & technology
Prescription history
Claim activity
Order status
Refill timing
Benefit information
How I investigate
Follow the prescription through the system.
I review prescription history, claim activity, timing, and available order information to determine where the prescription is within the process. If the prescription has moved to mail service, I work with the appropriate pharmacy resources to determine its status and explain the available options to the member.
Business Analyst thinking
Where did the process break down? What information is available? What does the member need to know to move forward?
Quality Analyst thinking
What should have happened at each stage? Where did the actual workflow differ from the expected outcome?
Software Engineering thinking
Could better system visibility, notifications, automation, or workflow design prevent this confusion?
Member problem
“Why does my notification say my medication is not covered?”
A member receives a notification that a medication requires prior authorization and is unsure what the message means, who needs to act, or how the process affects their ability to receive their medication.
Systems & technology
Coverage information
Claim response
Authorization status
Prescriber workflow
Benefit rules
How I investigate
Translate system behavior into understandable next steps.
I review the available information to determine what the plan is waiting for, explain the prior authorization process in plain language, and identify the appropriate next step for the member or prescriber.
Business Analyst thinking
What is the current authorization workflow? Where is the member experiencing friction? What information is missing?
Quality Analyst thinking
Did the notification accurately represent the system state? Was the correct information presented to the member?
Software Engineering thinking
How could the system communicate authorization status more clearly and reliably?
Member problem
“I'm out of medication and my refill won't process.”
A member is transitioning to mail service but has already run out of medication. The immediate problem requires attention while the underlying refill workflow also needs to be understood.
Systems & technology
Refill history
Claim processing
Benefit rules
Mail-order workflow
Pharmacy information
How I investigate
Separate the immediate problem from the underlying workflow.
I review the available claim and benefit information to understand why the local refill did not process, identify possible options for the immediate need, and explain how the future mail-order process should work.
Business Analyst thinking
What is the intended refill process? Where does the member's experience differ from that process?
Quality Analyst thinking
What condition caused the refill to reject? Did the system behave according to the applicable rules?
Software Engineering thinking
How could the workflow better anticipate timing issues and prevent avoidable interruptions?
Member problem
“Why is my prescription suddenly more expensive?”
A member arrives at the pharmacy expecting a familiar copay but finds that the medication costs significantly more than expected.
Systems & technology
Claim data
Medication tier
Quantity
Days supply
Accumulator information
How I investigate
Use available data to understand the outcome.
I review claim information, medication details, quantity, days supply, benefit tier, and applicable accumulator information to understand the factors contributing to the member's cost and explain the result clearly.
Business Analyst thinking
What business rules influence the member's cost and what information is needed to explain the outcome?
Quality Analyst thinking
Did the claim process according to the expected benefit rules? What data contributed to the result?
Software Engineering thinking
How can systems make complex cost information more transparent, consistent, and understandable?
Member problem
“The pharmacy says my insurance rejected the prescription.”
A member has active coverage but receives a rejection at the pharmacy and needs to understand why the claim did not process.
Systems & technology
Claim adjudication
Rejection information
Refill restrictions
Quantity limits
Benefit rules
How I investigate
Identify the point of failure and determine the next action.
I review the claim response to understand whether the rejection is associated with refill timing, quantity limits, days supply, coordination of benefits, authorization requirements, or other processing conditions. I then explain the result and identify the appropriate next step.
Business Analyst thinking
What process is supposed to occur? Where is the friction and what information is needed to resolve it?
Quality Analyst thinking
What should the claim have done? What actually happened? Can the rejection be traced to a specific condition or rule?
Software Engineering thinking
How could the system be designed to handle these conditions more reliably and provide clearer feedback when something fails?
Leadership indicators
The way I work is the proof.
A future lead or supervisor should be measured by more than tenure. These are the practical behaviors I bring into customer service work.
Operational Empathy
I think about the customer, the advocate handling the issue, and the process behind the interaction. Good service should work for everyone involved.
- Clear documentation
- Customer-centered communication
- Awareness of internal handoffs
Calm Under Pressure
High-volume or emotional situations require patience, focus, and tone control. I aim to bring stability when conversations become difficult.
- De-escalation mindset
- Steady prioritization
- Professional follow-through
Team-First Thinking
Leadership is not only about being the strongest individual performer. It is about helping the team communicate, improve, and stay aligned.
- Peer support
- Knowledge sharing
- Constructive feedback
Team engagement
Creating connection through humor, encouragement, and small team moments.
I believe a strong customer service team needs more than process knowledge. It also needs encouragement, connection, and moments that make the day feel lighter. I use playful messages, funny replies, helpful tips, and team prompts to help build morale while keeping the space professional and supportive.
Morning energy
Playful good morning messages
I like starting the day with cheerful good morning messages, cute GIFs, and positive energy. It gives the team a small moment to smile before jumping into calls, queues, and customer needs.
Morale building
Positive tone
Team connection
Team check-ins
Funny replies to “How’s it going?”
When someone asks, “How’s it going?” or “How are calls?” I keep it honest but playful. I use humor to acknowledge the day without making it feel negative, helping the team laugh while still staying focused.
Humor
Honesty
Emotional awareness
Keeping it light
Jokes that make stressful moments easier
Customer service can be emotionally heavy, so I use appropriate jokes and playful replies to help the team reset. A quick laugh can make a difficult day feel more manageable.
Stress relief
Team morale
Appropriate humor
Getting to know each other
Polls
I like posting simple polls and fun questions that help teammates learn about each other. These small interactions create connection, make the chat feel more welcoming, and help people feel included.
Inclusion
Relationship building
Engagement
Ending the day well
Funny and playful goodbye messages
At the end of the day, I like sending playful goodbye messages that celebrate making it through the shift. It gives the team a lighthearted closing moment and helps everyone leave on a better note.
Encouragement
Positive closure
Team spirit
Coming soon
Mindset pages for deeper leadership philosophy.
Later, this portfolio can include pages about how I approach coaching, conflict resolution, quality conversations, team morale, and service improvement.