area · Leadership
Leading with process and calm
People leadership across three stages (a team of 3, a team that grew from 3 to 5–6, and a 4–5 person cell) and process leadership with a documentation standard adopted by 5 developers.
- RFC → ADR → backend reality → atomic steps, across 63 features
- Mentorship, technical direction and hiring input
- Requirement templates with technical context from day zero
- rfc
- adr
- jira
◆ TeamGrowthChart + DocsStandard
Leading means keeping the reasoning visible
People and process: the teams I led, the documentation standard a team of 5 adopted, and the principles behind both.
TeamGrowthChart
SEO Contenidos
Team Lead · 2019 – 2021
team of 3Centria Group
Front End Supervisor · 2021 – 2025
from 3 to 5–6 engineersInlaze
Cell lead · 2025 · ~5 months
4–5 person cell
- at the start
- growth
- depending on the stage (range)
DocsStandard
- 01
RFC
What we want to solve and what the alternatives are.
- 02
ADR
What was decided and why, with its evidence.
- 03
Backend reality
What actually exists on the other side, verified.
- 04
Atomic steps
The implementation in small, reviewable steps.
- features with the full flow
- 63
- developers adopted it
- 5
- repositories where it lives today
- 2
- of the repo's 1,427 documents
- 1,026
Principles
mentoring
Mentoring means keeping the reasoning visible, not just the solution.
I wrote 116 of the 196 RFCs and ADRs of a frontend platform, and mentored a team that grew from 3 to 5–6 engineers.
hiring
A team grows well when whoever leads it helps choose who joins.
At Centria the frontend team grew from 3 to 5–6 engineers over 4 years, with my input on hiring.
decisions
A decision is written down with its evidence and corrected in public if its premise fails.
An ADR of mine assumed a premise that turned out false; the next day I corrected it in writing, keeping a record of the mistake.
No demo: every number in this section is real.
Cases
Cell lead
I led a full 4–5 person cell for about 5 months and then supported the new lead.
Mentoring and hiring
A frontend team that grew from 3 to 5–6 engineers over 4 years, with mentoring, technical direction and hiring input.
Documentation standard
RFC → ADR → backend reality → atomic steps, applied to 63 features, adopted by 5 developers and carried over to a second repository.
Shall we build something reliable?
I reply in English or Spanish.