Job Title

Why this role existsAIApply is scaling fast. What we need now is product clarity, ruthless prioritisation, and fast shipping — not process for process’ sake.This role is for a Product Engineer: someone who can own product problems end-to-end, make strong decisions, and build the solution themselves in Laravel.If you describe yourself primarily as a “stakeholder manager” or someone who “aligns teams,” this isn’t the role.If you like owning outcomes, shipping weekly, and sweating details, keep reading.What you’ll ownYou will own core product surfaces from problem → solution → impact.Examples:Activation & onboarding flows (first 24h experience)Retention loops (day 7 / day 30)Auto-Apply workflows (quality, confidence, transparency)Core dashboard UX and system clarityMonetisation & plan boundaries (what users actually understand)You will:Identify the highest-leverage product problemsDefine the simplest possible solutionBuild it yourself (Laravel + frontend)Measure impact and iterate quicklyWhat you’ll do day-to-dayProductTurn fuzzy problems into clear, testable product betsKill ideas that don’t move activation, retention, or revenueWrite concise specs only when useful (often a few bullets is enough)Make trade-offs without needing consensusEngineeringShip production-quality Laravel codeImprove and extend existing systems (not rewrite for fun)Work directly with Stripe, analytics, AI workflows, queues, cron jobsDebug real user issues, not theoretical onesData & outcomesThink in funnels, cohorts, and deltasObsess over activation, retention, LTV, and churnUse data to decide what not to buildOwn results, not just deliveryRequired backgroundYou must have:5+ years experience with Laravel in productionStrong SQL and backend fundamentalsFrontend competence (enough to ship clean UX without hand-holding)Experience owning features end-to-end in a real productProduct intuition grounded in user behaviour, not opinionsBias toward speed, clarity, and simplicityYou likely have:Worked at an early-stage or scaling SaaSStrong opinions about bad UX and bloated productsShipped things that materially moved metricsLittle patience for bureaucracyWhat we explicitly don’t want“Pure” PMs who don’t buildProcess-heavy frameworks without outputJira theatre and over-documentationPeople optimising for optics over impactPeople uncomfortable saying “no”