Scott E.

Backend engineer focused on API integrations, workflow automation, and production-safe systems. Recent work: • Fixed a failing CRM → HRIS pipeline (Blue → Rippling) by resolving mapping issues, duplicate records, and unsafe update logic, restoring reliable synchronization • Converted a manual Jupyter Notebook workflow into a structured GitHub Actions pipeline using Python and API integrations for data extraction, filtering, enrichment, and reviewable output generation • Built and maintain a distributed FastAPI trading backend with broker integrations, real-time alerts, scheduled execution workflows, and 99%+ uptime I work best in systems where reliability matters — backend services, ETL pipelines, API integrations, and automation workflows that need to run predictably in production. I build systems from scratch and also stabilize existing systems when they break. That includes backend architecture, data flows, database design, async processing, and production-safe deployment, as well as debugging undocumented systems and fixing issues that are already costing time and money. While my core focus is backend, I’m also comfortable building clean, functional frontends (React / Next.js) for dashboards, workflows, and internal tools when needed. My stack is primarily Python, FastAPI, TypeScript, PostgreSQL, Redis, and REST APIs, with experience in GitHub Actions, Docker, cloud deployments, and distributed systems. I’ve also worked with PineScript and MQL5 (C++-style trading automation language) in trading systems. I focus on practical engineering: clear logic, strong observability, and modular, well-encapsulated design so systems are easier to debug, extend, and operate reliably. If you need backend work that has to be reliable — not just “working for now” — I’d be glad to help.