Backend engineering and consulting for US companies. We architect scalable backend systems, pricing engines, and data pipelines that drive measurable business outcomes.
When your day ends, engineering keeps moving
Omu Systems is backend consulting led by Jacob Parrott, previously a senior backend engineer at Engine (Hotel Engine) and FIS, focused on pricing systems, microservices, and data pipelines that have driven $30M+ measurable revenue impact.
Jacob is based in Japan with full US work eligibility (US citizen, US LLC): straightforward US contracting with a timezone-backed delivery model. Most teams get more useful calendar coverage — deep implementation can advance after your afternoon while collaboration stays in a bounded, predictable live window, with written handoffs so nothing stalls between sessions.
American citizen operating a US-registered LLC. Straightforward contracting for US tech companies.
No junior handoffs. Architecture, implementation, and reviews stay with the same engineer.
Backend systems, pricing logic, and data-heavy pipelines — designed and built to production standards.
Decompose monoliths into well-bounded services. gRPC contracts, domain modeling, and architecture that scales with your business.
Production-grade APIs and services in TypeScript, Node.js, Python, Golang, and Rust. Built for reliability, tested for confidence.
Revenue-critical pricing systems, dynamic margin optimization, and strategy frameworks that drive measurable financial outcomes.
ETL and event-driven pipelines, production observability, and infrastructure as code (Terraform, Kubernetes, CI/CD) when you need the full path to reliable operations.
You get tight agendas and fast follow-through: a bounded live block for decisions and pairing, plus a protected daily block for implementation and reviews — with PRs and written context so your team is never stuck waiting. Live collaboration is anchored to 05:00–09:00 Japan Standard Time, which usually lines up with U.S. afternoons on the prior U.S. calendar day (earlier on Pacific clocks, later on Eastern clocks). Deep work stays protected so meetings do not consume the build time, and the rhythm stays sustainable on both sides.
05:00–09:00 JST for standups, pairing, and decisions that need realtime. On the prior U.S. calendar day that is typically a Pacific afternoon window; for Eastern teams it is usually late afternoon or early evening — still US working hours, without booking your mornings.
13:00–17:00 JST for heads-down building, code review, and documentation — protected time so complex work ships instead of living only in meetings.
PRs, short walkthroughs, and written context so your team is never blocked between live sessions.
A few representative outcomes from production systems at Engine (Hotel Engine) and FIS.
Additional pricing, margin, and experimentation work at the same organizations contributed to the broader revenue impact cited above.
Whether you need to augment your backend team, architect a new system from scratch, or untangle a complex pricing problem — let's start with a conversation.