Senior software engineer
Building backend systems that last.
I'm Marcos, a backend engineer with 10 years of experience in distributed systems, APIs, and architecture.
Working on authentication and authorization with the Foundations team.
Explore my experience ↓04 / Principles
How I think about building software.
-
Consider the cost of complexity
A repository adds structure, but it also has a cost. Whether it helps depends on the problem.
-
Implicit coupling is hard to spot
Hidden dependencies can make changes risky and problems difficult to diagnose.
-
Name the trade-offs
Document the trade-offs so others understand what the decision means and why it was made.
-
Knowledge silos are an architecture problem
When only a few people understand a system, they can become bottlenecks. Sharing knowledge helps the team maintain it.
-
Agree on guardrails
Let the team shape the foundations and make the rules for critical parts explicit.
-
Write decisions down
Explaining a decision in writing can reveal gaps that were missed in conversation or code review.
01 / Experience
A bit of what I've worked on.
Solo founder
Svelto
Built a Slack-first compliance evidence platform and validated it with CISOs.
Staff engineer & backend tech lead
Rocket.Chat
Led backend engineering work, designed a Matrix-based messaging bridge, and presented architectural analysis to leadership.
Senior engineer
Worked on scheduling and creator economy products, including an AWS serverless backend.
Software engineer
Built APIs, contributed to a messaging platform, and worked on an e-learning product.
02 / Projects
Things I'm building.
Open source · Architecture
Maat
Architecture checks for large codebases. Maat turns coupling rules, module boundaries, and codebase policies into executable checks.
Explore the project ↗03 / Writing
Notes from the work.
Articles about backend systems, architecture, AI, and engineering teams.
Read the articles ↗Contact
Get in touch.
Have a question about something I wrote, or want to talk? Send me a message.