Pay
$122K–$190K is typical
The middle half of what similar US postings state. This one doesn’t list pay.
From 339 postings in the last year. Stated ranges, not salaries paid.
San Francisco, California, United States
Live, first seen by us 44 days agoWork setup in the employer’s posting: HybridFrom the employer’s posting
Employment type in the employer’s posting: FullTimeFrom the employer’s posting
Design and maintain core data models, marts, and pipelines
Manage warehouse architecture, permissions, performance, and cost
Document and build metadata, lineage, and context so AI systems can query data
Define dbt patterns, dimensional modeling, naming, and testing standards
Set data governance standards for access, ownership, retention, and sensitive data
design and maintain high-quality data models, marts, and pipelines that make analysis fast, reliable, and reusable
help own warehouse architecture, environments, permissions, performance, cost, data lifecycle, and operational hygiene
own the documentation, semantic context, metadata, lineage, and retrieval patterns that AI systems depend on
define and champion dbt patterns, dimensional modeling practices, naming conventions, tests, and review processes
define standards for access, ownership, lineage, documentation, retention, quality, and sensitive data handling
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications. We count a repost when the same title and location comes back as a new listing within 60 days of the last one coming down. Some hiring systems expire listings on a schedule, so repost rates vary by system.
$122K–$190K is typical
The middle half of what similar US postings state. This one doesn’t list pay.
From 339 postings in the last year. Stated ranges, not salaries paid.
Day 44
Similar jobs usually come down between day 7 and day 51.
At Perplexity, jobs usually come down by about day 81.
From 1,701 similar postings that came down, and 6 of Perplexity’s. Coming down is not always a hire.
14 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
- Experience building semantic layers, metrics layers, metadata systems, or data catalogs. - Python experience for data tooling, automation, orchestration, or quality checks. - Previous experience as an early analytics engineer or data engineer at a high-growth startup.
- 6+ years of experience as an analytics engineer, data engineer, data scientist, or closely related role. - Deep SQL expertise - you can reason about correctness, performance, joins, grain, and edge cases in complex warehouse queries. - Strong data modeling experience - you've worked hands-on with dbt (or a similar transformation framework) in production, and you understand dimensional modeling, data contracts, testing, and how analytical schemas should evolve.
- Experience with RBAC, PII handling, data classification, retention policies, audit workflows, or privacy/security reviews. - Experience with Databricks or other modern data infrastructure. - Experience building semantic layers, metrics layers, metadata systems, or data catalogs.
We're looking for an analytics engineer or data engineer who wants to build the foundation for an AI-native data organization. You'll design core data models, pipelines, semantic layers, data quality systems, governance practices, and warehouse workflows that power the entire company: helping teams make strategic decisions, operate the business, and move faster with trusted data. You'll also make sure those systems are secure, privacy-aware, and legible to AI agents, data scientists, and the rest of the company. This role is for someone who can operate at the boundary of analytics engineering, data engineering, data governance, and internal product. You care about dimensional modeling, dbt standards, cost-aware warehouse design, access controls, privacy, and the details that make data trustworthy. You also believe AI should make the data stack faster, easier to maintain, and more accessible across the company without weakening security or governance. What You'll Do
- Make the warehouse AI-readable - own the documentation, semantic context, metadata, lineage, and retrieval patterns that AI systems depend on to understand and query Perplexity's data correctly. - Own data modeling standards - define and champion dbt patterns, dimensional modeling practices, naming conventions, tests, and review processes. - Lead data governance practices - define standards for access, ownership, lineage, documentation, retention, quality, and sensitive data handling across the analytical warehouse.
- Deep SQL expertise - you can reason about correctness, performance, joins, grain, and edge cases in complex warehouse queries. - Strong data modeling experience - you've worked hands-on with dbt (or a similar transformation framework) in production, and you understand dimensional modeling, data contracts, testing, and how analytical schemas should evolve. - Pipeline ownership - you've built, maintained, debugged, and improved production data pipelines.
Bonus - Snowflake administration, optimization, cost management, or warehouse performance tuning. - Experience with RBAC, PII handling, data classification, retention policies, audit workflows, or privacy/security reviews.
Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.
Already applied? Track this application
Perplexity is AI for people who expect more. On the data team, that means building the systems that make our data reliable, understandable, and usable by both humans and AI.
We're looking for an analytics engineer or data engineer who wants to build the foundation for an AI-native data organization. You'll design core data models, pipelines, semantic layers, data quality systems, governance practices, and warehouse workflows that power the entire company: helping teams make strategic decisions, operate the business, and move faster with trusted data. You'll also make sure those systems are secure, privacy-aware, and legible to AI agents, data scientists, and the rest of the company.
This role is for someone who can operate at the boundary of analytics engineering, data engineering, data governance, and internal product. You care about dimensional modeling, dbt standards, cost-aware warehouse design, access controls, privacy, and the details that make data trustworthy. You also believe AI should make the data stack faster, easier to maintain, and more accessible across the company without weakening security or governance.
What You'll DoBuild the core data foundation - design and maintain high-quality data models, marts, and pipelines that make analysis fast, reliable, and reusable.
Manage the data warehouse - help own warehouse architecture, environments, permissions, performance, cost, data lifecycle, and operational hygiene so the platform scales cleanly.
Make the warehouse AI-readable - own the documentation, semantic context, metadata, lineage, and retrieval patterns that AI systems depend on to understand and query Perplexity's data correctly.
Own data modeling standards - define and champion dbt patterns, dimensional modeling practices, naming conventions, tests, and review processes.
Lead data governance practices - define standards for access, ownership, lineage, documentation, retention, quality, and sensitive data handling across the analytical warehouse.
Build with security and privacy in mind - partner with engineering, security, legal, and finance where needed to ensure data access, sharing, and AI-enabled workflows are appropriate and controlled.
Automate data quality and maintenance - build AI-assisted workflows that detect issues, explain root causes, suggest fixes, generate tests, and reduce manual firefighting.
Improve data team productivity - automate repetitive workflows, improve tooling, streamline development, and make it easier for data scientists and stakeholders to answer questions.
Partner across the company - work closely with data scientists, engineering, product, finance, and GTM teams to translate analytical needs into durable data systems.
Shape tooling decisions - evaluate build-versus-buy tradeoffs, manage vendor relationships when needed, and choose tools that scale with the team.
6+ years of experience as an analytics engineer, data engineer, data scientist, or closely related role.
Deep SQL expertise - you can reason about correctness, performance, joins, grain, and edge cases in complex warehouse queries.
Strong data modeling experience - you've worked hands-on with dbt (or a similar transformation framework) in production, and you understand dimensional modeling, data contracts, testing, and how analytical schemas should evolve.
Pipeline ownership - you've built, maintained, debugged, and improved production data pipelines.
Warehouse management experience - you've worked with warehouse administration, access patterns, permissions, performance tuning, cost management, or operational ownership.
Governance mindset - you think clearly about data ownership, access controls, privacy, retention, lineage, auditability, and the risks of making data too easy to access.
AI-native working style - you already use AI to speed up development, documentation, QA, exploration, and repetitive workflow automation.
Stakeholder fluency - you know how to turn messy analytical requirements into trusted models, metrics, and reusable data assets.
Autonomy and execution - you can take projects from ambiguous problem to production-quality system with minimal oversight.
Operational judgment - you care about reliability, governance, security, cost, and long-term maintainability.
Snowflake administration, optimization, cost management, or warehouse performance tuning.
Experience with RBAC, PII handling, data classification, retention policies, audit workflows, or privacy/security reviews.
Experience with Databricks or other modern data infrastructure.
Experience building semantic layers, metrics layers, metadata systems, or data catalogs.
Python experience for data tooling, automation, orchestration, or quality checks.
Previous experience as an early analytics engineer or data engineer at a high-growth startup.
Own the foundation - your work will determine how fast and confidently the company can use data.
Build for humans and AI - the next generation of data infrastructure needs to be understandable by agents as well as analysts.
High leverage - better models, pipelines, and tools multiply every data scientist and every stakeholder who depends on data.
Small team, broad scope - you'll have room to define standards, choose tools, and ship systems that become company-wide defaults.
New Analytics Engineer postings at the employers we follow are down 20% over the last 6 weeks compared with the 6 before.
Each bar is one week of new postings. The darkest bars are the last 6 weeks.
Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.
We file this job under Analytics Engineer, by the work the posting describes.
Analytics engineers turn raw warehouse data into clean, tested and documented tables that analysts and dashboards can rely on, often with dbt.
Expect strong SQL, data modeling, Git, and a warehouse such as Snowflake, BigQuery or Redshift.
A data engineer gets data into the warehouse; an analytics engineer shapes it once it is there and works closer to the analysts who use it.
The government has no code for analytics engineers, so these figures are for the closest group, database architects, the same group we use for data engineers.
Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
San Francisco, California, United States
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.