∘∘∘∘∘∘∘∘∘∘∘∘∘∘∘∘            
   •••••••••        ∘       •••••••••   
••••                ·               ••••
••●●●●              ·             ●●●●••
 •    ●●●           ·          ●●●    • 
 ••      ●●●●       ·      ●●●●      •• 
  •         ●●●●    ·   ●●●●         •  
  ••            ●●●●●●●●            ••  
   •            ····●···            •   
    ∘        ····   ●  ····        ∘    
    ∘∘   ····       ●      ····   ∘∘    
     ∘∘∘∘·          ●         ·∘∘∘∘     
      ∘∘            ●           ∘∘      
        ∘∘          ●         ∘∘        
         ∘∘•        ●       •∘∘         
            ••      ●     ••            
              ••    ●   ••              
               •••  ● •••               
root@alberth
root@alberth: ~v2025.06
// welcome. tap a command below, or type one — 'help' lists the full set
root@alberth ❯
// software engineer · backend

Software engineer. More than six years solving the hard problems.

root@alberth

Software engineer — the specialty is backend, in the .NET ecosystem and in whatever the problem calls for. More than six years in production: data contracts, distributed transactions, components other teams come to depend on.

↓ scroll — or drive it from the terminal: cd about · ls systems · cat log

cat about

/about

Software engineer. The specialty is backend, six years in the .NET ecosystem, but what matters is the problem. I've used whatever was available: when the right tool for the job was something else, it was something else.

The work that draws me is the kind with no obvious path: a system that needs to evolve without stopping, a model that doesn't scale, a service contract no one wants to own. I go into those points, understand what's actually blocking, not the symptom, and deliver something other teams come to depend on.

A decision with no cost isn't a decision, it's a preference. Every design chooses what it will have to manage. What concerns me isn't what the solution solves, it's what it brings along.

cat stack

/stack

The tools that ship.

infrastructure
Docker · Kubernetes · Azure · Azure Pipelines
data
PostgreSQL · SQL Server · MongoDB · InfluxDB · Entity Framework · Dapper
application
.NET · C# · Go · C++ · ASP.NET Core · Identity
messaging
Kafka · RabbitMQ · MQTT
observability
Grafana · Azure Monitor
cat log

/log

v2025.01Levva

Strategic integration engineering inside a platform of 60+ microservices. My scope goes beyond writing code: I contribute to architectural decisions, build reusable components that land across multiple systems, run PoCs to validate complex patterns, and help teams modernize legacy services without stopping the product clock.

v2024.01GrupoOrion

Built and owned the core business application end to end. Designed a custom RBAC authorization model for granular platform-wide access control. Architected Saga and Outbox patterns for third-party integrations. Diagnosed a billing bottleneck rooted in the access model — worst-case read time from 1 min 50 sec to 400ms.

v2021.02Meiaum digital

Grew from intern to leading the entire Development department across 100+ delivered projects. Defined development strategy, introduced agile practices, rolled out internal policies that stuck company-wide, and served as the primary interface between clients and technical teams. Also architected and built a full ERP from the ground up.

v2020.01World Skills

National software development competition. Intensive training with C# and Java against timed, high-pressure challenges built around real-world scenarios. This is where problem-solving became a practiced skill, not an assumed one.

build chain
base image
SENAI — Systems Analysis and Development, Technical Degree (2018–2021)
rebuild
ESTÁCIO — Systems Analysis and Development, B.Sc. (2023–2026)
current branch
IESB — Computer Science, B.Sc. (2024–2028, in progress)
next
PUC Minas — Distributed Software Architecture, Postgrad (2026–2027, in progress)
ls decisions/

/decisions

decisions/
cat dispatch

/dispatch

No transmissions yet. The API's still being built.

Unhandled Exception: System.NotImplementedException
   at Root.Dispatch.Render() in /dispatch.cs:line 1
   This section is under development.
cat off.sh

/off.sh

Outside the stack.

robotics
Currently finishing a robotic arm. Hardware has its own debugging rhythm — slower than software, and more unforgiving.
homelab
Self-hosted infrastructure at home. A practical environment for testing deployment patterns, networking configurations, and observability setups outside of work constraints.
AI
Following the engineering closely. Inference optimization, local model behavior, what actually holds up at the edge under production constraints.
reading
Technical literature and systems thinking. Currently working through algorithm fundamentals alongside distributed systems material.
contact

/contact

If you're looking at this from a hiring context, feel free to reach out directly. I respond to everything.

alberth.dev · software engineer · backend & distributed systems · v2026.06