I work where APIs meet the people trying to use them.

I help own an API platform’s public surface across docs, contracts, SDKs, interfaces, and developer outreach. You can see that work in Payabli’s developer documentation.

• Maintain developer documentation and the OpenAPI specification as living product surfaces, not end-of-sprint artifacts.
• Maintain custom server SDKs across eight languages and work through the awkward differences between their ecosystems.
• Investigate API drift and verify the contract between production behavior, the specification, generated surfaces, and docs.
• Design and implement accessible, responsive UI components that make the documentation journey easier to navigate.
• Build and maintain internal tools that turn recurring checks and editorial work into repeatable systems.
• Work directly with developers, carry their friction back into the product, and close the loop with documentation or code.

Small-team software with a broad remit, direct customer contact, and no room for “another department.”

• Built a TALL-stack and Filament admin system for interactive internal workflows used by non-technical staff.
• Scaffolded and maintained the SQLite database, including schema changes and migrations as those workflows evolved.
• Aggressively optimized accessible interfaces so the important paths worked well for the company’s actual target market.
• Went out to jobsites and spoke directly with paying customers to find friction in the site’s user journey.
• Turned field observations and customer conversations into changes across the website, internal tools, and marketing.
• Handled branding and marketing alongside the technical work, keeping the public presentation and internal system coherent.