About the role
Overview
Find the problem. Decide what to build. Ship it to production and prove it worked.
Reporting to the CTO.
Company Details
Periskope helps businesses run customer conversations and operations on WhatsApp. Chats, groups, ticketing and automation live in one workspace, used by teams around the world.
$2.5M+ ARR
~12 People
Profitable · Global customers
Seed · Saison Capital and Alliance
Requirements
2–5 years: In engineering, product, a founder's office, or your own startup.
Product intuition: You can look at a screen and say what is wrong with it, and why.
Proof you build: Something real you made with AI tools. A product, an internal tool, an automation people still use.
Hustle: You unblock yourself. You do not wait for a spec, a designer or permission.
Appetite for depth: You do not need to know production systems today. You need to want to own them.
Clear communication: You explain decisions, flag uncertainty early, and move work forward in a remote team.
Responsibilities
Customer problems: Talk to users every week. Turn what you hear into a clear call on what to build next.
Concept to production: Scope it, build it with agents, deploy it, and iterate on real usage.
A product surface: Own a part of Periskope end to end, and the metric it moves.
What ships: Challenge agent output, test assumptions, and stay accountable for the code and the result.
Production reliability: When something breaks, find out why and fix it. Learn the data models, APIs and WhatsApp infrastructure underneath.
Job Details
Remote for candidates based in India.
Interview Process
Share your profile and one thing you took from idea to shipped: the problem, what you built, how you used agents, and what changed. Shortlisted candidates move through three steps.
Conversation · Async on WhatsApp
Talk through your work and product decisions with Bharat (CTO).
Build together · 90 minutes
Take a real Periskope problem from brief to working build, live with Bharat.
Final conversation · 20 minutes
Discuss the role and mutual fit with Swapnika (CEO).
Why This Role Exists
For years, building software needed two people. A PM decided what to build. An engineer wrote the code. Most of the time went into the handoff between them.
That split no longer makes sense. AI agents now write most of our code. Typing code stopped being the bottleneck. Judgment took its place: knowing which problem matters, what the smallest useful fix is, and whether it holds up in production.
A Product Engineer is one person doing the whole loop. You talk to the customer, make the call, direct the agents, ship the change and watch what happens next.
How the Work Flows
Listen: Sales calls, support chats, churn reasons, usage data.
Decide: Pick the problem that matters. Cut it to the smallest useful fix.
Build: Direct agents. Review every diff. Test what they assume.
Ship: Release to real customers, behind a flag if it is risky.
Measure: Check usage and tickets. Keep it, fix it or kill it.
Then back to listening. A good loop takes days, not quarters.
Who This Is For
You do not need an engineering title. You need taste, speed, and a real wish to build things that run in production.
Engineers: Who care more about the customer than the stack.
Product managers: Who are tired of writing specs for someone else to build.
Founder's office operators: Who already do a bit of everything and want to ship software too.
Ex-founders: Who want to build product again, with less overhead.
Not a Fit If
You want a defined lane. This role does not have one.
You see building as someone else's job.
You think agents ship production code on their own. They do not. You own every line they write.
Important Note
ClanX is a recruitment partner, helping Periskope hire a Product Engineer.
Highlights
Talk to users. Ship with agents. Own the outcome.
Originally posted on Himalayas