Senior Backend & Platform Engineer
Backend and platform engineer with 7+ years across regulated banking, defense, and enterprise fintech. I tend to join complex systems mid-flight: existing codebases, existing constraints, and real operational consequences. My work usually starts with understanding the boundaries: where responsibility lives, what can fail, what must remain compatible, and what the system is promising to the services around it. From there, I take ownership of the parts that need it, whether that means designing a Kafka routing layer end-to-end, extending a distributed execution engine already operating at scale, or working through payment flows where business rules and reliability matter as much as the implementation itself.
Focus areas
Career highlights
A concise look. The full timeline is on the experience page.
Jul 2026 – Present
Senior Backend Engineer, QuickBooks Bill Pay / B2B Payments
Java-based B2B payments service on Intuit's QuickBooks Bill Pay team, following an internal transfer from Data Exchange Platform: hardening payment validation and correctness, and automating stale Payment Instruction lifecycle cleanup.
Jan 2026 – Jul 2026
Senior Backend Engineer, Data Exchange Platform / IDX
Core contributor on a centralized distributed execution engine that processes millions of executions per minute across tens of thousands of API and scraping-based data providers, deployed on AWS and Kubernetes.
Deep dives
Problem, architecture, decisions, and trade-offs across professional and personal work.
Independent architecture ownership, validated after the fact
Designing and owning a centralized Kafka routing layer for a banking platform, independently, and having the design validated by the principal architect after the fact rather than before.
A generated-vs-custom-code boundary that survives contract changes
Building a platform that generates NestJS backend-for-frontend services directly from Swagger/OpenAPI contracts, with a protected boundary that keeps a developer's custom logic intact across contract regeneration.
Incremental legacy modernization with controlled blast radius, not a rewrite
Migrating a 15-year-old legacy tax scripting pipeline onto a modern internal execution engine, provider by provider, using shadow validation to keep blast radius small instead of cutting the whole system over at once.
Outside of work
Self-initiated engineering projects, clearly separate from professional production work.
A local-first, framework-independent, multilingual RAG platform
A personal backend project: a Retrieval-Augmented Generation platform running entirely on local infrastructure (FastAPI, PostgreSQL, Redis, Qdrant, Ollama) with two interchangeable retrieval engines, multilingual Hebrew/English retrieval, and a document lifecycle covering ingestion, deduplication, deletion, re-indexing, and reconciliation.
A multiplayer Battleship game built by an autonomous multi-agent pipeline
A personal project exploring agentic software delivery: a multiplayer Battleship game (React/TypeScript frontend, Spring Boot backend) built through a pipeline of specialized AI agents covering planning, implementation, testing, and review, with no manual steps between requirement intake and PR.
A reusable code-review system with explicit semantics, evidence-backed findings, and deterministic validation
A personal project exploring what it takes to make LLM-assisted code review behave like an engineering system: explicit ownership boundaries, reproducible severity handling, policy enforcement, review and re-review workflows, validation, and portable packaging across coding-agent environments.
Open to backend and platform engineering conversations. The fastest way to reach me is email.