Skip to content
CV Rocket
Get started
How it worksThe enginePricingBlogContactSign in

Open nowPosted 3 days ago

Product Engineer - Remote

CLANX29 open roles

Where
Remote job, Remote
Work mode
Remote
Get the CV for this job

From $25 per CV, paid once. No subscription.

Your applicationOpen nowProduct Engineer - RemoteCLANX · Remote job, Remote

  1. YouYes, apply to this one.

  2. CV RocketCV written for this posting.

  3. 25 readersRecruiter, hiring manager, skeptic. Round after round.

  4. CV RocketApplied on CLANX's own form.

The reply lands in your private mailbox

3×more interviews than doing it yourself with ChatGPT.

The clock on this job

Early applications get read.

13.4% of postings close within 7 days. Measured by our own scanner across the market. CLANX postings stay open a median of 20 days.

Share of postings closed within
  1. 2.2%1 day
  2. 4.6%3 days
  3. 13.4%7 days
  4. 21.6%14 days
  5. 36.2%30 days
  6. 59.0%60 days
This job: posted 3 days ago

CLANX median: 20 days open

The posting

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.

  1. Conversation · Async on WhatsApp Talk through your work and product decisions with Bharat (CTO).
  2. Build together · 90 minutes Take a real Periskope problem from brief to working build, live with Bharat.
  3. 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

  1. Listen: Sales calls, support chats, churn reasons, usage data.
  2. Decide: Pick the problem that matters. Cut it to the smallest useful fix.
  3. Build: Direct agents. Review every diff. Test what they assume.
  4. Ship: Release to real customers, behind a flag if it is risky.
  5. 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.

From $25, paid onceGet the CV for this job

What happens when you press

One press. We do the rest.

  1. A CV for this posting

    Written against CLANX's own wording, from every piece of relevant proof in your profile.

  2. 25 readers review it

    Recruiter, hiring manager, skeptic and more read every draft, round after round. You get the best round.

    The review screen in CV Rocket: how each CV was read, round by round.

  3. We apply on CLANX's form

    Our application engine gets through the hardest forms there are. Where a question needs you, AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

    An application in CV Rocket: every answer filled in on the employer's form.

  4. Every reply, sorted

    CLANX's answer lands in your private mailbox, and we classify it on arrival: interview, question, rejection.

    The CV Rocket inbox: each employer reply classified as an interview, an action or a rejection.

  5. Reply with AI

    AI helps you write the email, checks it and sends it. We show you whether the recruiter read it.

  6. The interview in your calendar

    Full integration with your calendar. The invitation goes straight in.

    An interview invitation in the CV Rocket inbox, added to the candidate's calendar.
Get the CV for this job

From $25 per CV, paid once. No subscription.

Why it works

3×

more interviews than doing it yourself with ChatGPT.

ChatGPT writes a CV and never learns what happened to it. We see every reply. For each CV we know:

  • How it was written, and how the review scored it
  • When we applied, and how long after the posting went up
  • Which posting, which company, which city
  • Who got the interview, and who heard nothing

That is how we know which CVs get called.

Get the CV for this job

From $25 per CV, paid once. No subscription.

The numbers game

More applications. More interviews.

Every application goes out with its own CV, written for that posting and paid once. Send enough of them and the law of large numbers finds you the job.

Get the CV for this job
By hand5–10
With CV Rocket100
applications a day

Nearby

Live postings like this one

Same employer first, then the same role elsewhere.

Before you press

Straight answers

Get the CV for this job

From $25 per CV, paid once. No subscription.

What if my background isn't good enough?

We make the most of the background you have. The CV uses every piece of relevant proof your profile holds, and one of the 25 readers reads your whole profile and flags what the CV left out.

Do you really apply for me?

Yes, on the employer's own form, the hardest ones included. Where a question needs you, you answer it right there and AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

Is it a subscription?

No. You pay once per CV, from $25. Every application goes out with its own CV, written for that posting.

One job. One CV.
Paid once.

Pick the posting you want. We write for it, apply for you and catch the reply.

Get the CV for this job

From $25 per CV, paid once. No subscription.