Mechanism before modification
I read the system — traffic, memory, contracts — before I touch it. Guesswork is the most expensive dependency.
Renato Leal — Software Developer
Engineering the systems a business runs on.
Software developer focused on platform engineering, AI integrations and reverse engineering. I take systems that were never designed to work together and make them operate as one.
- 400+
- daily users on a platform I architected
- 98%
- lower software cost per seat
- 3
- operating systems from one desktop codebase
01
About
Built from the
mechanism up.
I'm Renato, a software developer based in Curitiba, Brazil. My work sits where products meet the systems they depend on: platforms that carry a company's daily operation, integrations with services that offer no public contract, and AI capabilities wired into real workflows rather than demos.
Before software, I studied electromechanics and mechatronics. That is where I learned to treat every system as a machine — something with inputs, tolerances and failure modes that can be measured. The habit followed me into computer science and still defines how I work: understand the mechanism first, then change it.
Most of what I know was learned under real load. I have been the only engineer behind a production platform, sat with the people who use it every day, and made architectural decisions that had to hold as usage grew.
- Based in
- Curitiba, Brazil · Remote
- Focus
- Platform engineering · AI integrations · Reverse engineering
- Education
- B.Sc. Computer Science · Technical degrees in Mechatronics and Electromechanics
- Languages
- Portuguese (native) · English
Grow it organically
Architecture that scales with evidence, not speculation. Start lean, measure, and invest where the load actually is.
Own the outcome
From the first commit to the person on the other side of the screen. Shipping is the midpoint, not the finish.
02
Results
Work that carries
real weight.
Three chapters, each a step up in scope and responsibility — from a tool built for curiosity to the platform an entire operation depends on.
-
Launch control for a racing simulator
My first real program. In motorsport, a two-step limiter holds the engine at a fixed RPM on the line by cutting ignition, so the car leaves with maximum traction. I wanted that control in Forza, a game that offers nothing like it — so I built it.
-
v1
Hotkeys
A global hotkey modulated throttle input to hold revs on the line. Crude, but it proved the idea worked.
-
v2
A real limiter
The cut-and-restore cycle was refined until revs held steady instead of oscillating around the target.
-
v3
Per-car profiles
The tool read live game state to identify the active car and applied an ignition-cut profile tuned to its engine.
OutcomeIt taught me the pattern I still follow: ship the smallest version that works, then let the problem pull the architecture forward.
-
v1
-
From desktop software to a web platform
As an intern I was handed the migration of an established desktop product to the web — a responsibility well beyond the usual scope of the role. The first months were demanding. They were also where I learned how software is actually built.
- Rebuilt desktop workflows as a web application on ASP.NET, JavaScript and SQL Server, preserving the business rules users depended on.
- Worked directly with clients, turning complaints and workarounds into requirements — and learning to hear the problem behind each request.
- Improved the usability and responsiveness of existing screens, and delivered cross-platform apps with .NET MAUI and Blazor.
OutcomeThe pressure of that project turned theory into engineering judgment, and made the end user a permanent part of how I design.
-
Current · Flagship
The core platform of an operation
Hired straight out of the internship as a mid-level developer, I designed and built — largely on my own — the multi-platform software that became the center of the company. Its revenue flows through it: the platform integrates third-party websites that expose no official integration, and carries the daily work of more than 400 people.
- 400+
- daily active users
- 98%
- lower cost per seat than the tool it replaced
- 3
- desktop operating systems, one codebase
- Lead
- from sole engineer to leading the team
Simplified view. Every arrow is a contract I designed or reverse engineered. Reverse engineering
Mapped undocumented platforms — request signing, session tokens, fingerprint invariants, WebSocket traffic — and rebuilt them as dependable integrations.
Cross-platform desktop client
An Avalonia application for Windows, macOS and Linux with embedded Chromium, isolated persistent sessions per account and a companion browser extension.
Web platform & API
ASP.NET Core and EF Core over SQL Server, JWT authentication, reporting, dashboards and server-driven permissions that reshape the interface without a release.
Real-time event pipeline
Webhooks verified with HMAC-SHA256, persisted before fan-out and delivered over SignalR to access-scoped groups, with idempotency designed per provider.
Zero-latency data capture
Passive network and WebSocket observers feed a durable local outbox; micro-batches reach the API idempotently without delaying the user's action.
AI integration
Platform capabilities exposed to AI agents through a Model Context Protocol server, turning internal operations into tools an assistant can call.
Scale & architecture
Vertical scaling first, then growth driven by real load. Led a module-by-module audit: 76 findings, a phased roadmap and a capacity plan from 100 to 100k users.
Team leadership
Moved from sole engineer to leading the team — setting conventions, reviewing work and turning operational needs into a roadmap.
OutcomeThe company now owns, end to end, the software its operation depends on. Building it is where I learned reverse engineering, vertical scaling, software architecture and how to lead the people who build with me.
03
Stack
Tools I have
shipped with.
Languages, frameworks and infrastructure used in real projects — from managed runtimes down to assembly. Click any of them.
04
Contact
Have a system that needs
to work as one?
Platforms, integrations with services that were never meant to be integrated, or AI that has to work in production. I am glad to talk it through.