I turn ideas into software people rely on.

Lead up to 12 engineers (development, infrastructure/ops, QA) for Open Publishing’s B2B software for publishing houses — while staying hands-on. I set architecture and own the move to the “new world”: cloud, microservices and a modern frontend.

• Own the transition from a part-legacy C++ monolith to AWS, Python microservices and TypeScript/React — a more open, maintainable, extensible platform that keeps the monolith itself leaner and more adaptable.
• New-stack services ship with dramatically faster deploy and feedback cycles — tight need → build → verify → deploy loops and a far better developer experience than waiting on long monolith builds.
• Lead and mentor the team, levelling up engineers — junior and senior — in cloud/AWS, data engineering, React and Python.
• Client-facing capabilities like these — rarely one feature alone, but the whole set — have repeatedly helped win over and impress new publishing-house clients evaluating the platform.

Senior full-stack developer in a distributed, agile Scrum team — full ownership from concept and API design through implementation, tests and deployment. Pioneered the company’s first microservice and its early ML work.

• Built the company’s first microservice (In-Book Marketing) end-to-end — the pioneer work that set the template for every service since.
• Introduced GraphQL to the team’s projects — well received by developers and clients.
• Brought in NoSQL (MongoDB, AWS DynamoDB) where relational models were a poor fit.
• Ran early data-science / ML studies on product and pricing data.

Full-stack developer through a period of rapid feature growth on GRIN’s publishing platform — the work that made it possible to white-label the software as SaaS, which became Open Publishing.

• Delivered a fast wave of full-stack feature expansion (C++ and JavaScript) on the core publishing platform.
• That groundwork enabled white-labeling the software as a SaaS product for other publishers — the seed that grew into Open Publishing, later founded and spun off as its own company.

Built the EJJE (英和和英辞典) English–Japanese dictionary feature end-to-end — both frontend and backend.

• Built the EJJE English–Japanese dictionary end-to-end, including a parser for a proprietary binary file format on the backend.
• Still in production today, largely unchanged.