Pendo tells a product team a lot about how people actually use their software, but only if someone sets it up correctly and keeps it that way. That upkeep work, quiet and continuous, is what this role is for.
The position is full-time, paying $81,500 a year, remote with no location tied to it anywhere in the world. The company hiring for this role runs Pendo across multiple product teams and needs someone who can keep the configuration clean as those teams' needs change.
Most of the work centers on configuring and adjusting Pendo: building out workflows, setting up automations, and connecting integrations so the platform reflects what each team actually needs to track. When something breaks or behaves unexpectedly, troubleshooting falls to this role first, before it becomes a wider team's problem. Training also matters here. Internal teams do not always know how to read what Pendo is telling them, and part of the job is showing them.
Data quality gets more attention in this role than people expect going in. A poorly tagged event or a broken integration quietly undermines every report built on top of it, and nobody notices until a stakeholder asks a question the data cannot actually answer. Catching that early, before a leadership deck gets built on bad numbers, is a real and recurring part of the job.
A recent example of the kind of problem this role catches: a checkout flow event stopped firing after a front-end update, and adoption numbers for that flow looked like they had cratered overnight. Nothing was actually wrong with the feature itself. The tracking had simply broken. Diagnosing that quickly, before someone escalates a false alarm to leadership, is exactly the kind of work this seat exists for.
A bachelor's degree in marketing, business, or a related field is the standard requirement, along with two years of hands-on experience configuring and managing Pendo specifically. Two years is enough time to have handled a platform migration or a significant workflow rebuild, which tends to matter more in an interview than years of general analytics experience without direct Pendo exposure.
Where a candidate holds a Pendo certification, that helps, though it is treated as a preference rather than a strict requirement. Problem-solving ability carries more weight day to day, since configuration issues rarely come with a clear manual answer and usually need someone willing to dig through settings methodically, one variable at a time, until the actual cause turns up.
The best fit for this seat is someone who finds satisfaction in getting a system to behave exactly as intended, rather than someone who wants constant variety in the work itself. Pendo administration rewards patience and precision far more than it rewards fast improvisation, and candidates who enjoy troubleshooting for its own sake tend to stay in this kind of role longer than those looking for a stepping stone.
There is a clear growth path attached to a role like this. Specialists who handle Pendo well for a year or two often move toward broader product analytics ownership, taking on tools beyond Pendo itself, or into a platform-strategy role advising on which analytics stack a growing product organization should standardize around. The Pendo-specific skill set is a strong foundation for that wider trajectory, not a ceiling on it.
The role pays $81,500 annually, full-time. Benefits commonly attached to roles like this include health coverage, paid time off, and retirement plan matching, along with a stipend toward ongoing platform training or certification, since Pendo itself updates its features regularly enough that staying current takes deliberate effort.
The work happens inside Pendo itself and a handful of collaboration tools, so remote has never been a limitation for this kind of role. A few overlapping hours with the product and engineering teams are expected, mainly for troubleshooting calls or training sessions, and the rest of the configuration and monitoring work can happen on a self-directed schedule. Remoteroles has placed several specialists into similar setups, and the consistent pattern is a handful of scheduled syncs each week surrounded by quiet, independent platform work.
A typical day might start with a quick review of adoption dashboards, move into a configuration change or two requested by a product team, and close with documentation of whatever changed. Training sessions and troubleshooting calls get scheduled around that core rhythm rather than replacing it.
Team size varies by employer, but this kind of role is rarely a solo function. Product managers lean on the data for planning decisions, engineering occasionally needs a hand instrumenting a new feature correctly from the start, and customer success sometimes asks for adoption numbers ahead of a renewal conversation. Being the one person who understands how the tracking actually works underneath all of those requests carries real weight, even without a large team title attached to it.
Candidates should apply with a resume detailing specific Pendo projects handled before, including the scale of the teams or products supported. A short technical conversation about a past configuration challenge typically follows an initial screen, often walking through a real workflow or automation the candidate built previously. There is no fixed deadline attached to this posting, and the employer is reviewing applications as they arrive, so a complete application with concrete project detail tends to move faster than a generic one.