About
I have been building software since 1997, and working for myself since 2020. I studied chemical engineering at the Technion, and it shows in how I read a system.
Currently: Independent consultant, open to new projects
Process engineering, pointed at software
A chemical engineer sizes a column with four questions: what goes in, what comes out, where the bottleneck sits, and what breaks when you push past the design assumption. I ask a codebase the same four. A nightly ETL and a filament melting at 215°C are the same problem in different units: inputs, a rate, and a failure you can measure.
I came out of that degree measuring before arguing. In most systems I get called into, the team states the problem in one sentence and nothing in the stack measures it.
What I do
Three fields, one method. I take .NET systems off Framework and onto .NET 10, Linux and containers while they keep serving traffic. I put LLMs inside a stack that already exists, as a step in a process that runs on Monday morning without me in the room. In a print shop it means the tenth part off the machine matches the first.
The clients look nothing alike. A four-person workshop in Holon and a CTO with a fleet of microservices are asking the same question in different vocabulary: where does this process leak, and what is the leak costing me?
How we would work
Start with an assessment. Two weeks: I read the code, sit with the people who maintain it, and hand you a document that ranks the failure modes and gives a plan someone else could execute. After that, a fixed-scope sprint with a date on it, or a retainer that puts me in your architecture calls and on your worst incidents.
I do the work myself. When a project needs more hands I bring people I have worked with for years, and the accountability stays with me.
Away from the keyboard: Holon, a bench of printers that are always mid-job, and an electronics diploma from the nautical school in Acre that still earns its keep thirty years on. Before all of it, sergeant and artillery team commander.
Twenty-five years, short version
- 2020 – now
- Amit Kuzi Consulting. A social network analysis platform, a cashless payment ecosystem, a travel and tourism app, and a long run of .NET Framework backends moved to .NET 10 and containers.
- 2024 – 2026
- GreenRoad Technologies, principal .NET developer and architect. Built the AI-assisted migration rig that converted legacy CoreWCF services to REST APIs, and shipped the collision detection engine with a zero-crash record.
- 2022 – 2023
- Cynet, hands-on team leader. Took the legacy codebase to .NET 6 and led the developers, automation and product people through the move.
- 2020 – 2022
- Microsoft, senior engineer on Power Query Dataflow for Power BI and Power Apps, working the concurrency and redundancy side of a high-availability service.
- 2017 – 2020
- Tzunami, VP R&D. Ran a 25-person team in Kathmandu alongside the team in Israel, on enterprise data migration and recovery.
- 1997 – 2017
- Amimon, CodeValue, Highcon, Cellebrite, Netformx, 3i-MIND, superDimension, OpenTV, Check Point and others. It started at Camtek in 1997, as an application engineer.