Founding Product & Engineering Lead (Technical) – PAM

Founding Product & Engineering Lead (Technical) – PAM
Location: Remote-first (Europe preferred)
Compensation: Equity with vesting. No salary until commercialization.

PAM is an AI-powered product that gives founders structured, actionable feedback on their pitch. It analyses pitch content, slideware, and delivery and returns personalised feedback, investor-style questions, and targeted resources to help founders improve with each iteration.

PAM is designed to scale high-quality pitch feedback beyond live programs and cohorts, while maintaining rigour, context, and fairness. The core product is already built and live in beta.

PAM is not an idea-stage product. Today, the system includes:

• A live web application where founders upload a pitch deck and record a pitch.

• AI-based analysis of pitch content, structure, and delivery, with scored feedback across multiple criteria.

• Investor-style questions generated from pitch content, with example answers.

• A results experience with personalised scores, feedback, and a curated resource destination.

• A production-grade technical stack running on cloud infrastructure with AI-powered analysis and transcription.

The foundations are in place. The next phase is about scaling, hardening, and evolving the product into a commercial-grade offering.

We are looking for a Founding Product & Engineering Lead to take full ownership of PAM from this point forward. This is a senior, hands-on role for someone who can move comfortably between product judgement and technical execution.

You will be accountable for what gets built next, why it gets built, and how it gets shipped. This is not a strategy-only role, and not a feature factory role. It is about making PAM reliable, scalable, and commercially viable.

• Full ownership of PAM’s product direction, technical roadmap, and prioritisation.

• Translating an existing beta product into a scalable, reliable, and monetisable platform.

• Product and engineering decision-making across frontend, backend, AI workflows, and infrastructure.

• Preparing PAM to scale from early beta usage to 1,000+ users while managing cost, performance, and reliability.
  

• Owning the evolution of feedback logic, scoring systems, and the results experience.

• Making pragmatic tradeoffs across accuracy, cost, speed, and user experience in an AI-driven system.

• Establishing clear product operations, including backlog management, release cadence, monitoring, and feedback loops.

• Working closely with Founderland leadership on commercialization strategy and funding readiness.

Technical context

You should be comfortable reasoning end-to-end across:

• A React-based frontend and component-driven UI architecture.

• Backend services handling file ingestion, transcription, analysis, and scoring.

• AI-driven systems using large language models for structured evaluation and feedback.

• Cloud infrastructure, deployment pipelines, and cost management in a production environment.

You do not need to have built this exact stack before, but you must be able to take responsibility for it and make confident technical decisions.

In the first 3 months

• You have a deep, working understanding of the existing system, architecture, and feedback logic.

• You define a clear, opinionated product and engineering roadmap focused on scale and commercial readiness.

• The current beta experience is stabilised, with obvious friction and failure points addressed.

In the first 6 months

• PAM reliably supports a significantly larger user base with predictable performance and controlled AI and infrastructure costs.

• Core feedback, scoring, and results flows are hardened, documented, and easier to evolve.

• There is a clear, testable path to monetisation or paid deployment informed by real usage data.
  

By 9–12 months

• PAM is no longer perceived as a beta tool, but as a product that can be sold, licensed, or funded with confidence.

• Product and engineering decisions are no longer a bottleneck to Founderland’s strategy around PAM.

• The groundwork is laid for hiring additional engineers or further spinning out the product, if desired.

• A senior engineer, technical product leader, or early CTO-type who wants real ownership.

• Someone comfortable joining pre-revenue, with equity as the primary upside.

• Someone who values shipping, iteration, and discipline over constant reinvention.

• Someone who is excited by the responsibility of making an AI product actually work at scale.