We are looking for a Senior Software Architect to help define and evolve the architecture of our SaaS platform and core products. You will work closely with product, delivery, and engineering squads to design scalable, reliable systems, set technical direction, and guide teams in making high‑quality architectural decisions that balance delivery speed with long‑term sustainability.
This is a hands‑on, senior technical leadership role: you will spend most of your time shaping architectures with teams, reviewing designs and critical code, and driving shared standards and patterns across the organization, all in an advance agentic environment.
Responsibilities:
Architecture & technical leadership:
Define and evolve the architecture for key domains in our platform (APIs, services, data flows, integration, observability, security).
Translate business and product requirements into clear, pragmatic technical designs and architecture roadmaps.
Create and maintain architecture artefacts: diagrams, decision records (ADRs), reference implementations, and guidelines.
Evaluate design options and technology choices, articulate trade‑offs, and lead the decision‑making process with stakeholders.
Push forward the agentic mindset and implementation.
Working with squads (R&D):
Partner with squad leads and senior engineers to design solutions, break down complex problems, and keep implementations aligned with the target architecture.
Participate in design / tech reviews, ensuring non‑functional requirements (performance, resilience, security, operability) are addressed early.
Provide hands‑on support where it matters most: spike and prototype critical flows, review complex pull requests, and help debug tricky production issues.
Partnering with Product:
Collaborate with Product to shape technical feasibility, sequencing, and scope for roadmap items and cross‑squad initiatives.
Communicate complex technical topics in simple language to non‑technical stakeholders when discussing roadmap options and trade‑offs.
Standards, reuse, and platform mindset:
Define and promote architecture principles, coding standards, and reusable patterns (modules, libraries, services) that reduce duplication and technical debt.
Champion platform thinking: design services and components that can be safely reused across teams and products.
Drive adoption of shared platform capabilities (observability, CI/CD, authentication, data, DevOps tooling) across squads.
Quality, reliability, and continuous improvement:
Ensure architectures are observable, operable, and resilient by design; partner with DevOps/SRE on deployment, monitoring, and incident response.
Identify areas of high technical debt or architectural risk and lead structured remediation initiatives.
Help define and track technical KPIs (e.g., performance, reliability, incident volume) tied to architecture decisions.
Mentoring and leadership:
Act as a technical mentor and sounding board for senior engineers and tech leads, helping them grow their architecture skills.
Foster a culture of thoughtful design, documentation, and constructive technical debate.
Lead by influence rather than authority: you help teams make better decisions instead of making every decision for them.

We're looking for a Senior Data Engineer to help build next-generation data platform - the lakehouse foundation that will power data processing across the entire product. This is not a "write pipelines on top of someone else's platform" role, and it's not a pure infrastructure role either. It's both, deliberately.

You'll own the platform end to end: the infrastructure it runs on (Spark on Kubernetes, Apache Iceberg, AWS Glue, Airflow), the frameworks and tooling that let dozens of other engineers build on it without reinventing the wheel, and the design of the data pipelines themselves. Everything you build becomes leverage for the teams around you - your abstractions, base images, CI/CD flows, and operational patterns are what make the platform usable at scale.

You'll also own one of the hardest ongoing trade-offs in a high-scale data platform: balancing cost and performance. Compute sizing, storage layout, partitioning and compaction strategy, job scheduling - every decision has a price tag and a latency profile, and you'll be the one making those calls with data.

This role is ideal for an engineer who is equally comfortable debugging a Spark executor OOM on Kubernetes at 10am, designing a clean Python framework API at noon, and modeling the cost impact of a table layout change in the afternoon.



What You'll Do

Platform & Infrastructure

- Design, deploy, and operate our Spark-on-Kubernetes compute platform, including autoscaling, resource tuning, and multi-tenancy considerations.

- Own the lakehouse storage layer built on Apache Iceberg and AWS Glue catalog - table design, partitioning, compaction, schema evolution, and retention.

- Build and operate orchestration on Airflow: DAG standards, deployment flows, environment promotion, and reliability.

- Own production operations of the platform: monitoring, alerting, incident response, and continuous hardening.

Frameworks & Developer Enablement

- Build the code frameworks, libraries, and templates that other engineers use to write pipelines - so that spinning up a new production-grade Spark job is measured in hours, not weeks.

- Define and enforce standards for pipeline structure, testing, observability, and deployment across teams.

- Own CI/CD for data workloads: image builds, artifact promotion, and GitOps-based delivery.

- Act as a technical partner to product and research teams building on the platform - your customers are other engineers.

Data Pipelines & Architecture

- Design and build scalable batch and streaming pipelines processing complex, high-volume datasets from diverse sources.

- Lead large-scale backfills and migration initiatives, ensuring data consistency and integrity across evolving storage and compute platforms.

- Design event-driven data flows over large-scale queue systems (Kafka) for reliable, efficient data movement.

Cost & Performance

- Continuously balance cost against performance: right-size compute, tune queries and jobs, optimize storage layout and file sizes, and choose the correct engine for each workload.

- Build cost visibility and attribution into the platform so trade-offs are made with data, not guesswork.