Hi, I'm
Glinet
I bridge the gap between business strategy, customer insight, and technical execution to build products that drive real impact.
From shipping code to owning outcomes
I started as a software engineer obsessed with elegant systems. Seven years later, I'm obsessed with something harder: building the right product.
Software Engineer
2017 – 2019
Built production apps, discovered the power of clean code and customer impact.
Senior Engineer
2019 – 2021
Designed systems at scale, mentored teams, started asking "why are we building this?"
Technical Lead
2021 – 2023
Led engineering teams, partnered with PMs, started owning outcomes not just output.
Technical Product Owner
2023 – Present
Own the roadmap. Write PRDs. Drive $1.2M ARR. Represent the customer in every sprint.
Technical Product Manager
Next Chapter
Scaling from team-level product ownership to multi-team product leadership.
Why I think differently about product
I speak both languages.
Engineers trust me because I've lived in their world. Executives trust me because I connect tech decisions to business outcomes.
I prioritize with data, not HiPPO.
Every roadmap decision is defensible with evidence — user research, usage data, or explicit trade-off reasoning.
I make engineers' lives better.
Clear requirements, well-groomed backlogs, and zero ambiguity in acceptance criteria. Sprint predictability is a product metric I own.
I obsess about the problem, not the solution.
Half the features I've killed were the right call. The hardest part of product is saying no with conviction.
How I think about product
Product management is not a role — it's a set of disciplines. Here are the ones I actively practice.
Product Discovery
Turning ambiguous problems into validated hypotheses through user research and data analysis.
Product Strategy
Connecting business goals to product decisions with a long-term competitive vision.
Roadmapping
Building stakeholder-aligned roadmaps that balance customer needs with business priorities.
Backlog Management
Keeping engineering teams unblocked with well-groomed, clearly scoped user stories.
Prioritization
Making tough trade-offs with transparent frameworks that earn engineering trust.
Stakeholder Management
Aligning diverse stakeholders through clear communication, roadmaps, and shared metrics.
Customer Research
Understanding real pain points through qualitative and quantitative research methods.
Product Analytics
Defining, measuring, and acting on the metrics that matter for product success.
Go-To-Market
Partnering with sales and marketing to launch features that actually reach customers.
Experimentation
Running rigorous experiments to validate assumptions before full investment.
Product Leadership
Creating alignment, clarity, and momentum across cross-functional teams.
Agile Delivery
Keeping sprint velocity high while maintaining quality and customer focus.
The engineering foundation behind the product
Not a list of buzzwords — a genuine engineering background that lets me have real conversations with architects, platform engineers, and data scientists.
Cloud & Infrastructure
Proficiency scale: These reflect working knowledge from production usage — not certifications. Honest self-assessment matters more than impressive numbers.
Products I've owned, decisions I've made
Real problems. Real trade-offs. Real outcomes. Each case study shows how I think, not just what I shipped.
Each case study walks through the full product process — from ambiguous problem to shipped feature to measured outcome.
Workflow Automation Platform
From manual ops to intelligent automation — 0→1 product build
Identified a manual operations bottleneck costing enterprise clients $450K/year, led a cross-functional team to build an intelligent workflow automation engine that drove $1.2M ARR in first quarter.
Developer Payments API Platform
Building a payments API that developers actually love to integrate
Led the design and launch of a REST + webhook payments API serving 200+ integration partners, achieving 99.98% uptime and a developer satisfaction score of 4.7/5.
EHR Integration Engine
HL7 FHIR integration that saved 3 hours per clinician daily
Drove the technical and product requirements for an HL7 FHIR integration that eliminated manual data entry for 8,000 clinical users across 12 hospital networks.
AI-Powered Feature Suite
Coming Soon — Structuring the AI roadmap for a B2B SaaS platform
Building the product strategy and technical roadmap for integrating LLM-powered features into an existing B2B SaaS platform without disrupting core workflows.
Impact first, responsibilities second
Seven years of building things that matter. Each role moved me closer to owning the product.
- Reduced time-to-market by 35% by introducing outcome-based roadmaps and eliminating scope creep
- Led discovery for a workflow automation feature that drove $1.2M ARR in first quarter post-launch
- Managed backlog of 300+ items, maintained 92% sprint predictability across 8 engineering teams
- Implemented RICE prioritization framework adopted by 3 other product teams company-wide
- Authored 40+ PRDs, user stories, and acceptance criteria with zero ambiguity escalations
How I think about products
Critiques, frameworks, teardowns, and redesigns. Product thinking that goes beyond your current role.
Why Slack's Notification Model Creates Power Users but Frustrates Everyone Else
Slack optimizes for message throughput over attention management, creating a product that feels productive while fragmenting deep work. The "always-on" mental model is a strategic moat that also becomes their biggest churn driver for non-tech users.
The Technical PM Advantage: How to Use Architecture Knowledge to Win Roadmap Arguments
Most PMs treat the engineering backlog as a black box. Technical PMs who understand dependency graphs, coupling, and technical debt can negotiate roadmap trade-offs from a position of genuine shared understanding rather than political maneuvering.
Linear vs Jira: A Product Person's Tear-Down of Two Competing Philosophies
Linear won over developers not by having more features than Jira, but by ruthlessly saying no. This teardown explores how design constraints create product philosophy, and what Atlassian could learn from product-led growth.
Redesigning Onboarding for a B2B Payments API: From 5 Days to 4 Hours
A breakdown of how I redesigned the developer onboarding experience for a payments API by applying Jobs-to-be-Done and progressive disclosure principles — cutting average integration time by 60%.
More product teardowns, competitive analyses, and decision frameworks published on the blog.
Not just what was built — why
Good product managers write down their decisions. Great ones write down the ones that were hard.
- 1.Visual no-code builder (broader appeal, longer build time)
- 2.API-first engine with JSON config (faster, but requires technical users)
- 3.Both simultaneously (higher risk, resource constrained)
Our first 10 enterprise clients all had internal dev teams. Going API-first would let us ship in 6 weeks vs 6 months, validate the core value prop, and layer no-code UI later.
- Excluded non-technical Operations teams from self-serve adoption initially
- Required ongoing PSE support for onboarding
- Created tech debt in UX when building the visual layer later
Ship in Q1, collect 3 months of usage data to inform the no-code UI design, launch visual builder in Q3.
Launched API engine in Q1. 89% of initial clients adopted. No-code layer launched in Q4 with far better UX because of real usage data.
Why a decision journal? Most product people remember decisions selectively. Writing down the problem, options, rationale, and outcome builds a feedback loop that makes future decisions better — and builds credibility with engineering and leadership.
How I measure product success
Data-driven decisions require the right metrics framework. This dashboard demonstrates how I think about product analytics.
- North Star Metric first — everything else is an input or diagnostic
- Guardrail metrics prevent optimization against the wrong thing
- Leading indicators (NPS, activation) beat lagging ones (churn) for decision-making
- Segment by cohort before drawing conclusions
Where I'm heading next
A public accountability roadmap for continuous growth. Product leaders who stop learning stop leading.
Now
3Active priorities this quarter
AWS Solutions Architect Certification
Complete SAA-C03 to deepen cloud infrastructure credibility for platform PM roles.
PM Interview Prep & Role Applications
Systematic preparation covering product sense, analytical, and technical PM interviews at top-tier companies.
AI Product Management Deep Dive
Complete IDEO AI for Product and build a personal LLM-integrated project from scratch.
Next
3Planned for next quarter
SQL for Product Analytics Course
Mode Analytics and Stratascratch structured practice for advanced product analytics SQL.
Product-Led Growth Frameworks
Study PLG motions at Slack, Figma, and Notion; develop a personal PLG playbook.
Kubernetes CKA Certification
Platform engineering credibility for Cloud/Platform PM roles.
Later
2Future vision items
MBA / Executive Education Evaluation
Research and evaluate top PM-focused executive education programs or part-time MBA options.
Speaking & Thought Leadership
Submit CFP for ProductCon or local product meetup; publish 3 long-form product essays.
Architecture I've built and owned
Technical PMs need to communicate in architectural terms. These are real patterns from production systems I've helped design.
Microservices Architecture
Event-driven microservices with Kafka, API Gateway, and service mesh — the architecture I helped design at FinTech.
Diagrams are illustrative representations of real architectures — not exact production configs.
Always building, always learning
I don't claim certifications I haven't earned. This section honestly reflects where I am in continuous learning — and where I'm heading.
Currently Learning
Reforge, Lenny's Podcast, Intercom on Product Management
Stephane Maarek / Udemy + AWS documentation
Mode Analytics School of Data, Stratascratch
OpenView PLG guides, Figma / Slack case studies
Planned Certifications
Amazon Web Services
Why: Signals cloud architecture depth for Platform PM and Cloud PM roles
Scrum Alliance
Why: Formal Agile credential to complement working experience
Google / Coursera
Why: Strengthen data & SQL storytelling for analytical PM interviews
CNCF
Why: Platform engineering depth for DevOps / Platform PM roles
Skills Under Development
"The best PMs are the most curious people in the room — not the ones with the most credentials."
Honest about where I'm growing
Most portfolios claim expertise in everything. This dashboard shows where I actually am — because self-awareness is a product skill.
Why this dashboard exists: PMs who don't know what they don't know make bad decisions. I track skill gaps explicitly so I can close them deliberately — and so the teams I work with know exactly what they get when they hire me.
Let's talk product
I'm actively exploring Technical Product Manager and Technical Product Owner opportunities. If you're hiring, let's connect.
Looking for Technical PM, Technical Product Owner, Platform PM, or AI PM roles at product-led companies.
- Technical Product Manager / Owner
- Platform or Cloud PM
- B2B SaaS or Developer Tools
- Remote or hybrid
- Impact-driven team