About ClearancePort

ClearancePort is an operating system for India's freight forwarders, customs brokers (CHAs) and transporters. It runs a shipment from the first quote to the final invoice. AI agents do the routine work, and people approve what matters.

What the platform covers today:

- Commercial: rate requests, vendor RFQs, quote comparison and quote sending, read straight from email and WhatsApp, in English and Hinglish.
- Customs: shipping bill and bill of entry checklists, HSN classification, duty and import-policy checks, and drawback and RoDTEP incentive recovery.
- Road: a transporter workspace for RFQs, dispatch, fleet and driver documents, trips, proof of delivery and freight bills.
- Air and ocean: booking, AWB rating, flight and container tracking, and exception handling.
- Finance: job costing, invoicing, vendor bill review, and sync with Tally and QuickBooks.
- Service desk: customer queries over email and WhatsApp, answered from live shipment data.

Every company on ClearancePort is its own tenant, with its own data. Forwarders and transporters work together through connections that both sides accept.

The role

You will be the person who knows how the work is really done on the floor, and makes sure the product does it that way. We build fast, and much of the routine work is done by AI agents. That makes the product owner's judgement the bottleneck: what an agent may do alone, what a person must approve, and what "done" means for a customs filing or a road trip.

You will work directly with the founder and the engineering team. You will own the backlog for one or two product areas, write the specs, test what ships on the real product, and sit with forwarders, CHAs and transporters to learn where their day breaks.

This is a product role, not a coding role. You do need to be comfortable reading data, asking sharp questions of a system, and saying plainly when something is wrong.

What you will do

- Turn operations into specs. Take a real workflow, such as a bill of entry query, a transporter's freight bill or a vendor quote that came back in Hinglish. Write down what the product must do, step by step, with the edge cases a desk executive would catch.
- Decide what agents may do on their own. For each agent action (send a quote, chase a document, propose a dispatch, flag a duty difference), set whether it acts alone,



proposes for approval, or is never automatic. Then check the results against what a careful person would have done.
- Test on the real product. Walk every release in the browser as a forwarder, a CHA, a transporter and a finance user. File clear defect reports: what you did, what you expected, what happened.
- Build the ground truth. Label real emails, documents and replies so we can measure whether the agents read them correctly. Keep the gold sets honest.
- Talk to users. Sit with customers during onboarding and pilots. Bring back the moments where they reached for Excel, WhatsApp or a phone call instead of the product.
- Own a backlog. Keep one or two product areas ranked by what blocks a customer's next milestone. Say no to work that does not.

Example problems you would own

- Customs: checklist fields a CHA still fills by hand; why an HSN suggestion was wrong; a duty or incentive the client is owed.
- Road and transport: a trip that cannot close without a POD; a transporter quote missing loading terms; fleet document expiry.
- Finance: a vendor bill that does not match the agreed rate; an invoice in the wrong currency; Tally sync gaps.
- Commercial: a customer RFQ with missing cargo details; which vendor quote to recommend and why.
- Air and ocean: a flight change nobody chased; a container exception that should have raised a task.
- Service desk: a WhatsApp status question the agent answered from stale data.

Must-haves

- You write clearly. A spec, a bug report or a one-page decision note from you can be acted on without a meeting.
- You are exact with detail. A wrong port code, a misread Incoterm or a duty off by one decimal bothers you.
- You are comfortable with spreadsheets and data. You can filter, pivot, and spot the row that does not add up.
- You are curious about how businesses actually work, and you ask "why is it done this way?" until you get a real answer.
- You can work on your own with little structure,



and you say early when you are stuck.
- You are studying or have recently finished a degree in any field: commerce, engineering, supply chain, economics, law or business.

Backgrounds we especially want to hear from The best candidates for this role have done the work our product automates. If any of these describe you, say so first in your application:

- Logistics and freight forwarding: you have worked at a forwarder, an NVOCC, an air or sea freight desk, a 3PL or a transporter. You have sent RFQs to vendors, chased bookings, or tracked shipments by phone.
- Customs and CHA work: you have prepared or checked shipping bills or bills of entry, worked with HSN codes, ICEGATE or a customs broker's office, or handled drawback and RoDTEP claims.
- Finance and accounts in trade: you have reconciled vendor bills, raised freight invoices, handled GST on services, or worked in Tally for a logistics or trading company.
- Operations in an exporting or importing company: you have been the person on the shipper's side who dealt with the forwarder and the CHA.
- Other trade-adjacent desks: shipping lines, airlines' cargo teams, ports, ICDs, warehouses, or trade compliance.

A plus

- Agentic or AI-first startup experience. You have worked on, tested or operated a product where AI agents take actions, not only answer questions. You know why "the model sounded right" is not the same as "the work was right".
- Hindi, or comfort with Hinglish, since many of our users write that way on email and WhatsApp.
- Any product, QA or business analyst internship.

You do not need all of these. One real stint on a logistics, customs or finance desk counts for more than a polished product course.

Your first 90 days

1. Days 1–30: learn the floor. Use ClearancePort as each kind of user on our demo companies. Shadow a forwarder or CHA desk. Write up the three biggest gaps between how they work and what the product does.

2. Days 31–60: own one area. Take over the backlog for one product area. Write specs for its next releases, and walk every release before it reaches a customer.

3. Days 61–90: own an agent. Pick one agent, such as quote sending, document chasing or vendor bill review. Build its labelled test set, measure how often it gets the work right, and propose what it may do alone.

📌 Product Owner Intern (Delhi)
🏢 ClearancePort
📍 Delhi