Backend-leaning full-stack engineer — real-time audio, monitored scraping pipelines, and code review for an open-source voice-AI ecosystem.

Most of what I build turns a raw signal — a phone call, a scraped web page, a spoken request — into something structured enough to trust and fast enough to act on.

Contribute on both sides of the project — building the openhome CLI and reviewing what developers ship with it (51 contributions to date):

CLI development (cli/)

• Authored the Local Link subsystem (cli/openhome/local.py) — the bridge daemon and openhome local {start,stop,status,logs,run} commands that let an ability run a command on the developer's own machine.
• Fixed ability resolution for enable/disable/trigger management, and added validation for trigger-word length and ability-name casing in the creation flow.

Code review

• Review and merge community pull requests against the platform's SDK compliance rules — correct plugin lifecycle usage, storage semantics, and safe handling of LLM-generated output.
• Audit changes the CI pipeline structurally cannot: static checks validate one entry file, so a defect in any other committed source file — a forbidden import, an unsafe pattern — passes CI green and only surfaces at deploy time.
• Trace runtime behavior by hand where the host SDK can't be executed locally, verifying control flow, state handling, and failure paths directly against source.

_{open to backend / real-time systems work}