11+
Years of experience
Since October 2014.
PLAYER PROFILE / 01 Barranquilla, Colombia
Senior Software Engineer
Open to new opportunities
Senior Software Engineer with 11+ years shipping frontend and mobile products used by millions — leading teams and architecture, and deliberately crossing into backend when the problem demands it.
11+ years across six teams: from broad early-career exposure — backend, frontend, mobile testing — at Janus IT, to leading 5–7 engineers as Tech Lead and Frontend Staff Engineer at Elenas, a social commerce platform that reached 3M+ downloads and 200K+ daily active users.
Today I ship with Spec-Driven Development: precise acceptance criteria, AI-generated first passes, and layer-by-layer validation before anything integrates. Backend (Node.js, Go, Rails) whenever the problem needs it.
11+ Years of experience Since October 2014.
5–7 Engineers led Team size led at Elenas under Scrum.
02 / CAREER STATS
Verified numbers from the career record — every value labeled for what it actually counts, and the Elenas scale figures presented as historical context because the company later shut down.
11+
Years of experience
Since October 2014.
6
Employers
Six employer chapters; Elenas also includes a three-role progression.
5–7
Engineers led
Team size led at Elenas under Scrum.
2
Stores published
The Elenas app was published to Google Play and the App Store.
Historical — Elenas scale at departure (2024)
3M+
App downloads
Historical Elenas figure by the time José left in 2024; the company later shut down.
200K+
Daily active users
Historical Elenas figure by the time José left in 2024; not a current app-store claim.
24s → 7s
Startup time on low-end devices
Performance result from the Elenas work.
14s → 5s
Checkout time
Performance result from the Elenas work.
~30%
Bundle/build optimization reduction
Rollup build-time optimization and code splitting at Monokera.
~25%
Faster test execution
After the Jest → Vitest migration at Monokera.
03 / SEASON LOG
Six employer chapters, October 2014 through July 2026 — the full chronology in order, readable as plain document content.
Oct 2014 – Feb 2016
Barranquilla
First development role: broad exposure across back-end, front-end, and mobile testing — the origin of the UX interest and of the comfort with not being boxed into one layer of the stack.
Frontend and Android Developer Oct 2014 – Feb 2016
Mar 2016 – Mar 2019
Barranquilla
Migrated a legacy web app to a new version using Vue.js.
Frontend and Android Developer Mar 2016 – Mar 2019
Mar 2019 – Sep 2019
Bogotá
Backend-heavy role: built the initial microservices for an order-rating feature using Node.js, Go, and DynamoDB, plus the ratings UI in Vue.js.
Full Stack Developer Mar 2019 – Sep 2019
Oct 2019 – Apr 2020
Bogotá
Real-time systems work: architectural patterns for Firebase communication, a driver–customer chat system, live order tracking with Firestore, and a live video chat feature for an online medical appointments vertical.
Frontend Developer Oct 2019 – Apr 2020
May 2020 – Oct 2024
Remote, Colombia
Four years on a social commerce platform across three roles: mobile architecture, EAS delivery, technical leadership, the performance project, migration of key mobile features to the web, and production-scale work.
Oct 2024 – Jul 2026
Remote, Colombia
Insurance management and sales platform: micro-frontend/monorepo architecture, reusable design-system components, test and build optimization, the Sales Builder Rails service, and Datadog-backed production work.
Senior Frontend Developer Oct 2024 – Jul 2026
04 / ATTRIBUTES
A scouting report in sober text levels — Primary, Strong, Working / Applied. No numeric ratings, percentiles, or years-per-skill claims: levels are written as text so meaning survives grayscale and zoom.
The core of the career: production frontend and mobile work.
Staff-level ownership of frontend architecture and team leadership.
Core workflow using AI tools for spec-driven development and code generation.
Client and server state kept deliberately separate in production apps.
Deliberate backend work taken on when the problem required it.
Testing strategy and release tooling built around real products.
Adjacent technologies and practices evidenced in production roles.
Learning / exploration — not production experience
Studied and practiced outside production — never presented as production experience.
05 / HIGHLIGHTS
Eight separate stories in moment / challenge / result form. Ownership and outcomes are kept exactly as the record states them — no merged claims.
01
MOMENT
An App Store rejection and a Google compliance deadline hit the Elenas app.
CHALLENGE
An outdated Segment SDK shipped with outdated Google Play Services versions.
RESULT
Patched the library to restore compliance under time pressure, then led migration to a modern Segment version once there was more runway.
02
MOMENT
Elenas moved off Expo Classic Updates.
CHALLENGE
Releases required a stronger delivery workflow.
RESULT
Led the Expo Classic Updates → EAS migration and the CI/CD pipeline around it, enabling OTA updates without full store republishing.
03
MOMENT
The Elenas app moved from Expo 47 to Expo 51.
CHALLENGE
Breaking changes affected core functionality.
RESULT
Led the migration under those breaking changes.
04
MOMENT
The most recent Elenas mobile architecture.
CHALLENGE
Maintainability and testability across mobile concerns.
RESULT
Separated data, domain, and presentation layers, keeping Zustand, Context API, and TanStack Query concerns distinct.
05
MOMENT
An internal dashboard still ran on Create React App v3.
CHALLENGE
The dashboard had to move to a current build tool.
RESULT
Led the CRA v3 → Vite migration.
06
MOMENT
An assisted insurance-sales micro-frontend needed a service.
CHALLENGE
The service had to manage its rendered components.
RESULT
Built the Ruby on Rails Sales Builder microservice — and picked up Rails for that need.
07
MOMENT
Elenas mobile performance work.
CHALLENGE
Startup and checkout were slow on low-end devices.
RESULT
Startup moved 24s → 7s and checkout 14s → 5s.
08
MOMENT
Current AI-assisted development.
CHALLENGE
Generated code still needs judgment and correction.
RESULT
Define acceptance criteria, generate a first pass with Claude Code/Cursor/Codex, validate layer by layer, and describe failures precisely enough for correction.
06 / GAME LOG
Seven case studies in box-score form — context, role, stack, and the documented outcome or responsibility. No fake scores, and no links the record can't back.
07 / DRAFT ME
Open to the next chapter
The record above is the honest scouting report for José Cabarcas: a frontend and mobile specialist at Staff level, with real leadership and production outcomes, who deliberately takes on backend work when the problem requires it. If that profile fits your team, the next move is one email away — no form, no middleman.
Education — Diploma in Software Engineering (2016) · B.S. in Systems Engineering (2011–2016), Universidad Simón Bolívar.