> Markdown version of [/jobs/ext/4790833-analytics-engineers](https://www.wearedevelopers.com/jobs/ext/4790833-analytics-engineers). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # analytics engineers - **Company:** Pendo - **Location:** Raleigh, NC, United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Query Performance, Sql Data Warehouse, Adobe InDesign, Artificial Intelligence, Airflow, Big Data, BigQuery, Software as a Service, Cloud Database, Code Review, Databases, Information Engineering, Extract Transform Load (ETL), Digital Architecture, Dimensional Modeling, Python (Programming Language), Operational Databases, Software Product Management, Software Engineering, SQL Databases, Data Logging, Snowflake, Change Data Capture, Data Management, Virtual Agents, Databricks - **Published:** November 19, 2026 - **Apply:** https://job-boards.greenhouse.io/pendo/jobs/8936989002 ## About the Role * 5-8 years of experience in analytics engineering, data engineering, or software engineering, including end-to-end ownership of production data products * Expert-level SQL, including window functions, complex joins and aggregations, and query performance tuning on large datasets * Hands-on experience with cloud data warehouses or lakehouses (e.g., BigQuery, Snowflake, Databricks) and the ingestion patterns that feed them, including managed ELT tools, batch and incremental loads, and change data capture (CDC) * Proficiency in Python and a workflow orchestrator (e.g., Airflow, Dagster) for building and operating production data pipelines * Deep data modeling skills, including dimensional modeling and semantic-layer architecture (e.g., dbt), and experience consolidating metric definitions across teams * A track record of owning the architecture of production analytics or AI products that others rely on daily, beyond pipelines that feed dashboards * Working knowledge of cloud authentication models and secure-by-design architecture, with experience reviewing code for security exposure * Experience building observability into data and AI products (logging, tracing, usage signals) and diagnosing issues when AI agent output is incorrect * Strong communicator who adapts to different audiences, mentors others, and actively uses AI-assisted engineering tools while helping teammates do the same ## Description Data pipelines and ingestion: Design and maintain reliable ELT/ETL pipelines that bring data from SaaS applications, production databases, and event streams into the warehouse, using batch, incremental, and change data capture (CDC) patterns. Own orchestration, scheduling, and data contracts with upstream source owners.Warehouse modeling and performance: Build layered, well-tested data models (staging, intermediate, and mart layers using dimensional or medallion patterns) in a cloud data warehouse or lakehouse. Tune SQL, incremental models, partitioning, and clustering for cost, performance, and point-in-time correctness. * Security and reliability: Serve as a security reviewer for what the team ships: own the authentication model, review pull requests and service architecture for exposure, and design to minimize attack surface. Help set standards for the scalability, stability, and continuous improvement of the semantic layer and the products built on it. * Mentorship and team elevation: Mentor teammates, as well as engineers from outside the data organization who are contributing to shared infrastructure for the first time. Raise the bar for the team's AI-assisted engineering practices and play an active role in recruiting. * Cross-functional leadership: Where business strategy is set but the technical path is not, define the approach before being asked. Break complex work into clear milestones, help stakeholders understand how it affects them, and lead cross-functional initiatives through to delivery. Success will be measured by * First 30 days: You have completed a diagnostic of the product and semantic layer you will own, covering strengths, gaps, security exposure, and the highest-leverage next improvement. You have a clear point of view on technical direction. * First quarter (90 days): You own the end-to-end architecture of at least one production analytics or AI product. You have shipped a meaningful improvement to it or to the underlying semantic layer, and your design decisions are holding up in production. * Reliable insight delivery: The product you own is accurate and available. When it breaks or produces incorrect results, you treat it as an incident, diagnose the root cause through logs and tracing, and fix it. * Team elevation: Teammates and contributors ship safer, more reliable work because of your reviews, mentorship, and standards, and the team's AI-assisted engineering practices have improved as a result. * Architecture durability: Your data modeling and semantic-layer decisions hold up as new use cases and consumers come online. Metrics are consolidated rather than duplicated, and you catch problems before they escalate., Pendo's Data & AI team operates on a builder-first model. A builder moves without being told what to do next. They see ambiguity and start solving. It is not about technical skill. It is a posture. These are the four competencies we hire for, develop against, and evaluate on: * Bias to Act (Judgment). When a modeling or architecture tradeoff has no clear right answer, you make the call, document your reasoning, and own the outcome. You make security and reliability decisions without waiting for escalation, and you prioritize by business impact, not request order. * Maniacal Focus (Velocity). Improvements ship without stalling in design review. You break complex projects into clear milestones and safely mergeable increments, balancing long-term semantic-layer architecture with near-term delivery. * Hone Your Craft (AI Fluency). AI-assisted engineering is a core part of how you model, test, and review code, and you help raise the team's standard, not just your own. You bring technical depth to AI fluency, engaging on architecture and capability tradeoffs rather than surface-level familiarity. Tools will change; what matters is being comfortable learning while the ground moves. * Team is Pendo (Impact & Ownership). Teams across Pendo depend on your product and the semantic layer beneath it every day. When you see a pattern being misused, you fix the pattern, not just the instance. You mentor on the why, not just the how, including engineers outside the data organization. Your impact extends beyond your own code to the whole team.