分析工程师
Analytics Engineer
全球可投
开发
🏢 公司 / 雇主
Pleo
🛠 技能要求
SQLdbtGCPBigQueryAirflowSegmentAmplitudeOmniLookerGit
📋 职位要求
- 在我们新的 Analytics Warehouse 中构建和维护 dbt 模型,采用清晰、分层的架构,并在此过程中将逻辑从旧工具迁移出来。 Build and maintain dbt models in our new Analytics Warehouse, using a clean, layered architecture and migrating logic off legacy tools as you go.
- 直接在 Segment 和 Amplitude 中负责埋点方案的实施和 QA,与产品及工程团队紧密合作。 Own tracking plan implementation and QA directly in Segment and Amplitude in close partnership with Product and Engineering.
- 通过将分组和结果数据建模为结构化格式来支持实验,使分析师和产品经理可以直接查询。 Support experimentation by modelling assignment and outcome data into structured formats that analysts and PMs can query directly.
- 在语义层中定义和记录指标,确保单一权威定义,使下游 BI 工具和 AI 应用给出一致的答案。 Define and document metrics in our semantic layer, ensuring a single authoritative definition so downstream BI tools and AI applications yield consistent answers.
- 将 AI 增强的数据建模实践作为编写、审查和迁移代码的标准方式。 Apply AI-augmented data modelling practices as a standard part of how you write, review, and migrate code.
- 与产品经理和分析师合作,将一次性问题转化为持久、可复用的数据模型。 Partner with Product Managers and Analysts to turn one-off questions into durable, reusable data models.
- 通过 dbt 测试、新鲜度 SLA 和主动监控来维护你所在领域的数据质量。 Maintain data quality in your domain through dbt tests, freshness SLAs, and proactive monitoring.
- 扎实的 SQL 和 dbt 经验,能够自如地端到端拥有模型。 Solid SQL and dbt experience, with a clear comfort owning models end to end.
- 对 Segment 或 Amplitude 等基于事件的埋点工具有实际使用经验。 Working knowledge of event-based tracking tools like Segment or Amplitude.
- 具备基于 Git 的开发工作流经验,包括发起和审查 pull request。 Experience with Git-based development workflows, including opening and reviewing pull requests.
- 清晰的沟通能力,能向技术和非技术利益相关者解释数据定义和结构。 Clear communication skills to explain data definitions and structures to both technical and non-technical stakeholders.
- 在日常编码和工作流程中真正常态化地使用 AI 工具。 Genuine day-to-day use of AI tooling as part of your standard coding and workflow routine.
📄 职位描述(中文)
关于 Pleo
混乱的费用管理是件棘手的事,繁琐的流程对所有相关方都是双输局面,不只是财务部门。在 Pleo,我们正在改变这一点。我们打造的支出解决方案让资金管理变得无缝、赋权且出奇地高效——对财务团队和普通员工皆然——我们的愿景是帮助所有企业“超越以往”。其实“Pleo”这个词的意思就是“超出你的预期”,而秉持这一信条正是我们过去 10 年成功的秘诀。如今,我们正处于旅程中的关键时刻;我们采取的每一步都直接影响着 40,000 多家客户、我们的业务以及我们共同的成功。我们需要那些以挖掘客户需求为荣、能将复杂问题转化为简单解决方案、(以尊重的方式)挑战现有做法、并且始终志存高远的人。远大的抱负驱动我们前行,我们不能说自己已经把一切都想明白了。坦率地说,这正是乐趣的一部分!我们可以说的是:我们是一个由 850 多名来自 100 多个国家/地区的成员组成的进取、进步、而且——最重要的——友善的团队,齐心协力共同交付企业支出管理的未来。
关于这个职位
Pleo 的 Intelligence(智能分析)职能涵盖完整的分析图景——产品行为、GTM(市场进入)表现、商业数据科学、财务报告以及运营智能。服务于这些团队的分析工程师拥有支撑这一切的数据建模层:dbt 模型、指标定义以及语义层贡献——分析师、产品团队和 AI 工具都依赖它们来获得一致、可信的答案。你将加入产品智能团队,构建让产品数据可信且可自助使用的埋点、实验和数据建模基础。你将加入一个紧密协作的团队,目前正将我们的分析技术栈迁移到新的 Analytics Warehouse 和 Omni 上,逐步淘汰 Looker 和 Hippocampus 等旧工具。如果你想构建的是他人做产品决策所依赖的基础设施,而不只是对现状做报告,那么这就是适合你的机会。
你将与谁合作及汇报对象
你将向负责产品智能与增长智能的分析经理汇报。你将与产品经理、产品分析师和工程团队紧密合作,从头开始把埋点、实验和指标定义做对。你还将与 Pleo 更广泛的分析工程社区互动,推动建立共享标准,尤其是保持整个组织内指标一致性的语义层。
你将要做的事
在我们新的 Analytics Warehouse 中构建和维护 dbt 模型,采用清晰、分层的架构,并在此过程中将逻辑从旧工具迁移出来。
直接在 Segment 和 Amplitude 中负责埋点方案的实施和 QA,与产品及工程团队紧密合作。
通过将分组和结果数据建模为结构化格式来支持实验,使分析师和产品经理可以直接查询。
在语义层中定义和记录指标,确保单一权威定义,使下游 BI 工具和 AI 应用给出一致的答案。
将 AI 增强的数据建模实践作为你编写、审查和迁移代码的标准方式。
与产品经理和分析师合作,将一次性问题转化为持久、可复用的数据模型。
通过 dbt 测试、新鲜度 SLA 和主动监控来维护你所在领域的数据质量。
你能带来的
扎实的 SQL 和 dbt 经验,能够自如地端到端拥有模型。
对 Segment 或 Amplitude 等基于事件的埋点工具有实际使用经验。
具备基于 Git 的开发工作流经验,包括发起和审查 pull request。
清晰的沟通能力,能向技术和非技术利益相关者解释数据定义和结构。
在日常编码和工作流程中真正常态化地使用 AI 工具。
能从容应对模糊性,并梳理旧逻辑以构建现代化的基础。
这个职位不适合以下情况
你只想写仪表板,而不想接触或拥有底层数据模型。
你需要在主动行动之前有严格的流程和繁重的前期结构。
你倾向于回避数据迁移、清理工作和旧系统重构。
你的前 6 个月
快速上手:掌握我们的 dbt 项目结构、埋点方案和迁移路线图,同时尽早提交小型的、经过代码审查的变更。
承担责任:负责迁移中的某个专门部分,例如某个事件领域或我们的核心实验数据模型。
推动一致性:为你所在领域建立语义层定义,使分析师和产品经理无需自定义变通方案即可自助获取准确的指标。
我们的技术栈背景
数据仓库:GCP / BigQuery(新的 Analytics Warehouse)
数据转换:dbt
编排:Airflow
埋点与产品分析:Segment、Amplitude
BI 与分析:Omni(正从旧工具 Looker 和 Hippocampus 迁移)
语言:SQL
看看这些福利!
你自己的 Pleo 卡(再也不用自己垫付费用了!)
工作日午餐由我们承包——根据你所在办公室的情况,享用供餐或获得午餐补贴。
根据你所在地点提供全面的私人医疗保险(保险选项包括 Vitality、Alan 或 Médis)。
25 天年假外加公共假期,还可通过薪资牺牲(salary sacrifice)方式额外购买 5 天假期。
灵活的办公方式,支持混合办公和完全远程办公。
通过 MyndUp 提供免费的心理健康和福祉支持。
丰厚的带薪育儿假政策,支持不断成长的家庭。
面试流程
初步通话:与我们的招聘伙伴进行 30 分钟
SQL 测试:通过 CoderPad 完成
用人经理面试:与我们的数据与分析经理进行 45 分钟
团队面试与现场案例:通过 CodeSignal 进行数据建模案例
最终面试:与我们的数据与 AI 副总裁进行 30 分钟
透明对我们很重要,所以我们也想分享一些……
🇬🇧 查看英文原文(Original description)
About Pleo Messy spend management is tricky business. And tedious processes are a lose-lose situation for all involved, not just finance. At Pleo, we're changing that. We build spend solutions that make managing money seamless, empowering, and surprisingly effective for finance teams and employees alike - with a vision to help all businesses ‘go beyond’. The word ‘Pleo’ actually means ‘more than you’d expect’, and living by that mantra has been the secret to our success over the last 10 years. Now, we’re at a pivotal moment in our journey; every move we make has a direct impact on our 40,000+ customers, our business, and our collective success. We need people who take pride in uncovering customer needs, who turn complex problems into simple solutions, challenge the way things are done (respectfully), and always aim high. With great ambitions driving us forward, we can’t say we’ve got this whole thing figured out. And frankly, that’s half the fun! What we can say is that we’re a driven, progressive, and, importantly, a kind bunch of 850+ people from over 100 nationalities, all committed to delivering the future of business spending, together. About the role Pleo's Intelligence function covers the full analytical picture - product behaviour, GTM performance, commercial data science, financial reporting, and operational intelligence. The Analytics Engineers who serve these teams own the data modelling layer that all of it runs on: dbt models, metric definitions, and semantic layer contributions that analysts, product teams, and AI tools depend on to get consistent, trustworthy answers. You'll be embedded in the Product Intelligence team, building the tracking, experimentation, and data modelling foundations that make product data trustworthy and self-serve. You'll join a close-knit team actively migrating our analytics stack onto a new Analytics Warehouse and Omni, moving off legacy tools like Looker and Hippocampus. If you want to build the infrastructure that other people's product decisions run on rather than just report on what exists, this is the opportunity for you. Who you'll work with and reporting to You will report to an Analytics Manager leading Product Intelligence and Growth Intelligence. You'll partner closely with Product Managers, Product Analysts, and Engineering to get tracking, experimentation, and metric definitions right from the ground up. You'll also engage with the broader Analytics Engineering community across Pleo to drive shared standards, especially around the semantic layer that keeps metrics consistent across the organization. What you'll be doing Build and maintain dbt models in our new Analytics Warehouse, using a clean, layered architecture and migrating logic off legacy tools as you go. Own tracking plan implementation and QA directly in Segment and Amplitude in close partnership with Product and Engineering. Support experimentation by modelling assignment and outcome data into structured formats that analysts and PMs can query directly. Define and document metrics in our semantic layer, ensuring a single authoritative definition so downstream BI tools and AI applications yield consistent answers. Apply AI-augmented data modelling practices as a standard part of how you write, review, and migrate code. Partner with Product Managers and Analysts to turn one-off questions into durable, reusable data models. Maintain data quality in your domain through dbt tests, freshness SLAs, and proactive monitoring. What you bring Solid SQL and dbt experience, with a clear comfort owning models end to end. Working knowledge of event-based tracking tools like Segment or Amplitude. Experience with Git-based development workflows, including opening and reviewing pull requests. Clear communication skills to explain data definitions and structures to both technical and non-technical stakeholders. Genuine day-to-day use of AI tooling as part of your standard coding and workflow routine. Comfort navigating ambiguity and untangling legacy logic to build modern foundations. This role is NOT a good fit if You only want to write dashboards without touching or owning the underlying data models. You require rigid processes and heavy upfront structure before taking initiative. You prefer to avoid data migration, cleanup work, and legacy system refactoring. Your first 6 months Ramp up: Master our dbt project structure, tracking plans, and migration roadmap while shipping small, reviewed code changes early on. Take ownership: Own a dedicated slice of the migration, such as an event domain or our core experimentation data models. Drive consistency: Establish semantic layer definitions for your domain so analysts and PMs can self-serve accurate metrics without custom workarounds. Our tech stack context Data warehouse: GCP / BigQuery (new Analytics Warehouse) Transformation: dbt Orchestration: Airflow Tracking and Oroduct Analytics: Segment, Amplitude BI and Analytics: Omni (migrating off legacy Looker and Hippocampus) Languages: SQL Show me the benefits! Your own Pleo card (no more out-of-pocket spending!) Lunch is on us for your work days—enjoy catered meals or receive a lunch allowance based on your local office. Comprehensive private healthcare depending on your location (coverage options include Vitality, Alan, or Médis). 25 days of annual holiday plus public holidays, with the option to purchase 5 additional days through salary sacrifice. Flexible working options supporting both hybrid and fully remote setups. Free mental health and well-being support through MyndUp. Generous paid parental leave policies to support growing families. The interview process Intro Call: 30 minutes with our Talent Partner SQL Test: Completed via CoderPad Hiring Manager Interview: 45 minutes with our Data & Analytics Manager Team Interview & Live Case: Data modelling case via CodeSignal Final Interview: 30 minutes with our VP of Data & AI Transparency is important to us so we also wanted to share some insights about what we’re looking for in applications to ensure you can set yourself up for success! Last time we hired an Analytics Engineer, we received a total of 173 applications but only 10 were selected for an intro call. Some of the key reasons why previous candidates didn’t make it past the application screening stage include: CV writing and content: it was very clear that many of the CVs we saw were very generic and AI generated. There is no issue with leveraging AI to help with CV writing, there was little indication of what real impact the candidates had in their previous experience. You might have heard of the “Achieved X, as measured by Y, by doing Z” formula (credit Laszlo Bock ~2014), this is a great way to give a clear picture of what you have actually worked on. Some link or quick description of the companies you’ve worked with is also a great help. Application care: every single application we receive is reviewed by a human (yes, hundreds of them) because we believe that candidates' efforts should be matched by an equal level of human care. This means that we expect a similar level of attention put into your application. Read and answer the application questions carefully, they make a huge difference in our decision-making process. Profile to role fit: there was misunderstanding about the type of experience we expect from an Analytics Engineer and we received many applications from candidates who had never been exposed to a product-led environment or had been exclusively focused on SQL/dbt work when we’re looking for both technical and stakeholders management and team collaboration experience. To be perfectly clear, this is NOT a Data Engineer role or a Data Analyst role! This is a heavily-driven dbt modelling role, experience in this area is critical. We’ve taken great care in writing this role description to reflect the reality of the job as best as possible, please ensure you read it carefully and highlight on your CV the experience relevant to what