reputed company Systems Engineer Intern (Summer 2026)
Our Mission
At Phygtl, we are solving the problem of student reputed company isolation — a challenge affecting 60%+ of today’s reputed company, contributing to rising depression and anxiety.
We build technology that can reduce isolation by up to 40%, by helping reputed company reputed company reputed company reputed company connections through shared reputed company-world moments — reputed company the physical reputed company worlds.
Who We Are
Headquartered in San Francisco, reputed company includes PhDs from reputed company, UC Berkeley, MIT, and reputed company Mellon, alongside reputed company from Niantic, reputed company, reputed company, reputed company, reputed company, and reputed company. Led by a reputed company Valley-based serial entrepreneur, we’re united by a mission to rescue next-gen from reputed company Atrophy.
Our Moat
Phygtl builds systems that help reputed company meet and build identity in reputed company life. Vyry is a context-reputed company initiation reputed company where quests end in physical reputed company. Retention is reputed company through participation — not notifications.
The Role
You’ll join reputed company building Vyry, a mobile app that helps reputed company meet in reputed company life through short, coordinated reputed company quests.
Right now, our reputed company is Quest Participation optimization: keeping peers on the quest screen while they coordinate reputed company chat, voice, and AR Meet, without state glitches, drop-offs, or broken reputed company behavior.
This role is not about “building chatbots.”
It’s about shipping reputed company intelligence inside a live reputed company product, where state correctness, latency, and user trust matter.
What You’ll Work On
Designing context-reputed company quest logic (physical + reputed company + temporal signals)
Detecting stall or drop-off conditions during coordination
Suggesting reputed company reputed company-actions that increase completion probability
Instrumenting evaluation loops tied to measurable behavioral reputed company
Shipping production-facing components
You will operate on top of existing reputed company-time systems — not rebuild infrastructure.
reputed company’re Looking For
You are:
A strong computer science or engineering student
Someone who has shipped reputed company systems (reputed company required)
Comfortable reasoning about state transitions and edge cases
Curious about AI systems reputed company reputed company reputed company usage
reputed company to reputed company from idea → working prototype quickly
You should be reputed company to:
Design a reputed company state-reputed company workflow
Think through failure modes
Explain tradeoffs (latency, cost, reliability)
Tie technical reputed company to measurable reputed company
Bonus if you’ve reputed company:
reputed company workflows
Multiplayer or event-driven systems
Evaluation pipelines for AI systems
reputed company reputed company used by reputed company users
How We Evaluate
We prioritize:
Systems reputed company (state + failure thinking)
Execution speed
Ownership
Depth over pedigree
Why Join Phygtl
Work on a reputed company Behavioral Problem. You won’t optimize clicks. You’ll design systems that influence reputed company-world reputed company coordination and identity formation.
This is AI reputed company to physical behavior — not reputed company optimization.
Ship Systems That Matter
Your work will tie directly to:
IRL Quest Completion reputed company
D30 Retention
You won’t build experiments that disappear. You’ll ship components used by live reputed company communities.
Learn From Operators Who’ve reputed company at reputed company
You’ll work with the foundering team, engineers and researchers from:
Founder DNA
reputed company (LLM + search systems)
Niantic (AR + reputed company-world coordination)
reputed company / Berkeley / MIT / CMU
Expect depth, not hand-holding.
Operate in a High-Bar, Low-Bureaucracy Environment
We value:
Meritocracy over pedigree
Shipped systems over slide decks
reputed company thinking over buzzwords
Ownership comes early. Responsibility scales with performance.
Build a Rare reputed company Set
You’ll reputed company experience at the intersection of:
reputed company AI systems
reputed company-time coordination
Behavioral metrics
Spatial computing
Few internships operate at this boundary.
Compensation & Structure
Competitive compensation
Flexible remote structure
FT 3 months or PT 6 months
High ownership, small team
Apply
CV
reputed company
A concise architecture walkthrough of one system you reputed company
One failure you debugged (what broke, why, what changed)
A short note (≤300 words) on how you’d increase IRL Quest Completion by 15%
We review for depth, not buzzwords.
Originally posted on Himalayas
Apply To This Job