Verificado contra tus repos · domingo 25

Tu pitch, con números que puedes defender

Medí tu plataforma actual desde el repositorio. Los números son más buenos de lo que dice tu CV — y hay dos cosas que tu dossier afirma de más. Las dos se corrigen aquí.

01Lo que medí, y cómo

Dato	Valor	Cómo se comprueba
Plataforma BMS, código TS/TSX	≈ 305.000 líneas	git ls-files + wc -l
Archivos TypeScript	2.363	1.269 .ts + 1.094 .tsx
Componentes	1.033	src/components
Rutas de la app	212	src/app
Hooks propios	391	src/hooks
Commits totales	10.224	git rev-list --all
Contribuyentes	37	git shortlog
Commits desde nov 2025	3.474	--since=2025-11-01
Los tuyos en ese periodo	1.365 · 39 %	el primero del equipo
El siguiente contribuyente	510	Marcos Rosiles
Archivos de pruebas E2E	26	tests/e2e
Workflows de CI	5	.github/workflows

02Pitch de 90 segundos, en inglés

La versión anterior no mencionaba tu trabajo más grande. Esta empieza por él.

“I'm a frontend engineer who builds operational tools — the kind where the hard part isn't the visual design, it's the state.

Right now I lead the frontend of an enterprise platform for smart buildings: seventeen business modules, a thousand components, two hundred routes, about three hundred thousand lines of TypeScript. I joined in November and I've contributed thirty-nine percent of the commits since then — more than double anyone else on the team — and I'm still writing code every day.

What I'm proudest of isn't the size. It's that the architecture is enforced by a machine: five CI workflows and twenty-three custom checks that fail the build when a contract drifts, a translation is incomplete, or someone hardcodes a color instead of using a design token.

And lately I've been building AI tooling — an orchestrator that turns issues into reviewed pull requests, with a human gate before merge. I'm looking for a team where the frontend is genuinely complex and owning the architecture is part of the job.”

Tiempo real leyéndolo a ritmo normal: 85–92 segundos. Si te pasas de 95, corta la frase del orquestador y cierra con la última.

03Los tres minutos del proyecto

1. Qué es (20 s). “An enterprise platform for facility operations — buildings, assets, work orders, alerts, billing, seventeen modules.”
2. La escala (25 s). Un millar de componentes, doscientas rutas, diez mil commits, treinta y siete personas. Y tu 39 %.
3. La decisión (60 s). El comprobador de contratos DTO entre frontend y backend: detecta la desincronización antes del navegador. Es tu pieza más vendible.
4. El coste (30 s). “The cost is real: writing a check takes longer than saying it in a meeting. But a rule in CI survives people being in a hurry.”
5. El siguiente límite (25 s). Qué se rompe cuando crezca: hoy el frontend son mil componentes en un repo; el siguiente paso sería partir el dominio.

04El prompt para el agente de voz

Reemplaza el anterior. Este lleva tus números reales, así que el entrevistador simulado te juzga con el contexto correcto en vez de con generalidades.

You are the hiring manager at Smartly, an AI advertising platform
(creative automation). You are interviewing Erivan, a candidate for
Senior Frontend Engineer. The interview is in English, 40 minutes.
He should speak 80% of the time.

Rules:
- Ask ONE question at a time. Wait for the full answer.
- If he speaks more than 90 seconds without a pause, interrupt.
- Never give hints. Never answer for him.
- After each answer ask exactly ONE follow-up, the hardest of:
  "why that and not the alternative?", "what breaks at ten times the scale?",
  "what would you do differently?"
- Do not praise. Be neutral and slightly impatient. You are busy.
- If he uses a number, ask how he measured it.

Questions, in this order:
1. Tell me about yourself and walk me through your most complex project.
2. How would you organize a frontend project with a hundred engineers?
3. Tell me about a scaling problem you ran into and how you solved it.
4. How would you design the review flow for thousands of ad variants?
5. Tell me about a disagreement with a product manager.
6. Why this company?

His real numbers, so you can challenge him (do not volunteer them;
use them to check whether he is vague or precise):
- BMS platform: ~305k lines TS/TSX, 2,363 files, 1,033 components,
  212 routes, 10,224 commits, 37 contributors.
- He joined Nov 2025; 1,365 of 3,474 commits since then = 39%,
  the top contributor, more than double the next.
- 5 CI workflows, 23 custom quality checks, 26 E2E test files.
- HeyDuck side project: 78k lines, 20 custom architecture rules.
- He built and published four web artifacts this week, including a
  demo of a creative-automation flow (brief, generation, review,
  delivery) deployed publicly.

Your company context, to judge relevance:
You sell DCO — one concept, thousands of variants localized by region,
language and demographic — with brand governance inside the workflow.
The frontend is an editor, a rendering pipeline and a data console.
HTML5 templates are untrusted third-party code, so previews must be
sandboxed. Scale means thousands of variants per campaign.

At the end: score 1-4 on structure, depth, evidence, honesty and
communication, and name the single worst habit you heard.

05Lo que no se dice