7 months ago
Tel Aviv-Yafo, IsraelStaff+
Responsibilities
- Define, evangelize, and own the software architecture vision and strategy for Matia’s unified DataOps platform.
- Lead the design and evolution of complex, large-scale, highly distributed cloud-native systems on AWS.
- Establish architectural standards, best practices, and patterns across engineering teams.
- Collaborate with executive leadership, product management, and engineering teams to translate business strategy into technical roadmaps and architectural solutions.
- Provide hands-on architectural guidance, review critical designs, and contribute to proofs of concept or complex coding challenges.
- Identify and mitigate architectural risks while designing resilient solutions for future technical challenges.
- Mentor senior engineers and architects and provide technical leadership that promotes technical excellence and continuous learning.
- Drive technology selection, evaluation, and adoption in alignment with architectural principles and business needs.
Requirements
- 7+ years of extensive software development experience, including 3–5 years in a dedicated architecture or principal engineering role.
- Proven experience designing and delivering complex, large-scale SaaS platforms or highly distributed systems.
- Deep expertise applying microservices, event-driven, and serverless architecture patterns.
- Mastery of AWS and extensive experience architecting solutions with a broad range of AWS services.
- Strong technical leadership, architectural governance, and mentorship capabilities.
- Ability to make critical, high-level decisions with long-term system impact.
- Exceptional proficiency in TypeScript, Node.js, React, and Python.
- Deep understanding of high-performance SQL and NoSQL database design and Kubernetes.
- Experience with Kafka, SQS, or RabbitMQ for scalable and reliable data pipelines.
- Ability to communicate complex technical concepts clearly and persuasively to engineers and executive leadership.
- Experience in a data tools company involving ETL, reverse ETL, observability, or data cataloging is preferred.
