Founding AI-Native TPM & Systems Integrity Lead

Why This Role Exists

In the age of AI, execution is being fundamentally redesigned.

Work that was previously:

• manually specified
• manually tested
• manually coordinated

is increasingly becoming AI-operated and agent-driven.

This changes the role of Technical Project Management and QA.

Instead of managing tasks and reporting bugs, the system itself can:

• generate specifications
• simulate workflows
• validate outcomes

What becomes critical is:

someone who designs how this system operates and ensures it produces correct outcomes.

What This Role IsThis role combines:

• Technical Project Management (TPM) — team alignment, orchestration, KPIs, outcomes

• Quality Assurance (QA) — system correctness, validation, reproducibility

Redesigned for an AI-native system.

You own:

• how work is executed across the system

• whether the system behaves correctly under real-world conditions

The Problem

Young people are more connected online than ever, yet lonelier than any generation before them.

Most digital platforms are optimized for passive consumption on screens, pulling people away from the environments they live in.

We are exploring the opposite:

technology that brings people together in real-world environments.

To do that, software must understand place, context, and coordinated action, not just users and clicks.

What We Are Building

Vyry is infrastructure that allows physical places to accumulate persistent digital meaning through human participation.

When students coordinate in quests, they are not simply completing activities. They are creating artifacts, relationships, and identity traces that remain anchored to real locations.

Over time, campuses develop a persistent experiential layer, where places contain memories, co-created assets, and discovery paths generated by the community itself.

The experiences are not the product.

They are the behavioral interface through which the system learns how humans coordinate and co-create meaning in physical environments.

Phygtl is building a system where:

• physical environments become stateful systems

• human coordination generates persistent artifacts

• places accumulate structured memory and identity

• distributed services maintain the world state of these environments

Recent proofs

• 12k → 175k students reached in 2025
• 25% of MAUs complete quests

• pilots show up to 40% reduction in social isolation

The team combines consumer product, spatial, and game-world expertise, with seasoned talent from:

Roblox • Niantic • Ubisoft

alongside a research layer that includes:

2 professors • 4 PhDsFuture DirectionToday Vyry operates as a mobile app.

The next phase evolves the system into infrastructure for smart glasses.

The long-term architecture enables developers and brands to create context-aware activities inside the spatial environment, similar to how platforms like Roblox enabled creators to build experiences on top of a shared world layer.

This requires building systems that not only scale technically, but behave correctly under real-world coordination.

What You Will DoYou operate across three layers:1. Execution Layer (TPM)

You ensure work flows correctly across the system:

• align teams around clear outcomes

• orchestrate execution across product, engineering, and AI systems

• translate system needs into structured work (Jira or equivalent)

• define KPIs such as:
  • system correctness
  • time to resolution
  • execution quality
• ensure outcomes match expectations

2. Correctness Layer (QA)

You ensure the system behaves correctly (Agents to run QA for Unity):

• define expected system behavior across flows

• identify where behavior diverges
• reproduce issues and edge cases
• validate fixes
• ensure failures are:
  • understood at root cause
  • reproducible
  • prevented from recurring

3. AI-Native Layer

You design how validation and execution scale:

• implement agents that:
  • simulate user behavior
  • test flows
  • validate outcomes
  • measure system performance

• create feedback loops that continuously improve the system

• reduce reliance on manual QA and manual coordination

Operational Ownership

You will define how system behavior becomes actionable across the team.

This includes:

• translating system gaps into clear, structured tasks (tickets, flows, validation units)

• ensuring issues are:
  • clearly defined
  • reproducible
  • outcome-driven

• establishing and evolving KPIs, including:

  • system correctness
  • validation coverage
  • time to resolution

• owning how work is tracked and resolved (Jira or equivalent)

• ensuring bugs are not just reported, but:

  • fully understood
  • fixed at the root
  • prevented from recurring

Hard Problems We’re Exploring

• ensuring correctness across multi-user, multi-step coordination flows

• designing validation systems that scale with real-world complexity

• orchestrating AI agents to simulate and validate system behavior

• building systems that detect and resolve failures before users experience them

Role

We are looking for a founding-level system operator and builder.

This role sits at the intersection of:

• execution (TPM)
• correctness (QA)
• automation (AI)

This is not a traditional TPM role.

This is not a manual QA role.

This is ownership of a new system layer.

Without this role, the system scales in features but not in correctness, and breaks under real-world coordination.

Compensation

This is an equity-first founding role.

Compensation is equity-only until our next funding round (target H2 2026).

You can join either:

• Part-time, while keeping your current role

• Full-time

This role is designed for someone who wants to be a founding member without starting from scratch alone.

Who This Is ForPeople who:

• think in systems and execution, not just features

• are strong in:
  • team alignment
  • orchestration
  • driving outcomes
• naturally identify:
  • edge cases
  • system failures
• are comfortable working with:
  • engineers
  • AI systems
  • product flows

• care deeply about correctness and outcomes

Who This Is NOT ForPlease do not apply if:

• you are looking for a salaried job today

• you want a freelance contract or short-term gig

• you are bridging time until your next role

• you prefer clearly defined specs over ambiguous systems

This is a founding role with real ownership and ambiguity.

If InterestedSend:

• a short note on why this role resonates

• examples of systems you’ve debugged, validated, or improved

Final Thought

If you have thought, “I want to build my own startup and make a real impact” — and are looking to do it as part of a team already in motion — we want to hear form you

Originally posted on Himalayas