Technical Support Engineer | SQL, HL7 & Cloud Infrastructure
Tier II escalation & root-cause analysis · SQL & data validation · HL7 v2 / EDI · API integrations · Azure SQL & server administration
I'm a Senior Product Support Representative, Tier II at Nextech Systems, a HIPAA-regulated healthcare SaaS platform, and the internal escalation point for critical incidents Tier I can't resolve. I diagnose complex system crashes, network failures, and software errors, and drive root-cause analysis on 50+ incidents monthly using Event Viewer, Process Monitor, and Wireshark to isolate routing problems, handshake failures, and traffic bottlenecks, 20% faster than team baseline. From there I partner with product development and engineering to scope and deploy the permanent fix, not just the workaround.
Underneath that is the data and infrastructure layer: I maintain Azure SQL Server environments and 50+ client-hosted servers at 99% uptime, support 20+ HL7 vendor API integrations (troubleshooting bi-directional sync, debugging broken web services, and repairing HL7 parsing errors to prevent data loss), and write complex SQL queries and scripts across 5–10+ tables to validate data integrity, repair corrupted records, and diagnose vendor API failures. I also administer Active Directory, manage firewalls, and interpret intrusion logs across Windows Server, macOS, and Azure.
I'm completing a B.S. in Computer Science (expected November 2026), coursework spanning cloud computing, DevOps, and data structures & algorithms, and I'm moving toward data engineering: the pipelines, modeling, and cloud data platforms just past where my current role stops. I also build full-stack applications, PulseList and Anchor, which cover data modeling, cloud sync, and product thinking.
A task tracker that visualizes urgency through live countdown timers and real-time progress signals. Multi-view (grid, list, timeline), Firebase cloud sync, and Google Calendar integration.
A lightweight finance suite covering budgets, savings goals, bill tracking, and net worth — cloud sync via Firebase, no forced sign-up. Built around what people actually need to know about their money.
Designed and maintained structured forms for clinical patient intake — 5–10 per day — mapped directly to EHR data fields to automate data pull workflows and reduce manual re-entry at the front desk.
Problem: Most task apps treat deadlines as static dates. You see a list of due dates, but you don't immediately know what needs attention in the next hour vs. next week.
Insight: Urgency is about time remaining, not just the date itself. Real-time countdown timers — not just due dates — tell you what to focus on next.
Solution: PulseList puts countdown timers front and center. Every task displays live time remaining, with color signals that shift from green → yellow → red as deadlines approach. Supports multiple views: a focused Today dashboard, a full task grid, and a timeline for longer-term planning.
Technical highlights:
What this demonstrates: Full-stack web development, cloud-synced architecture, product thinking, and production-ready code with accessibility and error handling built in.
Problem: Financial apps are either too complex, too simplified, require account linking and data sharing. None of them start with what most people actually need to know.
Insight: Most people only need a few core metrics: How much am I spending? Am I on track with my budget? What's my net worth? When are my bills due? How close am I to my savings goals?
Solution: Anchor is a lightweight finance app that syncs to Firebase for cross-device access, and covers the essentials: accounts, transactions, budgets, goals, and bills — with net worth calculated as assets minus liabilities.
Technical highlights:
What this demonstrates: Complex business logic, financial data modeling, full-stack development, and user-centric design.
Problem: Manual patient intake is one of the biggest sources of friction in a medical practice. When patients fill out unstructured documents, front desk staff re-enter that data by hand — introducing errors, slowing check-in, and creating compliance risks in a HIPAA-regulated environment.
Insight: A well-structured digital form isn't just a convenience — it's a data pipeline. If the fields are defined correctly from the start, the data flows cleanly into the system without manual intervention. The form is the first step of the clinical workflow.
Solution: Designed and developed structured patient intake forms at a volume of 5–10 forms per day using Microsoft Word and Excel with the Developer toolkit — building forms with defined data fields, content controls, dropdowns, checkboxes, and input validation to standardize how patient information is captured across the practice. Forms were built to map directly to the data fields used in Nextech's EHR platform.
Technical highlights:
Impact:
What this demonstrates: Data field design and mapping in a clinical environment, HIPAA-aware development, healthcare IT domain knowledge, and high-volume production output with real operational impact.