Registry · PA-D1B6D4
Staff Backend Engineer, distributed systems
Fourteen years designing the systems that cannot go down: hospital networks, public health platforms, retail ERPs. Java and Spring Boot, event-driven architecture, concurrent socket integrations and the observability to prove they hold. Master's in artificial intelligence; ships models as services when the problem asks for it.
Availability
Available nowProfiles presented within 48 hours
Seniority
Staff ยท 14 years
Stack
JavaSpring BootRabbitMQEvent-drivenMicroservicesTCP/IPHL7OraclePostgreSQLAngularDockerCI/CDPython
Languages
Spanish (native)English (B2)
- 2025 to 2025 Senior Systems Consultant Apr 2025 to Oct 2025
- Designed an event-driven auditing architecture on Spring Boot and RabbitMQ that lifted cross-cutting concerns out of the services that used to carry them.
- Turned operational data into real-time analytics the organization uses to monitor and decide.
- Built simulation-friendly interfaces and test harnesses so operational scenarios could be validated before they happened.
- Led two junior developers and coordinated delivery with QA, backend and design.
- 2019 to 2024 Specialist Developer Mar 2019 to Dec 2024
- Core member of the nationwide system team recognized by WHO/PAHO in 2023 for digital health innovation.
- Designed HL7 interoperability over TCP/IP (MLLP) with concurrent socket communication between hospitals and the central platform.
- Built the centralized identity service with Spring Security and JWT for a microservices architecture.
- Introduced CI/CD pipelines and automated testing across the platform.
- 2016 to 2018 Senior Software Developer Apr 2016 to Aug 2018
- Built ERP-integrated workflows for inventory, billing, sales and purchasing.
- Created a national incident-monitoring platform that reduced fraud and tightened operational control.
- Designed the data-integrity mechanisms for enterprise processing across distributed transactions.
Want PA-D1B6D4 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.