Start with the outcome
Understand what must change for the person or business using the system, then work backward into the architecture.
About Fyxtez
I turn complex problems into working systems.
I'm a Rust and product engineer working across real-time systems, automation, integrations, and the applications people use to turn live data into decisions and action.
Backend depth · Product ownership · Practical infrastructure
The work
Backend depth. Product ownership. Real-world feedback.
For more than six years, I've been building software around live data, external systems, automation, and workflows where reliability directly changes the result. Rust became my core stack because it gives me the control and predictability those systems demand.
I prefer owning the complete path: receiving data, shaping state, exposing a clear boundary, and delivering an interface that makes the system useful. That has taken my work across backend services, browser products, Linux desktop software, and Android applications.
Trading is one of the demanding environments that shaped this way of thinking, but it is not the boundary of my work. The same method applies wherever there is data to understand, a process to improve, and a real problem worth solving.
6+Years building
14Documented systems
RustCore engineering stack
3Web · Desktop · Mobile
A useful perspective
Trading taught me to respect the distance between data and action.
Live markets expose weak assumptions quickly: stale state matters, latency matters, unclear interfaces matter, and failures need to be visible. I bring that discipline to products in any industry—not by forcing trading ideas onto them, but by treating data, reliability, risk, and user decisions as parts of one system.
How I work
Pragmatic architecture with a clear reason to exist.
I care about performance and technical depth, but only when they improve the system people actually depend on.
Keep complexity earned
Use the simplest design that can remain reliable under the actual load, risk, and operational constraints.
Own the complete path
Follow data from ingestion and state through APIs, automation, and the interface where decisions are made.
Build for real use
Good software is understandable, observable, inexpensive to run, and useful after the first impressive demo.
What I bring
One engineer across the complete system.
Strongest in Rust backend and real-time work, with enough product range to carry the result all the way to the user.
01Systems
Rust backend & real-time
Async services, WebSockets, event-driven workers, live data, typed APIs, integrations, and state that has to remain predictable.
02Products
From service to interface
User-facing applications that connect strong backend boundaries to clear workflows across browser, desktop, and Android.
03Delivery
Practical infrastructure
Linux deployments, background services, observability, external APIs, and architecture shaped by cost as well as performance.
Work together
Bring me the problem, the data, and the constraints.
I'm interested in serious Rust, real-time, automation, integration, and product work where useful engineering can create a measurable result.