Senior .NET & Microservices Developer

Héctor Sulbarán

AI-Augmented Engineer

I build enterprise backend systems, scalable APIs, and AI-agent workflows that help teams ship faster with technical precision.

8+ years. 4 countries. Real production environments.

Héctor Sulbarán wearing a black hoodie in a dark portrait

Methodology

Human-led engineering. AI-augmented execution.

AI accelerates delivery inside a system of context, constraints, and verification. Architecture, security, product decisions, and final acceptance remain under human judgment.

6

projects in production

< 24h

minimum time to production (Faro)

99.7%

latency reduction (HorasBot)

commit velocity (NetSuite)

Keep critical paths independent

External dependencies and supporting layers stay decoupled so the core function continues operating when an integration fails or becomes unavailable.

Meet users in channels they already use

Telegram, WhatsApp, or Slack reduce friction when they already belong to the user's workflow. Architecture adapts to real behavior instead of forcing a new interface.

Use AI only where it adds value

Deterministic tasks remain deterministic. AI reasoning is reserved for ambiguity, analysis, and complex execution; it is never added by trend or by default.

Validate before assuming

Assets, data, requirements, and system responses are verified against real behavior. No input is treated as complete simply because it appears correct.

Require human review at every phase

Planning, implementation, and delivery advance in stages with explicit approval. Every phase has acceptance criteria, technical verification, and a clear point to stop or correct course.

Treat living documentation as the source of truth

Briefs, specs, plans, acceptance criteria, and CLAUDE.md hold context, decisions, and constraints. Execution starts from that documentation system, never from an isolated prompt.

Design governance that prevents errors

Scoped permissions, traceability, guardrails, and explicit approvals turn technical judgment into operating rules. The system does not depend on the model remembering to behave correctly.

Cross-Project Summary

One method applied across six different contexts.

ProjectTypeDelivery pressureHeadline metric
FaroHumanitarian responseExtreme · < 24h to production500+ · 89% · < 3s
HorasBotInternal enterprise automationMedium · daily team adoption15 min → 3 s · 99.7% · 98%
RatioPersonal finance productNo external pressure · full SDD0 · 120+ · 6
WOI 2469B2B/B2C commercial landing pageMedium · client delivery cycle4 B2B · 3d · 10× · ≥95
hsulbaran.devPersonal brand and lead conversionLow · detailed visual iterationLighthouse ≥90 · $0/mes · bilingüe · < 3 semanas
NetSuiteEnterprise AI governanceSustained · active production system482 · 125 · 1–8 → 18–23
Contact