Senior Backend Software Engineer

Sedric is the AI compliance platform for financial services. Our agentic AI automates oversight across customer communications and marketing — real-time guardrails on calls, pre-approval review on every marketing asset, and post-publication monitoring across partners and channels. Because every customer gets a dedicated compliance model, accuracy goes up, false positives go down, and compliance teams move faster without taking on more risk. Every call we guard, every asset we review, every signal we surface runs through the Core team. It's the pipeline that moves data at Sedric's scale, feeds our analysis engines, and powers the apps our customers depend on every day. As we grow, that load is only getting heavier — more data, more customers, more surface area, and zero room for the Core to be the thing that slows us down. This is your chance to build the infrastructure backbone that has to hold as we scale 10x, sitting exactly where AI meets business impact. You'll report to your Team Lead, based in Tel Aviv on a hybrid model.

Requirements: You're a fit if… You bring both the technical depth and the ownership mindset this role demands. • You have 5+ years of relevant experience in SaaS, ideally in a startup environment • You've built and scaled systems on AWS or another major cloud provider • You're comfortable across Python, Node.js, and TypeScript • You've worked with Docker, Kubernetes, and message queues like SQS or Kafka in production • You know your way around Postgres and Snowflake, or any similar databases, and how to keep them fast under load • You've used tools like Claude and Cursor to move faster, and bonus points if you've integrated LLM flows into a live product • You review code like you mean it — clear opinions, not just approvals • You have a real sense of urgency and don't wait to be told what's next • You collaborate in a way that makes the people around you better, not just yourself You're probably not a fit if… • You wait to be handed tasks instead of finding the next important thing • You treat speed and quality as a tradeoff instead of a discipline • You don't have a point of view on how code should be written or reviewed • You need a fully mapped playbook before you can move • Ambiguity slows you down instead of sharpening your focus