Software / Support Engineer
Jan 2025 – Sep 2026
Support Engineer: Jan – Dec 2025 · Software / Support Engineer (Contractor): Jan – Sep 2026
- Reduced support ticket volume by about 50%: built Jira dashboards to measure ticket types and volume, identified the top causes (failed transactions from low Lightning liquidity, deployment errors in production, and repeated frontend issues), took ownership of node liquidity, pushed the infrastructure team to fix the deployment process, fixed recurring frontend issues, and helped train customer-facing teams on common misconceptions about our services.
- Joined technical calls with client developers to help them integrate the company API, and did product demos.
- Resolved hundreds of support tickets for internal and external clients, reproducing issues and investigating with SQL, logs, browser DevTools, client input, and the code on GitHub; separated product bugs from client errors and flagged recurring ones to product as UX improvements.
- Owned the support escalation process in 2026: triaged issues, set priority by customer impact, and assigned the work between myself and a team of 3–4 senior engineers.
- Created Datadog monitors with alerts to Slack and PagerDuty, and followed up on critical incidents with engineering.
- Integrated several external exchanges for price rates, real-time quotes, and order placement.
- Built back office APIs in Go, including user roles and permissions management for customer support.
- Set up the public API documentation portal with Zudoku, generated from Swagger / OpenAPI specs.
- Built a scheduled PostgreSQL cleanup job that reduced a transactions table by about 25%; ran migrations to remove legacy data and reduce costs.
- Managed Lightning Network node liquidity with LND and RTL: channel flow analysis and circular rebalancing.