Phygtl, Inc. · Remote · United States
In the age of AI, execution is being fundamentally redesigned.
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:
someone who designs how this system operates and ensures it produces correct outcomes.
Technical Project Management (TPM) — team alignment, orchestration, KPIs, outcomes
Quality Assurance (QA) — system correctness, validation, reproducibility
Redesigned for an AI-native system.
whether the system behaves correctly under real-world conditions
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.
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.
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.
They are the behavioral interface through which the system learns how humans coordinate and co-create meaning in physical environments.
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
pilots show up to 40% reduction in social isolation
The team combines consumer product, spatial, and game-world expertise, with seasoned talent from:
alongside a research layer that includes:
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.
You ensure work flows correctly across the system:
orchestrate execution across product, engineering, and AI systems
translate system needs into structured work (Jira or equivalent)
You ensure the system behaves correctly (Agents to run QA for Unity):
define expected system behavior across flows
You design how validation and execution scale:
create feedback loops that continuously improve the system
reduce reliance on manual QA and manual coordination
You will define how system behavior becomes actionable across the team.
translating system gaps into clear, structured tasks (tickets, flows, validation units)
establishing and evolving KPIs, including:
owning how work is tracked and resolved (Jira or equivalent)
ensuring bugs are not just reported, but:
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
We are looking for a founding-level system operator and builder.
This is not a traditional TPM 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.
This is an equity-first founding role.
Compensation is equity-only until our next funding round (target H2 2026).
Part-time, while keeping your current role
This role is designed for someone who wants to be a founding member without starting from scratch alone.
think in systems and execution, not just features
care deeply about correctness and outcomes
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.
examples of systems you’ve debugged, validated, or improved
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