Software Engineer

Team: Tel-Aviv Office

Location: Tel Aviv

Commitment: Full-Time

Workplace Type: hybrid

Responsibilities:

You’ll transform operational tasks, currently residing in runbooks, Slack threads, and minds, into robust, observable, and maintainable systems. This involves:
 
• Designing and constructing Kubernetes operators and infrastructure microservices that enable self-healing and self-management of the infrastructure.
• End-to-end ownership of shared infrastructure components like Kafka and Debezium, facilitating safe and independent consumption by the rest of the R&D team.
• Developing continuous delivery (CD) pipelines and deployment workflows that minimize time-to-deliver and eliminate bottlenecks between teams.
• Designing systems with self-service in mind, allowing other teams to expedite their processes without initiating tickets.
• Measuring key performance indicators (KPIs) such as ticket volume, hours of manual work per week, time-to-deliver, and the level of friction experienced by consumers.
• This transformation goes beyond automation through scripting languages like Python or Bash. It demands genuine software engineering expertise, encompassing API design, extensibility, failure modes, observability, and upgrade paths.
 

Requirements:

• 5+ years of professional software engineering experience
• Bachelor’s degree in Computer Science, Computer Engineering, or a related field (Preference for top-tier universities).
• Proven experience building and operating cloud-native applications (AWS preferred), with a deep understanding of cloud design patterns.
• Software engineer thinking: you will design for maintainability, you think about interfaces, you care about the experience of whoever uses your work next - whether that's another engineer or a future version of yourself.
• Solid programming skills — Typescript / C# / Java / Go / Python
• Fluency with GitOps / CD patterns and the tooling around them (Argo CD, Helm, etc.)
• Production-first as a state of mind - This sometimes require to function under context switch and several efforts that needs to run in parallel.
• Capability to turn experience into high quality designs - is measure by how you think about failure, observability, consumption and rollout strategy.
• Strong sense of ownership - You don't close the ticket and move on. You follow a thing through until it's right, and you notice when something adjacent is broken even if it's not yours.
• Think systems and KPIs - You understand that a good solution to a recurring problem should eliminate the problem, not just handle it this time. You ask "what does success look like in 6 months?" before you write line one.

Nice-to-Have:

Nice to have: experience building Kubernetes operators (controller-runtime), platform-adjacent work, designing internal services consumed by other engineering teams.

What This Is Not:

- This is not an SRE role focused on incident response and runbook maintenance
- This is not a DevOps role focused on CI pipelines and developer tooling
- This is not a cloud architect role that produces diagrams but doesn't ship code

If you want to build things that matter, own them end-to-end, and measure whether they actually improved the organization's ability to move — this is the role.