Start Date
Immediate
Expiry Date
15 Feb, 27
Salary
65000.0
Posted On
17 Nov, 26
Experience
8 year(s) or above
Remote Job
Yes
Telecommute
Yes
Sponsor Visa
Yes
Skills
Industry
Information Technology & Services
Job Description
Our customers are internal and technical: developers, architects, platform engineers, system administrators
and implementation teams.
You'll understand their workflows, friction points and adoption barriers
deeply, build named relationships with the ones who matter most, and treat their day-to-day
experience — from APIs and SDKs to documentation and onboarding — as the truest measure of
whether the product is working.
Own the problem, the customer and the outcomes for a programme or product line — you set the what and the why, and partner with engineering and architects on the how.
engineers, build deep named partnerships, and turn real evidence into a prioritised, outcomedriven roadmap.
quality, onboarding and adoption — as the measure of product success, and get ahead of
needs customers haven't yet named.
acceptance criteria the team can build against with confidence — and set the standard for
how that's done across the team.
extensibility without getting lost in them.
for how the team applies it — while the product judgement stays yours.
be the product partner they seek out to make hard calls faster and with less friction.
you rather than holding knowledge to yourself
Qualifications
not in features or technology for its own sake.
— and a track record of advocating for their experience and shifting product direction because
of it.
infrastructure products, with a record of independently owning outcomes at programme or
product-line level.
Clear Roadmap And Requirements Others Build Against.
APIs, schemas, logs and code to understand impact (writing production code is not required).
architects and senior stakeholders without authority.
business strategy into clear product direction, and present confidently to leadership.
Job Description
Our customers are internal and technical: developers, architects, platform engineers, system administrators
and implementation teams.
You'll understand their workflows, friction points and adoption barriers
deeply, build named relationships with the ones who matter most, and treat their day-to-day
experience — from APIs and SDKs to documentation and onboarding — as the truest measure of
whether the product is working.
Own the problem, the customer and the outcomes for a programme or product line — you set the what and the why, and partner with engineering and architects on the how.
engineers, build deep named partnerships, and turn real evidence into a prioritised, outcomedriven roadmap.
quality, onboarding and adoption — as the measure of product success, and get ahead of
needs customers haven't yet named.
acceptance criteria the team can build against with confidence — and set the standard for
how that's done across the team.
extensibility without getting lost in them.
for how the team applies it — while the product judgement stays yours.
be the product partner they seek out to make hard calls faster and with less friction.
you rather than holding knowledge to yourself
Qualifications
not in features or technology for its own sake.
— and a track record of advocating for their experience and shifting product direction because
of it.
infrastructure products, with a record of independently owning outcomes at programme or
product-line level.
Clear Roadmap And Requirements Others Build Against.
APIs, schemas, logs and code to understand impact (writing production code is not required).
architects and senior stakeholders without authority.
business strategy into clear product direction, and present confidently to leadership.