Data Platform Architect

See yourself at Twilio

Join the team as Twilio’s next Architect on our Data Substrate team

About the job

Twilio runs on data, and the platform underneath it is entering a major shift. Open table formats, the convergence of lakes and warehouses, tightening privacy regulation, and AI workloads are all changing what a data platform has to do. We’re hiring an Architect to set our direction through that shift and to make sure the systems we build over the next 3-5 years are the right ones.

You’ll own the technical strategy for our data platform, spanning storage, lake and lakehouse architecture, catalog and governance, and privacy-by-design. You’ll work across org boundaries, setting standards that dozens of teams build on and raising the technical bar for the engineers around you.

Responsibilities

In this role, you’ll:

• Own the architecture and multi-year technical strategy for the data platform, including the lake/lakehouse, ClickHouse, Elasticsearch, and governance, and keep them coherent as one platform rather than separate systems. Define where each engine fits (for example, ClickHouse versus open table formats on object storage) and the migration path between them.
• Make and document the major design decisions (ADRs, RFCs) on storage and open table formats, catalog strategy, compute engines, tenancy, data placement, and build-versus-adopt tradeoffs, with cost and performance at petabyte scale as explicit design constraints.
• Set the reference architectures for how our core storage and query engines (ClickHouse, Elasticsearch, and lake engines) are deployed, tuned, scaled and operated as shared platforms, including capacity, cost, tenant isolation, and upgrade strategy.
• Define the reliability model for the platform: availability targets, failure domains, disaster recovery, observability, and incident response patterns that teams can adopt.
• Build privacy and compliance into the architecture, not onto it. Design deletion and right-to-erasure, retention, data residency, and PII classification so they work across the platform’s storage layers, backups, and derived datasets, including data that arrives from upstream streaming systems.
• Drive data governance: classification, catalog and metadata, lineage, access control integrated with our authentication and authorization systems, data contracts, quality and integrity standards, and a catalog teams actually use.
• Review designs and technical direction across the org, and act as the escalation point on hard distributed-systems and performance problems.
• Mentor principal and senior engineers, and grow architectural judgment across the org, not only within one squad.
• Partner with product, security, infrastructure and consuming teams to turn business needs into platform roadmaps, and say no or re-sequence when the tradeoffs require it.
• Track emerging data technologies (such as streaming-first architectures, federated query, and AI-ready data layers) and bring forward the ones worth adopting, with evidence from prototypes or benchmarks.

Qualifications 

Twilio values diverse experiences from all kinds of industries, and we encourage everyone who meets the required qualifications to apply. If your career is just starting or hasn't followed a traditional path, don't let that stop you from considering Twilio. We are always looking for people who will bring something new to the table!

Required:

• Bachelor’s or Master’s degree in Computer Science, Engineering, or a related field, or equivalent practical experience.
• 15+ years of experience in software development or a related field, with at least 8 years in an architecture or senior technical leadership role.
• Proven track record of architecting and delivering large-scale data platforms and setting their technical strategy, on cloud infrastructure such as AWS, deployed with Kubernetes, Terraform and Helm.
• Deep expertise in storage and compute for analytical data: columnar and open table formats, lake and lakehouse architecture, partitioning, indexing, query planning, and how the choices affect cost and performance at petabyte scale.
• Breadth across data storage and retrieval technologies, with hands-on depth in at least two of: analytical/OLAP engines (e.g., ClickHouse), search engines (e.g., ElasticSearch/OpenSearch), and lake or distributed processing engines (e.g., Spark, Trino, Flink). You can reason about when to use each, how they interoperate, and how to migrate between them.
• Working knowledge of streaming systems (e.g., Kafka) and how they interact with downstream storage.
• Practical experience designing data governance at scale: data classification, catalog and metadata management, lineage, and access control integrated with authentication and authorization systems.
• Practical experience implementing privacy and compliance requirements (deletion, retention, residency) across a large, heterogeneous data estate.
• Proficiency in one or more of Python, Java, and Go.
• Track record of writing and driving architecture decisions across multiple teams, and of changing the direction of an organization’s technical roadmap through influence rather than authority.
• Experience elevating engineering standards and mentoring senior engineers across teams.
• Demonstrated commitment to operational excellence: architecting for high availability, observability and incident response in distributed systems, and being credible when a platform is failing in production.
• Strong written and verbal communication, including making a complex tradeoff clear to engineers and to senior leadership.

Desired:

• Experience operating one of these engines (e.g., ClickHouse, ElasticSearch) at scale, including replication, sharding, ingestion behavior, and multi-tenant isolation.
• Experience with catalog and metadata systems (e.g., Unity Catalog, Glue, Polaris, DataHub) and open table format catalog strategy.
• Experience with a platform migration across domains or ownership models, such as moving from central to domain-owned data.
• A track record of measurable cost optimization on large data platforms.
• Networking and network security knowledge.

Location

This role will be remote, and based in the United States. 

Travel 

We prioritize connection and opportunities to build relationships with our customers and each other. For this role, you may be required to travel occasionally to participate in project or team in-person meetings.

What We Offer

Working at Twilio offers many benefits, including competitive pay, generous time off, ample parental and wellness leave, healthcare, a retirement savings program, and much more. Offerings vary by location

Compensation

*Please note this role is open to candidates outside of California, Colorado, Hawaii, Illinois, Maryland, Massachusetts, Minnesota, New Jersey, New York, Vermont, Washington D.C., and Washington State. The information below is provided for candidates hired in those locations only.

The estimated pay ranges for this role are as follows:

• Based in Colorado, Hawaii, Illinois, Maryland, Massachusetts, Minnesota, Vermont or Washington D.C. : $207,200 - $233,100. 
• Based in New York, New Jersey, Washington State, or California (outside of the San Francisco Bay area): $219,360 - $246,780.
• Based in the San Francisco Bay area, California: $243,680 - $274,140.

This role may be eligible to participate in Twilio’s equity plan and corporate bonus plan. All roles are generally eligible for the following benefits: health care insurance, 401(k) retirement account, paid sick time, paid personal time off, paid parental leave.

The successful candidate’s starting salary will be determined based on permissible, non-discriminatory factors such as skills, experience, and geographic location.

Application deadline information

Applications for this role are intended to be accepted until 1/4/2027 but may change based on business needs.