Your Mission
You will be responsible for:
Build and optimize high-performance systems supporting Driver App, Passenger App, and Web Dashboard integrations
Own and implement third-party integrations (e.g., maps, payments, telematics, notifications)
Collaborate closely with mobile, web, and product teams to deliver cohesive end-to-end features
Participate actively in architectural design and technical decision-making
Ensure system scalability, low latency, and high availability for real-time operations
Implement and maintain database structures, data pipelines, and service communication layers
Contribute to CI/CD pipelines, deployment processes, and infrastructure improvements
Maintain a security-first mindset when designing and implementing backend services
- Continuously improve code quality, documentation, and development workflows
Who You Are
You should have:
3–5 years of backend engineering experience, with at least 2 years in production environments serving real users.
Node.js/TypeScript, Go, or Python/FastAPI — Proficiency in one or more of our core backend languages
Solid understanding of RESTful API design, including versioning, error handling, pagination, and security best practices.
PostgreSQL preferred Hands-on experience designing and maintaining relational database schemas.
Familiarity with Redis for caching, session management, and real-time state.
Experience writing unit and integration tests, and a genuine commitment to test coverage as part of the development loop — not an afterthought.
Stripe or equivalent — including webhooks, refunds, and payout flows (Stripe Connect experience is a strong plus for driver payouts). Proven experience integrating payment systems.
Map box, Google Maps, or similar experience working with mapping and routing APIs:
Twilio, Firebase Cloud Messaging, or equivalents. Familiarity with SMS and notification gateways.
- Integration with ERP Systems like Odoo and SAP.
Qualifications & Mindset
You should have:
Experience in mobility, logistics, ride-hailing, or any real-time marketplace platform.
Exposure to event streaming systems such as Kafka, RabbitMQ, or Redis Streams.
Familiarity with observability tooling: Datadog, Prometheus, Grafana, or similar.
Basic understanding of geospatial data and PostGIS — even reading queries written by the Principal Engineer counts.
Experience with background job queues and scheduled tasks (BullMQ, Celery, or similar).
Contributions to open-source projects or a strong engineering blog/portfolio.
Data Privacy
The information in this document is confidential and intended only for the recipient. Any copying, sharing, or reuse without authorization is prohibited and may result in legal consequences.