Perplexity
Member of Technical Staff, AI Products (Early Career - Industry)
San Francisco, US
Role snapshot
Perplexity is hiring a Member of Technical Staff, AI Products (Early Career - Industry) on a full-time basis. This is a role based in San Francisco, US. The listing highlights AI Products.
- Company
- Perplexity
- Location
- San Francisco, US
- Job type
- Full-time
- Experience
- 1+ years
- Posted
- Oct 2, 2026
Who this role suits
People with roughly one to three years of experience who can own small pieces of work with light guidance and want to widen their scope.
How to prepare your application
- Check your résumé against the listed skills (AI Products) and give each one a concrete example: what you built or achieved, not just that you used it.
- Prepare two or three stories about work you owned end to end, including one thing that went wrong and what you changed.
- Read what Perplexity publishes about its product or team, so you can say clearly why this role and this company.
Apply only on Perplexity's own site. A genuine employer never asks candidates for money, deposits or bank details to apply, interview or “secure” a job. If something looks wrong, use Report a problem with this listing and we will review it. Read how we check listings.
About the role
NOTE ON ELIGIBILITY: this role is for industry candidates already working in software engineering for the past 1+ years. New grads and current students should NOT apply to this role (instead, visit pplx.ai/newgrads).
About the role
In 2026, we launched Computer, the defining product for the new era of agentic AI. Millions of people now use Perplexity to transform knowledge into action, through Search, Comet, and Computer. Product Engineering owns those experiences end to end, from the interface a user touches to the search and model calls behind it, on top of roughly 200M queries a day and a 200B+ URL index.
This is a full stack role in the truest sense. There are no frontend or backend lanes here, and no one waits for a ticket before starting. It suits people who love to build and want the room to do it. What you have shipped and how quickly you learn tell us far more than years on a resume or where you went to school.
What you will do
Own a user-facing surface end to end, from the interaction, design, and frontend through the application logic, APIs, data models, and the search or model calls behind them.
Ship to production continuously. New engineers typically have code in front of users in their first week.
Build with AI as a primary tool, not a novelty. We expect you to use agents and coding models aggressively to move faster, and to have sound judgment about when their output is wrong.
Turn ambiguous product ideas into working prototypes, then use real usage data and evals to decide what survives.
Raise the quality bar on reliability, latency, and craft for the surfaces you own.
Work directly with designers, PMs, and research engineers, without unnecessary process in between.
What we look for
1+ years of professional software engineering experience, or a track record of strong internships where you shipped production code at scale.
Strong in at least one backend language, such as Python or Go, with real experience across services, APIs, and relational data modeling. Comfortable working in React and TypeScript on the frontend.
Real evidence of building: production work you understand in depth, shipped side projects with actual users, meaningful open-source contributions, hackathon wins, or research you turned into working software.
Comfort with ambiguity and an instinct to start building incrementally rather than wait for a spec.
Hands-on experience with AI products, with opinions about their rough edges and what that means for the product you are building.
Nice to have
Experience with our stack: React or Next.js, Python, Go, PostgreSQL, Redis, Docker, AWS. You will not be expected to know all of it on day one.
Experience building on top of LLMs: AI orchestration, RAG, evals, agents, tool use.
Product taste. You can tell a good interface from a bad one and explain how to improve it.
A public track record we can read, such as GitHub, a technical blog, or a demo we can try.