{
    "componentChunkName": "component---src-templates-work-js",
    "path": "/work/axle-health",
    "result": {"data":{"markdownRemark":{"html":"<h2>Axle Health</h2>\n<p><strong>Senior Full-Stack Engineer • Contract</strong></p>\n<p>Enterprise-grade logistics platform for in-home care operations</p>\n<p>Worked on a high-complexity scheduling and coordination system used by care teams managing real-world patient visits. The product sits at the intersection of logistics, healthcare, and operations, where reliability matters more than anything.</p>\n<hr>\n<h3>Key Outcomes</h3>\n<ul>\n<li>Improved consistency across scheduling and operations workflows.</li>\n<li>Reduced friction for coordinators managing multi-visit, real-world logistics.</li>\n<li>Strengthened frontend/backend contract reliability in workflow-heavy systems.</li>\n<li>Helped establish a more scalable foundation for future automation and analytics.</li>\n</ul>\n<hr>\n<h3>Client</h3>\n<p>Axle Health operates in a space where software directly impacts real-world care delivery. Their platform focuses on scheduling, route optimization, patient engagement, and operational visibility for in-home healthcare providers.</p>\n<p>As demand scaled, the system needed to remain flexible without becoming unpredictable — something that’s easier said than done in logistics-heavy products.</p>\n<p>I joined to support product and engineering initiatives focused on improving reliability, clarity, and scalability across core workflows.</p>\n<hr>\n<h3>Contributions</h3>\n<p>Most of my work sat at the intersection of <strong>frontend workflows and backend orchestration</strong>.</p>\n<p>One of the first things I noticed was how sensitive the system was to small inconsistencies — especially in scheduling and workflow transitions. In a product like this, a minor mismatch between UI and backend logic can cascade into real operational confusion.</p>\n<p>I focused on tightening that layer:</p>\n<ul>\n<li>Improved behavior across key workflow handoffs between scheduling and operations.</li>\n<li>Strengthened API and UI contract alignment to reduce ambiguity in critical flows.</li>\n<li>Contributed to backend services handling scheduling logic and workflow orchestration.</li>\n<li>Supported async/background processes for handling operational events and exceptions.</li>\n</ul>\n<p>On the frontend side, I worked with <strong>React + TypeScript</strong>, building internal tooling used by coordinators who rely on speed and clarity to do their jobs.</p>\n<p>On the backend, I worked within a <strong>Node.js + AWS environment</strong>, supporting services that needed to be predictable under real operational load.</p>\n<hr>\n<h3>Challenges</h3>\n<h4>1. Scheduling is not just CRUD</h4>\n<p>This wasn’t a simple calendar system. Scheduling involved:</p>\n<ul>\n<li>geography and routing</li>\n<li>clinician availability</li>\n<li>time windows and constraints</li>\n<li>last-minute changes and exceptions</li>\n</ul>\n<p>Even small inconsistencies could break downstream workflows. The challenge was keeping the system flexible while still behaving predictably.</p>\n<hr>\n<h4>2. Frontend / backend alignment</h4>\n<p>In a workflow-heavy system, the UI is only as good as the backend contracts behind it.</p>\n<p>There were cases where:</p>\n<ul>\n<li>the UI assumed one behavior</li>\n<li>the backend responded differently under edge conditions</li>\n</ul>\n<p>Fixing this wasn’t about rewriting everything — it was about tightening contracts and making system behavior more explicit and reliable.</p>\n<hr>\n<h4>3. Scaling without overengineering</h4>\n<p>As the product evolved, there was a constant tension between:</p>\n<ul>\n<li>adding new workflow capabilities</li>\n<li>keeping the system maintainable</li>\n</ul>\n<p>The goal wasn’t to introduce complex architecture — it was to <strong>make practical improvements that actually reduced operational risk</strong>.</p>\n<hr>\n<h4>4. Healthcare-grade expectations</h4>\n<p>Even though this wasn’t a clinical system, it still lived in a domain that requires:</p>\n<ul>\n<li>strong reliability</li>\n<li>clear permissions and access control</li>\n<li>integration readiness (EMRs, APIs, etc.)</li>\n</ul>\n<p>Engineering decisions had to reflect that level of trust.</p>\n<hr>\n<h3>Accomplishments</h3>\n<p>This project pushed me more toward <strong>building dependable systems rather than just features</strong>.</p>\n<ul>\n<li>Improved how I think about workflow-heavy product design.</li>\n<li>Got stronger at identifying weak points in system behavior rather than just code.</li>\n<li>Learned how small improvements in reliability can have outsized impact in operations software.</li>\n<li>Contributed to a system where engineering quality directly affects real-world outcomes.</li>\n</ul>\n<hr>\n<h3>Tech Stack</h3>\n<p><strong>Frontend</strong></p>\n<ul>\n<li>React</li>\n<li>TypeScript</li>\n</ul>\n<p><strong>Backend</strong></p>\n<ul>\n<li>Node.js</li>\n<li>REST APIs</li>\n<li>Async/background job processing</li>\n</ul>\n<p><strong>Infrastructure</strong></p>\n<ul>\n<li>AWS</li>\n</ul>\n<p><strong>Integrations</strong></p>\n<ul>\n<li>EMR integrations</li>\n<li>API-first architecture</li>\n<li>Enterprise authentication (SSO/SAML-ready)</li>\n</ul>\n<hr>\n<h3>What I’d Do Next</h3>\n<p>If I were to continue on this, I’d push deeper into:</p>\n<ul>\n<li>predictive scheduling assistance</li>\n<li>smarter exception handling</li>\n<li>operational analytics and visibility</li>\n<li>decision-support tooling for coordinators</li>\n</ul>\n<p>The foundation is there — the next step is making the system more proactive, not just reliable.</p>\n<hr>","frontmatter":{"title":"Axle Health","slug":"/work/axle-health","company":"Axle Health","role":"Senior Full-Stack Engineer","timeline":"2020 - 2022","summary":"Built full-stack product improvements for a home healthcare logistics platform focused on scheduling reliability, operational visibility, and scalable care-delivery workflows.","liveUrl":"https://www.axlehealth.com/","repositoryUrl":"","screenshots":[{"src":"/images/work/axle-health/clinician-driven-scheduling.png","alt":"Axle Health clinician-driven scheduling interface"},{"src":"/images/work/axle-health/real-time-visibility.png","alt":"Axle Health real-time visibility dashboard"},{"src":"/images/work/axle-health/ai-scheduling.png","alt":"Axle Health AI-assisted scheduling workflow"}],"architecture":null,"roadmap":null,"outcomes":null}}},"pageContext":{"slug":"/work/axle-health"}},
    "staticQueryHashes": ["2009693873","2077189868","3303540520","3505212370","3825832676"]}