Backend and integration engineer focused on migration tooling, ETL workflows, API services, and automation. I build software that translates legacy systems, reduces manual work, and holds up when people depend on it.
A few projects that show how I approach migrations, integrations, internal tools, and practical problem solving.
Core contributor on an internal migration system that translates legacy Sage 300 CRE data into Sage Intacct-ready outputs. Helped turn a fragile, query-driven process into reusable stored procedures, functions, validations, and automation layers that supported six client migration tracks and pushed the workflow toward roughly 95% automation.
Built a live integration pipeline connecting Sage 300 CRE to Monday.com through Node.js and 32-bit ODBC. Designed the job flow around diffing, retries, structured payload generation, and idempotent processing so operational teams could trust updates instead of manually reconciling them.
Built a purpose-fit API client for Sage Intacct's XML API when generic tools were slowing the team down. Supports nested field construction, payload preview, auth handling, and object-level CRUD workflows to make debugging, testing, and mapping work faster and less error-prone.
Built as a personal project to support endometriosis management and day-to-day symptom tracking. The focus was simple: make something useful, secure, and easy to trust. I designed the app around authenticated access, audit logging, rate limiting, and careful handling of sensitive health data.
I am strongest where data, APIs, automation, and operations meet — and I am comfortable moving across the stack when the work calls for it.
I do my best work in environments where the problem is not neat yet: legacy systems, manual processes, messy datasets, half-documented workflows, and teams that need something reliable. My default instinct is to understand the business constraint, design the technical path, and automate the pain away.
My strongest lane is backend engineering for integrations, migrations, and operational tooling. That includes ETL workflows, APIs, validation layers, retry-safe processing, logging, reconciliation, and the practical systems work required to make software dependable in finance-heavy environments.
I have worn a lot of hats — engineering, infrastructure, troubleshooting, client-facing delivery, and documentation — which is why I tend to ramp quickly and figure things out when the path is unclear. I am comfortable across the stack, but I market myself backend-first because that is where I create the most value.
I step into unclear systems, trace how they really work, and turn tribal knowledge into repeatable engineering.
I do not automate blindly. I care about logging, validations, reconciliation, and safe re-runs because production work needs trust.
I can work with consultants, accountants, operations teams, and engineers to turn business rules into systems that actually ship.
Looking for backend, integration, migration, and automation engineering work where I can own problems and build reliable systems.