• Own the full lifecycle of CRM Bulk Import: orchestration workers, the external-import read proxy, mapping layers, and the integration seam with downstream HighLevel services • Design and evolve the import pipeline — Pub/Sub topics, Trigger and Import workers, batch hydration, and ID-mapping in Redis — for correctness and throughput • Build and scale stateless proxy services (NestJS) that talk to third-party CRM REST APIs (HubSpot today; Salesforce, Pipedrive, Zoho next) with Bearer-token auth, pagination, batch reads, and rate-limit handling • Tackle distributed systems concerns: idempotent imports, retries, partial-failure resumption, dedup, fair-use across tenants, and backoff against upstream rate limits • Keep the integration layer CRM-agnostic: clean client abstractions, mappers, app-id resolution, and a guard/interceptor seam that stays untouched as new CRMs land • Design the import data contracts — raw vs mapped response modes, camelCase transform rules, exclusion lists — and keep them stable for worker callers • Improve performance and reliability of large imports (millions of records per run) through batching, paging, parallelism, and smart write-side fan-out • Ship end-to-end when needed — including UI changes in Vue (import progress, error reporting, mapping setup) — without blocking on cross-functional handoffs • Instrument the system: traceIds, structured logs, metrics, and SLOs that make import behavior legible across bulk-actions, external-import, and oauth-api • Drive incident response, postmortems, and the engineering hygiene that keeps a high-traffic, third-party-dependent product healthy

• Own large features end-to-end—from design to production • Drive key architectural decisions • Mentor junior developers • Optimize backend performance • Scale infrastructure • Improve frontend responsiveness • Debug complex production issues

• Own the full lifecycle: translate business requirements into scalable, production-grade solutions • Design and implement frontend and backend systems, APIs, and workflows • Rapidly prototype, validate with users, and iterate to production quality • Ensure performance, reliability, and scalability of systems • Monitor applications, maintain documentation, and improve engineering processes

• We’re building a Trading Terminal— a platform for reviewing and replaying trades, designed for prop firms and traders. It combines order flow visualization with replay, audit, and execution in one system. • We work in a spec-driven way: we plan before we build. • Building real-time market data pipelines (Level 2 data, order book reconstruction) • Developing order flow visualizations (footprints, heatmaps, DOM, profiles, CVD) • Improving the trading interface (charts, DOM, tape, order panel working together) • Preparing live data features for partnerships with prop firms • Integrating with market data providers