Project+4
Jobcadu — Career Platform Startup
Aug 2025
Product . Systems . Craft
Phurin
Building products at the intersection of product sense, systems thinking, and mindful craft.
Scroll
Chapter 06
Redefining
The AI-Native Architect
Leveraging LLMs to shift from brick-laying to blueprinting, thinking and verification. Understanding how systems, products, interfaces, decisions, and teams hold together.
Chapter 05
Integration
Applied AI & Operations
Led the full-stack rebuild of a core product. Applied AI-augmented development to increase shipping speed while simultaneously scaling cross-border teams across Thailand and Vietnam.
Chapter 04
More Autonomy
Product + Design + SEO
Bridged the gap between product and execution. Expanded scope beyond management into UX design (Figma) and SEO, reducing dependency on specialists to accelerate the user journey.
Chapter 03
Entropy
Working with ambiguity
Operated in a pre-product environment with minimal resources. Mastered the loop of acting under uncertainty: using rapid execution to build and generate the data needed for the next decision.
Chapter 02
Fundamentals
Getting Project done
Worked in project management roles and developed basic work habits. Learned how to coordinate with others, meet expectations, and take responsibility for outcomes.
Chapter 01
The Reset
Market Reality Check
Graduated in Economics, then completed two marketing internships. Entered a data-heavy role where a failed probation period stripped away illusions of competence. This forced a hard reset.
What I can
contribute
01
MVP & Prototypes
Turn unclear assumptions into testable forms rapid enough to learn and cheap enough to discard.
02
Scope & Timeline
Make trade-offs explicit: what matters now, what can wait, where risk accumulates.
03
Cross-Domain Work
Bridge engineering, design, and business logic so constraints are shared and trade-offs are understood.
04
Context Management
Refine and log loose decisions into reusable artifacts and system prompts that encode good judgment for repetition and scale.
How I learn & decide
through PM thinking frames
Signal I noticeHow I reason & interveneImpact / Effort
Problem feels unclear, complex or messyI reduce it to first principles and real constraints: time, cost, people, risk - before discussing solutions.
High/ Low
Pressure to decide quicklyI separate decisions that are safe to lock from those that must stay alive, so learning remains cheap.
High/ Medium
Teams disagree or talk past each otherI make trade-offs explicit and visible, translating between engineering reality, business pressure, and user psychology.
High/ Low
Scope keeps expandingI communicate, manage-up, and re-anchor priorities around learning speed and direction, not feature count.
Medium/ Low
Decisions get agreement too quicklyI ask how this could fail, where users may misinterpret, and which assumptions are still untested.
High/ Medium
These are not steps or frameworks. They are signals and instincts that help me recognize when to step in. , so teams don’t commit too early to the wrong kind of certainty or head down a likely dead-end path.
These features
come standard.
Numerical
Numbers backup story and decisions
My Economics background helped me become comfortable with graphs, trade-offs, and efficiency. Basic stock investing has influenced how I read numbers, traction, and early feasibility.
GraphsTrade-offsEfficiencyThinking in Bets
Alignment
Leadership sleep well
I think my ex-boss slept a bit better because I took ownership of my work and paid close attention to product quality. I also try to notice early signals and assumption risks before problems grow.
Early signalsOwnershipQualityTrust
Get to know me
questions
Mostly early-stage questions where data is incomplete. I focus on defining initial direction, setting scope boundaries, and clarifying user expectations.