Senior Platform Engineer — Cloud-Native Backend (Remote/Hybrid)

Frescocooks; Dublin; Hybrid; EUR 90,000 - 130,000; Full time

Benefits offered by this job

Equity

Hybrid/Remote model

Employee Share Option Scheme

Job summary

Fresco is seeking a senior backend engineer to drive the design and evolution of KitchenOS, our multi‑sided smart kitchen platform. This is a deep‑IC, design‑first role where you’ll help shape how ~20 event‑driven microservices fit together and raise the abstractions the team builds on.

Strong AWS and fluent Python are essential; the role emphasizes a system‑design mindset—thinking in services, events, and trade‑offs rather than individual functions.

Qualifications

• 5+ years designing and building backend systems on AWS.
• Fluent in Python with strict typing (Pydantic v2, pyrefly).
• Experience with DynamoDB, Redis, PostgreSQL, and Elasticsearch.
• Strong infrastructure-as-code ownership with CDK and Terraform.
• Comfort reading IoT/embedded protocol code.

Responsibilities

• Shape architecture of ~20 Lambda-based Python microservices across device control, cooking sessions, media, recipes and auth.
• Design domain event patterns across services with EventBridge, SQS, and SNS.
• Own schema and API design, improve shared abstractions (API Gateway, VPC, cache, DynamoDB).
• Stay close to services after they ship; participate in on-call rotation.
• Design for cost; optimize memory, timeouts, and data payloads.
• Grow the team’s skills via mentoring and knowledge-sharing.

Skills

AWS

Python

Event-driven

Lambda

API Gateway

Terraform

CDK

Datadog

DynamoDB

Redis

PostgreSQL

Elasticsearch

IoT protocols

English

Tools

AWS CDK

Terraform

Job description

Fresco is seeking a senior backend engineer to drive the design and evolution of KitchenOS, our multi‑sided smart kitchen platform. This is a deep‑IC, design‑first role where you’ll help shape how ~20 event‑driven microservices fit together and raise the abstractions the team builds on.

Strong AWS and fluent Python are essential; the role emphasizes a system‑design mindset—thinking in services, events, and trade‑offs rather than individual functions.