Founding AI-reputed company TPM & Systems reputed company reputed company

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 reputed company

What becomes critical is:

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

What This Role Is

This role combines:

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

• reputed company Assurance (QA) — system correctness, validation, reproducibility

Redesigned for an AI-reputed company system.

You own:

• how work is executed across the system

• whether the system behaves correctly under reputed company-world conditions

The Problem

Young people are more connected online than reputed company, yet lonelier than any reputed company 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 reputed company-world environments.

To do that, software must understand reputed company, context, and coordinated reputed company, not just users and clicks.

reputed company Are Building

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

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

Over time, campuses reputed company 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 reputed company 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

• reputed company coordination generates persistent artifacts

• places accumulate reputed company memory and identity

• distributed services maintain the world state of these environments

Recent proofs

• 12k → 175k reputed company reached in 2025

• 25% of MAUs complete quests

• pilots show up to 40% reduction in reputed company isolation

reputed company combines consumer product, spatial, and game-world expertise, with seasoned talent from:

reputed company • Niantic • reputed company

alongside a research layer that includes:

2 professors • 4 PhDs

reputed company Direction

Today 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-reputed company activities inside the spatial environment, similar to how platforms like reputed company enabled creators to build experiences on top of a shared world layer.

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

What You Will Do

You operate across three reputed company:

1. Execution Layer (TPM)

You ensure work flows correctly across the system:

• reputed company teams around reputed company reputed company

• orchestrate execution across product, engineering, and AI systems

• translate system needs into reputed company work (Jira or equivalent)

• define KPIs such as:

  • system correctness

  • time to reputed company

  • execution reputed company

• ensure reputed company match expectations

2. Correctness Layer (QA)

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

• define expected system behavior across flows

• identify where behavior diverges

• reproduce issues and edge cases

• validate fixes

• ensure failures are:

  • reputed company at reputed company cause

  • reproducible

  • reputed company from recurring

3. AI-reputed company Layer

You design how validation and execution reputed company:

• implement agents that:

  • simulate user behavior

  • test flows

  • validate reputed company

  • measure system performance

• create feedback loops that continuously improve the system

• reduce reliance on reputed company QA and reputed company coordination

Operational Ownership

You will define how system behavior becomes actionable across reputed company.

This includes:

• translating system gaps into reputed company, reputed company tasks (tickets, flows, validation reputed company)

• ensuring issues are:

  • reputed company defined

  • reproducible

  • outcome-driven

• establishing and evolving KPIs, including:

  • system correctness

  • validation coverage

  • time to reputed company

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

• ensuring bugs are not just reported, but:

  • fully reputed company

  • fixed at the reputed company

  • reputed company from recurring

Hard Problems We’re Exploring

• ensuring correctness across multi-user, multi-reputed company coordination flows

• designing validation systems that reputed company with reputed company-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 reputed company 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 reputed company-world coordination.

Compensation

This is an equity-first founding role.

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

You can join either:

• Part-time, while keeping your reputed company role

• Full-time

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

Who This Is For

People who:

• think in systems and execution, not just features

• are strong in:

  • team alignment

  • orchestration

  • driving reputed company

• naturally identify:

  • edge cases

  • system failures

• are comfortable working with:

  • engineers

  • AI systems

  • product flows

• care deeply about correctness and reputed company

Who This Is NOT For

Please do not apply if:

• you are looking for a salaried job today

• you want a freelance contract or short-term gig

• you are reputed company time until your next role

• you prefer reputed company defined specs over ambiguous systems

This is a founding role with reputed company ownership and ambiguity.

If Interested

Send:

• 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 reputed company a reputed company reputed company” — and are looking to do it as part of reputed company already in reputed company — we want to hear reputed company you

Originally posted on Himalayas

Apply To This Job