Product Analytics Specialist (Pendo)

Status
Open
Remote policy
Remote
Employment type
Not stated
Salary
45,000-65,000 €
Tech
data
Source
manfred
First observed
2026-10-16 09:55 UTC
Last seen
2026-10-16 09:55 UTC
Consecutive misses
0 of 3

What the posting says

[**Centellic**](https://www.centellic.com/) stands at the center of the legal industry market that it serves, enabling customers to **make better decisions through its journalism, robust data services, and AI tools.** Today, **the company is in the midst of a major data infrastructure transformation that will unlock new value by unifying and enriching data assets in a cloud-native ecosystem.** They've just rolled out **Pendo** across their products, and they've got a very clear problem: *plenty of data coming in, and nobody with the time to make sure it's right.* If your idea of fun is tracking down why an event fired twice on Tuesday and never on Wednesday, keep reading πŸ‘‡ ### 🫡🏻 Let's start with some context about Centellic ;) The organization was formed through the combination of **two major players in the legal information space: ALM and LBR**. Under the Centellic brand, **their flagship**[ **Law.com**](http://law.com) **and**[ **Lexology**](https://www.lexology.com/index) **product offerings continue to operate as market-leading platforms.** This strategic integration brings together a legal intelligence group with 25 years of experience leveraging technology, insights, and analytics, powered by a global team of over a thousand professionals. In addition, **they are truly international, with offices in 5 major cities:** London, Hong Kong, New York, Washington, and Austin. 🌍 The group is in the middle of a serious data transformation. They're unifying and enriching their data in a cloud-native ecosystem and building AI products on top of it. Among them are an AI research assistant that answers questions with citations back to the source documents, and an **MCP server** that lets lawyers query Docket Navigator straight from Claude or Microsoft 365 Copilot πŸ€– **Pendo is a key piece of that puzzle.** It's how product, marketing and sales find out what users *actually* do, not what everyone assumes they do. The implementation is brand new, and right now it sits with two people: **Cara, Head of Applied Innovation**, and the **Group Product Director**. Both are juggling a lot, and Pendo deserves someone who can give it their full attention as it rolls out across the business. **That's you.** You'll own the health and usefulness of Pendo. In practice: * βœ… Every product sends data **the same way**. * βœ… The data **can be trusted**. * βœ… Teams answer their own questions *without opening a request every time.* You know how it goes when nobody owns the tracking plan: `button_click`, `buttonClick`, `Button Clicked` and `btn_clk_final_v2` all end up living happily in the same dashboard. Your job is to make sure that never happens here πŸ˜… And no, they're not looking for someone whose whole career has been Pendo. If you come from **product analytics**, know your way around **instrumentation, event schemas and dashboards**, and want to grow into owning the implementation, **Cara will personally help you get up to speed** with the tool πŸ™Œ On the culture side, **Centellic has always been deeply committed to fostering an inclusive, positive, and inspiring workplace,** winning the **2024 Inspiring Workplaces Award.** They take social responsibility seriously, **actively supporting community and charitable initiatives**. One example is their partnership with the **Swawou School in Sierra Leone**, which provides education for young girls πŸ’› Your week will be split between three things: making sure **the data is right**, making sure **people can use it**, and making sure **new products don't break either of those** πŸ’ͺ **πŸ‘©β€πŸ’» With engineering** Most of your influence will come through **clear tickets**. When a product needs new tracking, you'll define what gets sent, how it's named and which metadata it carries, and hand it over in **Jira** for the team to pick up in their sprint. You'll plug into the engineering teams' agile rituals where tracking work gets planned, so tracking is part of the build from day one and not a patch after release. Before a new feature goes live, you'll do a quick check that what's being sent matches the agreed schema. *Because "we'll add the tracking later" is the analytics version of "works on my machine"* πŸ™ƒ **πŸ“£ With PMs, marketing and sales** The goal is for teams to **serve themselves**, not to queue up behind you. You'll build the dashboards and views they need (in Pendo, in Power BI or through the MCP), show them how to use them, and be around when they get stuck. Think **office hours** rather than a ticket queue. For sales and customer-facing teams, a lot of this will connect with **Salesforce**, so they can see how their accounts are actually using the product. **🧭 With Cara** A regular **1:1** to review priorities, unblock whatever needs unblocking and decide where to focus next. In the early months she'll be very hands-on with you on Pendo itself. Over time, the ownership will be increasingly yours. **πŸ“š How things get documented** Your tracking plan, metadata schema and naming conventions will live in **Confluence**, where engineers and PMs can check them. *If it's not in the tracking plan, it doesn't exist* πŸ˜‡ Work is tracked in **Jira**, and day-to-day communication happens in **English over Teams**. **Must-haves:** * πŸ“Š Experience in **product analytics** with Pendo or a similar tool (Amplitude, Mixpanel, Heap…). * 🧱 A solid understanding of **instrumentation, event tracking, metadata, event schemas and data quality**. * πŸ•΅οΈ Enough technical ability to **debug tracking with engineers**: checking what's being sent, using browser DevTools, spotting why an event doesn't show up. *If you've ever opened the Network tab to find out why something came through as* `undefined`*, you'll feel right at home.* * ✍️ The ability to write **clear, actionable tickets and specs** for engineers. * πŸ“ˆ Experience building **dashboards and reports that non-technical people actually use**. * πŸ‡¬πŸ‡§ **Advanced English**. The team is in the UK and the US, and everything happens in English. * 🌱 Wanting to **own the implementation** and become the company's reference for product analytics. * πŸ“ Being **based in Spain**. **You'd blow their minds if you also...** 🀯 * Have worked **hands-on with Pendo**. * Have experience with **Salesforce** (*big* plus, since a lot of the sales-facing work depends on it). * Have used **SQL**. * Have worked with **Power BI**. * Have set up a **tracking plan or analytics governance across several products**. * Come from a **B2B SaaS** company. πŸ–οΈ 23 days of vacation 🧠 Employee assistance programme and wellness/vision-care budget πŸ’° Pension plan participation πŸ—£ Coaching / therapy sessions πŸŽ‰ Team-building events πŸ’» Equipment: Your laptop and everything you need will be sent to your home

Quality

Completeness: 70%

Not enough history yet to judge honesty signals.

Timeline

  1. *
    #1376022 2026-10-16 09:55 UTC
    Published