Backend Engineer (Tel Aviv)

Overview

We are looking for a Senior Backend Engineer to join our R&D team and play a central role in building the core technology behind Parametrix Insurance. Our product activates the moment something breaks in the digital world, when a cloud region goes down, a SaaS platform fails, or a data center experiences an outage. Our systems detect these events in real time and automatically trigger payouts to customers with no paperwork and no delays.

In this role, you won’t be building standard backend features. You’ll help design and scale the monitoring and event-processing architecture that tracks cloud performance globally, analyzes massive data streams in milliseconds, and executes financial transactions with near-perfect accuracy. If you’re excited by the idea of engineering systems that have to stay reliable even when the internet isn’t, this is the place for you.

‍

Key Responsibilities

• Architect and scale Python-based microservices that can handle unpredictable traffic spikes during global outage events.
• Design resilient, fault-tolerant cloud infrastructure in AWS or GCP that keeps running even when parts of the internet aren’t.
• Optimize real-time data pipelines that ingest and process third-party performance data in milliseconds.
• Own the backend development lifecycle, from architectural decisions to production deployment and ongoing improvements.
• Collaborate across Engineering and Product to ensure our monitoring engine and payout systems remain fast, accurate, and reliable.

‍

The Tech Stack You'll Use

• Python: FastAPI, Django, Flask
• Cloud: AWS (Lambda, ECS, S3) or GCP
• Data: PostgreSQL, Redis, Kafka/Kinesis
• Ops: Kubernetes, Terraform, Docker

‍

Qualifications

• Deep experience building production systems in Python.
• 6+ years of backend engineering, with strong architectural skills.
• Understanding ofdistributed systems and how to design for scale, resilience, and performance.
• Believe in Infrastructure as Code and build with automation and reliability in mind.
• Care about observability (logs, metrics, traces) and know how to instrument systems so they never go dark