Registry · PA-28EFC9
Senior Backend and DevOps Engineer, Node.js and event-driven systems
Backend engineer who also runs the infrastructure his systems live on. TypeScript and Node.js with Kafka and RabbitMQ at the core, from a production-scheduling engine with an event backbone to messaging platforms that carry traffic for telecoms. On the other side of the deploy: Linux, GCP, AWS, Docker and the CI/CD to get there.
Availability
Available nowProfiles presented within 48 hours
Seniority
Senior ยท 5 years
Stack
TypeScriptNode.jsNestJSNext.jsKafkaRabbitMQRedisPostgreSQLMySQLGCPAWSDockerCI/CDAngularReactStripe
Languages
Spanish (native)English (B1)
- 2026 to 2026 Senior Developer and Solution Architect Jan 2026 to Apr 2026
- Designed a microservices architecture on Express and Next.js joined by a Kafka event backbone, keeping orders, inventory and notifications consistent while decoupled.
- Built the scheduling engine: a Tetris-style optimizer that loads machines, inserts critical orders and shifts existing production.
- Modeled concurrent production between areas with WIP buffers and micro-batches, and real-time traceability that reschedules on reported deviations.
- Automated deployment with Docker.
- 2024 to now DevOps and Senior Developer Jul 2024 to Present
- Runs Linux servers, MySQL and PostgreSQL (hosted and containerized) with migrations and backups, and access and firewall policy.
- Administers GCP (snapshots, load balancers, CDN, instances, IAM) and AWS services (SES, RDS, EC2) for production environments.
- 2021 to 2024 Software Developer Nov 2021 to Jul 2024
- Built a Twilio-style messaging platform on Node.js and Kafka, event-driven, integrating Gupshup, Amazon SES, Meta, Twilio and SparkPost for telecom and call-center clients.
- Developed geolocation-based recommendation services (Turf.js, Google Maps, KMZ processing) for a telecom operator.
- Delivered e-commerce backends on NestJS, Redis and RabbitMQ with React frontends for supermarket and coffee retail chains.
Want PA-28EFC9 on your team?
Tell us about the role. We present the profile within 48 hours.
Why does this engineer carry a code instead of a name?
Policy: the code protects the engineer and keeps your systems free of our signature. Everything you can verify is on this page; the name comes later in the deal, off platform. More in the FAQ.