Clarify
Step 01
Clarify Before Delivery
Start by separating the raw ask, affected screen, user role, workflow, data dependency, deadline pressure, and expected outcome before asking engineering to build.
DiscoveryBRD/SSDAcceptance Criteria
Sanitized evidence trail
Urgent requests to delivery-ready artifacts
Apr 2025-now
158Delivery Cards
Sanitized Trello delivery evidence across urgent intake, development follow-up, UAT, reporting, document, and closing flows.
143Requests Structured
Delivery cards I created to turn short requests, screenshots, issue notes, documents, and follow-up items into trackable work.
120Linked Artifacts
File and link attachments tied to delivery cards, keeping screenshots, requirements, UAT notes, reports, and handover references traceable.
IT product owner CV
Cathleen Etam Nathani
Product Owner/Technology Business Analyst
Product Owner for software and IoT delivery who turns urgent asks, screenshots, UAT feedback, API/device context, billing rules, and handover notes into work teams can verify.
Screens, roles, and data fields clarified
BRD/SSD, UAT, manuals, handover
Billing, reporting, and access issues tracked
Delivery rhythm
Ask
Clarify
Verify
Handover
Sanitized Trello evidence SSD/UAT ready IoT + ERP operations
01 / Profile
I turn messy IT requests into delivery evidence.
I work best where short stakeholder asks, screenshots, deadline pressure, meeting notes, device/API details, billing rules, and UAT feedback need to become visible work that engineering and operations can act on.
Best fit
PO / Technology BAIoT + ERP operationsSSD / UAT / handover
Operating profile
Requests, screenshots, UAT feedback, reports, and handover notes stay tied to delivery work.
Intake
01Scope the ask
Screen, role, data field, and expected result are separated before the request becomes delivery work.
Trace
02Keep the proof chain
Screenshots, notes, checklist items, and decisions stay attached to the same work item.
Close
03Make closure visible
UAT feedback, report handoff, issue status, and close-out references remain visible until wrap-up.
How I work
1
I clarify rough requests by anchoring them to the affected screen, user role, data field, API/device context, or billing rule.
2
I keep screenshots, documents, meeting notes, and checklist items attached to the same work item so decisions do not disappear in chat.
3
I follow work beyond intake by keeping report handoff, UAT feedback, issue status, and closing context visible until the item can be wrapped.
Education
Bachelor of Computing (S.Kom.), Informatics Engineering - Information Technology
Universitas Surabaya (UBAYA)
Graduated
Graduated August 8, 2024
GPA
3.375/4.00
Credits
144 credits across 47 courses
Predicate
Sangat Memuaskan (Very Satisfactory)
Thesis: Street Vendor Recommendation System Using Machine Learning
Relevant coursework
Software EngineeringDatabaseHuman Computer InteractionWeb ProgrammingWeb Framework ProgrammingFull-Stack ProgrammingNative Mobile ProgrammingHybrid Mobile Programming
Study program accreditation: A
02 / Delivery method
How rough requests become verified delivery notes.
I anchor each request to the affected screen, user role, data rule, test note, and handover path before it becomes delivery work.
Specify
Step 02
Make Work Testable
Turn screenshots, feedback, meeting notes, and requirements into user stories, QA checklists, UAT notes, and handover references so stakeholders can verify what has actually been delivered.
User StoriesUATHandover
Close
Step 03
Keep Follow-up Visible
Track open issues, report handoff, UAT feedback, risks, decisions, and release-readiness items clearly so product, technical, and operational teams can move without repeated clarification.
Issue TrackingStakeholder UpdatesDelivery Ownership
03 / Evidence ledger
Sanitized Trello evidence, translated into recruiter-safe claims.
The page avoids raw client names, private links, and credentials. The useful signal is the work pattern: cards, attachments, comments, checklists, API notes, and UAT follow-up stayed connected.
What was messy
Note 01
The delivery board has a large surface: 177 cards across request, development, reporting, done, waiting, hold, meeting, cancel, and document lists. Without a clear action trail, dashboard changes, device/gateway work, ERP-style billing and usage rules, invoice fixes, exports, UAT feedback, and handover notes can become difficult to audit.
What I organized
Note 02
My work account logged 977 visible actions across 158 cards from November 2025 to June 2026, including card creation, attachments, checklists, comments, and status movement. Linked docs and sheets added context for ERP integration API notes, customer/product/invoice references, API endpoints, MQTT fields, downlink queues, device fields, gateway statistics, RTU data, app flow issues, billing/usage notes, pricing/tariff rules, and report/export requests.
What changed
Note 03
The sanitized evidence trail now shows 1,920 board actions, 48 active checklists, 27 board comments, and 120 attachment records, with recruiter-facing CV wording kept client-neutral and free of raw links or credentials.
Working docs
BRD/SSDUser storiesScreen notesUAT feedbackHandover docs
Screens and flows clarified
- Dashboard, device, gateway, and RTU flows
- Billing usage, pricing/tariff, invoice, and report export
- Access roles, API context, data sync, and handover notes
04 / Work record
Evidence-backed PO work, plus UI/UX and web foundation.
The strongest role signal is product ownership and BA delivery in IoT/software operations, supported by UI/UX design practice and earlier web development work.
April 2025 - Present
PT. IoT Kreasi Indonesia
- Structured 143 urgent requests, screenshots, meeting notes, feedback, and issue reports into traceable Trello delivery cards.
- Kept 158 delivery cards visible across request intake, development follow-up, reporting, waiting/hold, meeting, document, and done flows.
- Clarified dashboard, device/gateway, RTU, API, tenant/access, report/export, and UI flow requirements with engineering and operations teams.
- Supported ERP-style billing and usage work covering pricing/tariff rules, invoice follow-up, transaction usage, tenant reports, and ERP API context.
- Turned operational requests into BRD/SSD notes, user stories, acceptance criteria, UAT checklists, user manuals, and handover references.
- Supported Postman, K6, and Locust readiness checks, then translated findings into practical follow-up notes.
January 2024 - Present
Self-Employed
February 2024 - June 2024
Perfect Barbershop
05 / Evidence samples
Work samples grouped by what a PO has to clarify.
These samples focus on work I actually touched: requirements, UAT feedback, troubleshooting flow, ERP-style billing operations, reporting, and handover preparation.
*Note: This evidence trail represents only a subset of client-safe, sanitized tasks recorded for professional demonstration. It is not an exhaustive list of every project and activity completed.
Filter evidence by work type
Showing 5 of 5 samples for all work samples.
Evidence set
Showing the full evidence set.
5 / 5 shown
Smart IoT Dashboard Requirements
Turned scattered operational signals into visible delivery items across request, development, reporting, done, waiting, hold, meeting, cancel, and document flows.
Result
Made delivery status and ownership easier to audit through cards, dated actions, comments, checklists, and attachments.
Sanitized requirement excerpt
Dashboard request converted into acceptance-ready scope
Role: operations/admin user reviewing IoT dashboard data.
Screen: device, gateway, and report/export views.
Scope note: clarify visible fields, export behavior, role access, and expected UAT evidence.
Acceptance check: selected role can inspect the right data, export the expected period, and confirm the issue is ready for handover.
TrelloRequirement TrackingUser StoriesUAT Follow-up
Docs, UAT, and Flow Evidence
Reduced ambiguity by keeping delivery notes attached to the same cards that engineering and operations used for implementation follow-up.
Result
Made product follow-up easier to reconstruct because comments, files, and checklist items stayed tied to dated Trello activity.
Sanitized UAT checklist excerpt
User manual and UAT handover checklist
Confirm user role and menu access before testing.
Compare dashboard data against expected device or report context.
Record screenshot, finding, owner, status, and follow-up date on the same card.
Mark handover-ready only after user note, open issue, and closing reference are visible.
UAT ChecklistMoM NotesReport RequestsAttachment Records
Gateway Monitoring & Troubleshooting Flow
Helped move technical issues from scattered requests into a visible workflow where request status, development progress, and reporting needs could be reviewed.
Result
Improved traceability for technical follow-up by keeping issue context, files, and status movement in one board.
Sanitized triage note excerpt
Gateway or RTU issue framed for engineering follow-up
Observed symptom: dashboard, gateway, meter, RTU, or technician-app behavior does not match expected flow.
Evidence captured: affected identifier, screenshot/file, timestamp, and related report/export need.
Technical context: API/device field, downlink or queue reference, and expected data behavior.
Close condition: engineering response, retest note, stakeholder update, and final status movement are recorded.
Issue TriageGateway/RTUMQTT/Queue ContextPostmanFollow-up Actions
ERP-Style Billing & Usage Workflows
Helped make finance and operations-facing requirements inspectable without turning them into vague requests for engineering.
Result
Shows product ownership across operational workflows where IoT usage data, tenant setup, billing rules, invoices, and exports need to stay aligned.
Sanitized billing rule excerpt
Billing/export requirement framed before implementation
Workflow: tenant or area-based usage review for billing/report export.
Rule context: pricing/tariff period, WBP/LWBP handling, invoice correction, or transaction usage filter.
API context: customer, product, invoice, and report fields need consistent references.
Acceptance check: output matches selected tenant, period, tariff rule, and export/invoice expectation.
ERP API ContextBilling/UsagePricing/Tariff RulesTenant Reports
Responsive App Flow Wireframe
Gives hiring managers a safe visual sample of UI/UX thinking without exposing client files, private Figma links, or unfinished client material.
Result
Shows design judgment through layout structure, hierarchy, and state planning rather than unsupported claims about shipped client results.
Anonymized wireframe artifact
Mobile-to-desktop flow for a task review screen
Mobile state: search/filter, task list, priority marker, and next action are visible above the fold.
Detail state: summary, evidence attachment, owner, status, and acceptance note stay grouped.
Desktop state: list and detail can sit side-by-side for faster review.
Handoff note: components, empty state, loading state, and validation copy are named before development.
Figma ThinkingWireframe FlowResponsive LayoutDeveloper Handoff
06 / Skills
Skills tied to documented delivery work.
My technical, tool, domain, and delivery skills connect to API notes, IoT data fields, ERP-style billing workflows, UAT, handover, and product documentation.
Technical conversation
Programming and data fundamentals that help me discuss feasibility, web-product behavior, and technical constraints clearly.
Python
JavaScript
Java
C#
Kotlin
PHP
HTML
CSS
MySQL
Tools used around delivery
Used for API checks, IoT follow-up notes, performance readiness, interface work, documents, and team follow-up.
Postman
K6
Locust
GitLab
Figma
Microsoft Office
Trello
IoT / ERP domain context
Delivery surfaces I have handled or documented through board evidence, API notes, issue follow-up, and workflow clarification.
IoT dashboard workflows
Gateway/RTU data
MQTT field checks
Downlink queue flow
ERP API context
Billing/usage workflows
Pricing/tariff rules
Tenant access and reports
Product / BA operating methods
The day-to-day methods behind clearer scope, UAT, billing/usage workflows, and project closing.
Product Ownership
Business Analysis
Agile/Scrum
BRD/SSD
UAT
Backlog Support
Issue Triage
IoT Issue Follow-up
Technical Requirement Review
Billing/Usage Workflow
Pricing/Tariff Review
Tenant Access Mapping
Documentation