05 / AI-Native Vertical SaaSActive product

Placement OSInception to Offer

My roleProduct + Systems Architect

ContextMBA candidates, mentors, institutions

System classAI-Native Vertical SaaS

Portfolio evidenceArchitecture · decisions · production

01 / Brief

The problem

MBA candidates were moving through disconnected CV tools, courses, mentors, practice cases and application trackers. The real problem was missing state: nobody could see the candidate’s current role target, evidence gaps, practice history and next best action in one system.

Open product preview

02 / Constraints

Why it was hard

01The experience needed to support first-year internships, final placements, mentors and administrators.

02The browser should remain thin; core state, validation and authorization belong on the server.

03The product needed role-specific journeys across marketing, business analysis, product and case interview tracks.

04Multi-tenancy, policy enforcement and observability were required from the platform foundation.

03 / Architecture

System shape

The architecture is expressed as operational layers: experience and identity at the edge, bounded orchestration in the middle, governed data and tools underneath, and evidence across the entire path.

Placement OS / logical architectureSanitized portfolio view

01ExperienceGo templ + HTMX + Alpine

02ApplicationEcho modular monolith

03Domain modulesResumes, interviews, applications, diagnostics

04PlatformPostgreSQL, Redis, Casbin

05OperationsOTel, rate limits, CSRF, tenant context

04 / Decisions

The engineering judgment

A modular monolith before distributed services

Strong module boundaries preserve speed and consistency while leaving extraction paths for future scale.

Server-driven UX for workflow-heavy screens

Go owns validation, identity, search and pagination; HTMX progressively updates the interface.

Candidate state is the product spine

Diagnostics, CV evidence, practice, mentoring and applications update one longitudinal career model.

AI is embedded at decision points

Agents diagnose gaps, improve evidence, run practice and interpret progress instead of existing as a floating chat panel.

05 / Production

Hardening the system

01Casbin-backed authorization and tenant-aware middleware.

02CSRF, identity, organization and rate-limit layers.

03PostgreSQL as system of record with Redis for ephemeral/queued concerns.

04OpenTelemetry across request and workflow boundaries.

05Modular domain ownership for maintainability and team scale.

GoEchotemplHTMXAlpine.jsPostgreSQLRedisCasbinOpenTelemetryModular monolithMulti-tenancyRBACAI UXDomain modeling

06 / Outcome

A system designed to preserve the candidate’s complete journey from uncertainty to a defensible offer-ready profile.

Next case study / 06