Senior Software Engineer (Platform)
Posted Updated
Description
- Fresco is looking for a senior engineer to help drive the design and evolution of KitchenOS, our multi-sided smart kitchen platform. This is a deep-IC, design-first role: working alongside a strong platform team, you’ll help shape how ~20 event-driven microservices fit together, make the architecture calls that keep them fast and cheap to run, and raise the abstractions the whole team builds on
- Strong AWS and fluent Python are essential, but the thing that sets this role apart is a system-design mindset: you think in services, events, and trade-offs, not individual functions
- You’ll report to the Engineering Manager for Platform & Firmware and work cross-functionally to design, build, and ship end-to-end platform capabilities
- Shape the architecture of ~20 Lambda-based Python microservices (Python 3.14, aws-lambda-powertools) spanning device control, cooking sessions, media, recipes, and auth
- Design domain event patterns across services with EventBridge, SQS, and SNS, choosing delivery semantics and sync vs async fan-out deliberately, and challenging designs that don’t earn their keep
- Own schema and API design, and improve the shared abstractions the whole team depends on (API Gateway, VPC, cache, DynamoDB tables). Drive direction through design docs and cross-team code review
- Stay close to your services after they ship. Ownership is shared across the team, so like everyone here you’ll take part in the on-call rotation for what you build, supported by self-service deployment and alerting
- Design for cost. Fold efficiency into architecture decisions: right-size memory/timeout, avoid noisy events, fat payloads and chatty calls, and catch cost regressions early via Cost Explorer and Datadog
- Grow the team’s skills through mentoring, knowledge-sharing sessions, and other technical initiatives
- Senior IC: deep technical ownership and influence through code, design, and review, not people management
- Make deliberate architecture trade-offs (event delivery semantics, on-demand vs provisioned, cold-start vs reserved concurrency, sync vs async fan-out) and challenge infrastructure that isn’t earning its keep
- Own infrastructure as code (CDK or Terraform + deployment pipelines) and observability (Datadog APM, Lambda tracing, structured logging, alarms) for what you build
- Share the on-call rotation; everyone owns what they ship
- Engineering hygiene: strict typing, unit tests, Python tooling via uv, ruff, pyrefly, and Poe
Benefits
- Comprehensive healthcare
- Pension scheme access
- Generous paid family leave
- 24 paid annual leave days and the option to work from anywhere for up to 1 month
- Work from home for up to 4 days per week
- Collaborative workspace when in the office
- Stock options
- Professional development stipend of €1000 annually
- Relocation and logistic costs
- Celebrations from cook-alongs to whiskey tastings
- Fluent in English; a clear communicator with both technical peers and less-technical stakeholders
- Strong AI engineering practice: AI tooling is a core part of your workflow, and you can bring the team along on adoption
- Can read IoT/embedded protocol code (CBOR, KSUID, CRC) without panicking
- Strong infrastructure-as-code ownership. We use AWS CDK (writing constructs, not copy-pasting templates); deep Terraform experience transfers well and is equally welcome
- Comfortable across DynamoDB, Valkey (Redis), PostgreSQL (SQLModel/Alembic), and Elasticsearch
- Typically 5+ years designing and building backend systems at scale, with significant time on AWS, spanning services, events, and architecture trade-offs, not just individual functions. We care more about the depth of what you’ve designed than the exact year count
- Fluent in Python with strict typing (Pydantic v2, pyrefly)
- Appliance/IoT protocol knowledge
- LLM integration (prompt pipelines, structured extraction)
- Multi-tenant SaaS platform experience
