Product owner

Please login or register as jobseeker to apply for this job.

TYPE OF WORK

Full Time

SALARY

1600

HOURS PER WEEK

40

DATE UPDATED

Jun 23, 2026

JOB OVERVIEW

Product owner / Backlog Administration & Service Desk Specialist (Jira / Jira Service Management)

We are a Dutch SaaS company building an AI-native platform on which organizations run their customer-facing and operational processes — CRM, customer journeys, and workflow management. Our enterprise customers operate in energy, telecom, and field operations, with new verticals coming.

We are looking for a sharp, detail-obsessed specialist to run our service desk and product backlog administration. This is not a ticket-pushing job: customers bring us complex, often vague problems, and you are the one who untangles them, translates them into clear tickets, and thinks along with the customer about the right solution.

You are the first responder on our customer service desks and the guardian of our Jira backlog. You make sure every customer request is acknowledged fast, turned into a well-written ticket, refined until the dev team can pick it up without questions, and kept in sync until it ships. You work alongside modern AI-assisted tooling — we automate the repetitive parts step by step, and you run the process, handle the judgment calls, and keep quality at 100%.

Responsibilities

Service desk first response — acknowledge incoming customer requests within 15 minutes during working hours, across multiple customer service desks (Jira Service Management)
Ticket intake — convert each service desk request into exactly one well-structured Jira ticket (user story, acceptance criteria, correct type/labels/links/epic)
Refinement— drive tickets to Definition of Ready: clarify with stakeholders, attach context, route complex items through the refinement flow, escalate what you cannot resolve
-Complex problem analysis— dig into vague or multi-layered customer problems, ask the right questions, find the root cause, and translate it into clear, actionable tickets — you think along with the customer instead of just logging what they say
Status synchronisation — keep service desk and Jira statuses in sync through the full lifecycle, so customers always see the true state
Delivery & release validation— closely involved in feature delivery: manually test and validate new features and configurations before they reach the customer, and confirm they work after release
Configuration work— resolve configuration-level issues in the platform yourself (settings, templates, setup) instead of routing everything to developers
-Customer communication drafts — prepare release notes and pre/post-release customer updates
Backlog hygiene & reporting — periodic backlog clean-ups, sprint/cycle progress reports, flag bottlenecks and stale tickets
Scrum collaboration— participate in the daily scrum and sprint rituals with our (remote, English-speaking) dev team

Requirements

- 2+ years hands-on experience with **Jira and Jira Service Management** (workflows, boards, linking, JQL is a plus)
- Excellent written English — you write user stories, acceptance criteria, and customer-facing updates
- Extremely detail-oriented and process-driven — status accuracy and ticket quality are the core of this job
- High analytical intelligence (IQ 120+)— you can break a complex, ambiguous problem down to its root cause and concrete next steps. We test cognitive ability as part of the hiring process.
- Reliable availability with overlap with European (CET) morning hours — our response SLA is contractual
- Experience working with Scrum/agile software teams
- Comfortable working with AI-assisted tooling and structured runbooks (we document everything; you follow and improve the playbook)
- Self-starter who escalates early instead of guessing

Nice to have

- Experience with manual QA / acceptance testing of web applications
- Experience configuring SaaS platforms (workflows, templates, settings)
- Experience at a SaaS / software product company
- Confluence experience
- Basic understanding of software release cycles (staging vs production)

How to apply

Reply with:
1. A short note on your Jira/JSM experience (which workflows you managed, team size)
2. One example of a user story + acceptance criteria you wrote (or write one for a feature of your choice)
3. A short description of a complex problem you untangled for a customer or team: what was unclear, what did you do, what was the outcome
4. Your available working hours in CET

Shortlisted candidates will take a cognitive ability test and complete a small trial task.

Applications without these three items will not be considered.

VIEW OTHER JOB POSTS FROM:
SHARE THIS POST
facebook linkedin
  BENCHMARKS  
Loading Time: Base Classes  0.0009
Controller Execution Time ( Jobseekers / Job )  0.0147
Total Execution Time  0.0161
  GET DATA  
No GET data exists
  MEMORY USAGE  
1,512,832 bytes
  POST DATA  
No POST data exists
  URI STRING  
jobseekers/job/Product-owner-1674787
  CLASS/METHOD  
jobseekers/job
  DATABASE:  onlinejobs (Jobseekers:$db)   QUERIES: 13 (0.0095 seconds)  (Hide)
0.0003   SELECT *
                                
FROM exrates
                                WHERE rate_name 
'USD-PHP' 
0.0003   SELECT *
FROM `employer_jobs`
WHERE `job_id` = 1674787
 LIMIT 1 
0.0011   SELECT *
FROM `employers`
WHERE `employer_id` = 770587
 LIMIT 1 
0.0017   SELECT COUNT(*) AS `numrows`
FROM `t_thread` `t`
LEFT JOIN `t_thread_misc` `miscON `t`.`id` = `misc`.`thread_id`
WHERE `t`.`job_id` = 1674787
AND `misc`.`idIS NULL 
0.0005   SELECT e.business_namee.logoe.websitee.rebill_datee.date_added member_datehitsDATEDIFF('2026-08-12',ej.date_added) duration_daysDATEDIFF('2026-08-12',e.rebill_date) duration_rebillej.*, e.deactivate FROM employers eemployer_jobs ej WHERE e.employer_id ej.employer_id AND
                                   ((
e.user_level >= '500' AND ej.date_added <= e.rebill_date)
                                   OR 
e.employer_id '' OR (ej.date_approved <> '2000-01-01' and DATEDIFF('2026-08-12',ej.date_added) <= 14 ))
                                   AND 
e.deactivate != AND ej.deleted AND job_id '1674787' 
0.0008   SELECT *
FROM `employer_jobs_skills` `ejs`
LEFT JOIN `skills_categories` `scON `ejs`.`skill_id` = `sc`.`id`
WHERE `job_id` = 1674787 
0.0007   UPDATE employer_jobs SET hit_counts '***Jun-23-2026=342***Jun-24-2026=101***Jun-25-2026=64***Jun-26-2026=9***Jun-27-2026=3***Jun-28-2026=8***Jun-29-2026=8***Jun-30-2026=8***Jul-01-2026=14***Jul-02-2026=7***Jul-03-2026=4***Jul-04-2026=5***Jul-05-2026=4***Jul-06-2026=3***Jul-07-2026=6***Jul-08-2026=1***Jul-09-2026=4***Jul-10-2026=3***Jul-12-2026=6***Jul-13-2026=4***Jul-14-2026=3***Jul-15-2026=6***Jul-17-2026=4***Jul-19-2026=4***Jul-20-2026=7***Jul-22-2026=3***Jul-23-2026=2***Jul-24-2026=8***Jul-25-2026=7***Jul-26-2026=18***Jul-27-2026=17***Jul-28-2026=16***Jul-29-2026=17***Jul-30-2026=11***Jul-31-2026=17***Aug-01-2026=20***Aug-02-2026=14***Aug-03-2026=11***Aug-04-2026=12***Aug-05-2026=14***Aug-06-2026=9***Aug-07-2026=17***Aug-08-2026=21***Aug-12-2026=1' WHERE job_id'1674787'  
0.0009   UPDATE employer_jobs SET monthly_hits '***Jun-2026=543***Jul-2026=201***Aug-2026=119' WHERE job_id'1674787'  
0.0007   SELECT date_sent FROM jobseeker_sent_emails WHERE jobseeker_id '' AND job_id '1674787' AND status LIKE 'sent%' ORDER BY id DESC  
0.0003   SELECT *
FROM `employer_jobs_skills` `ejs`
LEFT JOIN `skills_categories` `scON `ejs`.`skill_id` = `sc`.`id`
WHERE `job_id` = 1674787 
0.0017   SELECT COUNT(*) AS `numrows`
FROM `employer_jobs`
WHERE `employer_id` = '770587'
AND `date_added` >= '2022-06-08' 
0.0003   select from teasers 
0.0002   SELECT FROM skill_categories WHERE skill_cat_id='' 
  HTTP HEADERS  (Show)
  SESSION DATA  (Show)
  CONFIG VARIABLES  (Show)