Software Engineer

Role overview Own backend services end to end — design, implementation, deployment, and on-call quality — for a product that turns location-based questions into reviewed intelligence. The stack is Python and Node.js on Google Cloud, and the work sits at the intersection of data, GIS, and product across multiple Central and Eastern European markets. Latency, correctness, and long-term clarity of the systems all matter.

Responsibilities - Design, build, and operate backend services and APIs in Python and Node.js, covering report workflows, authentication, delivery, and platform integrations. - Run production workloads on GCP — Cloud Run, Cloud Storage, Pub/Sub, Cloud SQL — backed by solid CI/CD, logging, metrics, and alerting. - Own reliability for the paths that matter most: ingestion handoffs, report generation, and client-facing delivery under real load. - Partner with data and GIS engineers so spatial and market data moves cleanly through the product, with clear contracts and no silent failures. - Raise the bar on code review, testing, and operational documentation so the next engineer can take over without archaeology.

Requirements - Three or more years shipping production backend or full-stack software in Python and/or Node.js. - Hands-on ownership of services in the cloud — preferably GCP — including deploy, debug, and recovery. - A habit of writing clear interfaces, thinking in failure modes, and preferring boring, reliable systems over clever ones. - Comfort collaborating with non-engineers such as analysts, researchers, and designers, and translating product needs into shipped work.

Benefits and work setup - Stack: Python, Node.js, GCP (Cloud Run, Cloud Storage, Pub/Sub, Cloud SQL). - Work sits at the intersection of data, GIS, and product across CEE markets.