Resume

Software Engineer · Healthcare technology, pharmacy benefits management

• Engineering lead on a historical claims import platform: designed the data model so adjudication, accumulators, and reporting could consume imported claims with no code changes from those teams, and delivered it code-complete across three repositories ahead of the deadline
• Owned cross-team data-integrity validation for a legacy-to-modern claims platform migration: built a CLI validation suite with dozens of automated checks and a thorough unit test suite, wrote the source-to-target mapping and validation guide the team adopted, and independently verified the full dry-run at production scale before legacy decommission, with the handful of mismatches identified and explained
• Found and fixed a migration defect that had attached claims to the wrong members, correcting a large population of claims and heading off downstream eligibility, accumulator, and reporting errors
• Led cross-system data quality initiatives across the claims pipeline, finding and fixing systemic issues affecting large record populations, with production corrections delivered through formal change control
• Root-caused a high-exposure billing discrepancy and showed the real member impact was a small fraction of the headline figure, then rewrote the query plan behind it to take a large-scale member resolution from twenty minutes to seconds
• Investigated and resolved escalated production reporting incidents through root cause analysis, and wrote the correction runbooks so the fixes outlived the incidents
• Built Python automation for production claims analysis that turned hours of manual batch work into minutes, adopted as the operations team's standard workflow
• Designed GraphQL APIs bringing cost calculation transparency to pharmacy claims, with Relay-compliant patterns, graceful degradation for older data, and shared fragments that cut frontend duplication
• Performed 100+ code reviews per quarter across 8 repositories, catching security vulnerabilities, data integrity bugs, and race conditions before they shipped

Technical Lead, Full Stack Software Engineer · Payments

• Authored Python coding standards based on PEP 8/257 that became the team baseline, covering layout, naming, error handling, and documentation while keeping the payments platform PCI compliant
• Engineered a webhook subscription management system on AWS Lambda and DynamoDB, enabling real-time payment event notifications to external systems
• Built card-present transaction processing by integrating the TriPOS Cloud API with Payrix, from POS terminal communication through transaction storage
• Architected a secure, responsive iframe payment component in Next.js and TypeScript for credit card and bank account management inside the core application
• Restructured monolithic Lambdas into modular microservices with PyTest suites at 80%+ coverage, surfacing 60+ bugs along the way
• Designed the Datadog tagging schema and monitoring strategy across payment services, cutting incident response time through structured, contextual logging
• Mentored junior engineers through reviews and pairing, on Pythonic idioms, data structures, and test-driven development

Full Stack Software Engineer · Boutique fitness studio management SaaS

• Developed the Ember.js admin application and Django REST APIs for a multi-tenant platform serving national boutique fitness brands
• Implemented cart and checkout features including line-item discounts, quick-sale modals, and payment flows for in-studio point of sale
• Built automated end-to-end suites in Selenium and Python covering check-in, checkout, and class reservation flows
• Engineered a multi-tenant customization framework letting franchise clients ship white-labeled apps with their own styling and feature sets

Core Contributor, Full Stack · Accessibility-focused GUI for generating JavaScript tests, 1,000+ GitHub stars

• Materially improved application performance and cut code editor memory use by roughly 60% by replacing heavyweight dependencies while preserving full terminal emulation
• Extended TypeScript coverage through the React-Redux layer so action creators, reducers, and state were checked at compile time
• Implemented Redux for immutable, predictable state, eliminating unnecessary re-renders and prop drilling