Open to senior and staff backend engineering roles · Remote · UTC-6
Senior Backend Engineer building reliable Python, AWS, and voice systems.
I'm Adrian Romo. 8+ years building scalable Python APIs, AWS Lambda architectures, Amazon Connect and Lex voice flows, and omnichannel integration frameworks for enterprise virtual support platforms — Slack, Microsoft Teams, Google Chat, and Webex.
Experience
40–60%
Help-desk call volume reduction at Espressive's enterprise virtual support agent.
0
Critical security vulnerabilities maintained over 2 years across enterprise integrations.
8+ yrs
Backend engineering across enterprise SaaS, fintech tooling, and voice automation.
Selected work
Engineering case studies
A few systems I've designed, shipped, and operated. Stack, role, and outcome — links open the full write-up.
Homelab Ops
Self-hosted stack behind Traefik + Authentik
Omni-Router
Channel-agnostic conversation backbone
Voice Orchestrator
Amazon Connect + Lex + Lambda fulfillment framework
Technical expertise
What I work with
Tools and platforms I reach for, grouped by where they show up in the work.
Backend
- Python
- Django
- Flask
- REST APIs
- Celery
- Object-Oriented Programming
- Pytest
Cloud / AWS
- AWS Lambda
- Multi-region deployments
- S3
- IAM
- Docker
- Kubernetes
- Terraform
- CI/CD pipelines
Voice / IVR
- Amazon Connect
- Amazon Lex
- Amazon Polly
- Speech-to-text / Text-to-speech
- NLP
- Asynchronous IVR flows
Integrations
- Slack
- Microsoft Teams
- Google Chat
- Webex
- Enterprise application integration
- Authentication / MFA
- Secrets handling
Databases / Infrastructure
- Postgres
- Redis
- SQL
- Schema design
- Data migration
- Performance optimization
- SonarQube
Writing
Recent technical writing
Architecture notes, project logs, and engineering reflections.
Building Voice Integrations on Top of Async Chatbots
What breaks when you front an async chatbot with Amazon Connect + Lex, and how to keep latency, barge-in, and context handoff sane.
What I Learned Designing Omnichannel Backend Integrations
Shared intent schema, eventually-consistent conversation state, and why the channel should be the last thing your backend knows about.
From Backend Engineer to Technical Leader
What actually changed when I stopped being the one writing the code — and what I wish someone had told me in year four.
About
How I work
I focus on backend systems where reliability, security, and maintainability are non-negotiable — APIs that survive enterprise scale, integrations that hold under real production load, and voice infrastructure that handles support traffic without compromise.
I value clear architecture, secure-by-default patterns, reusable frameworks over repeated fixes, and code that future engineers can safely change. I work cross-functionally with product, QA, and UX, lead code reviews, and ship to multi-region AWS Lambda environments.
More about meContact
Open to senior backend engineering roles.
If you're hiring for Python, AWS, voice, or backend platform work — or want to talk architecture, integrations, or scaling enterprise support — reach out directly.