Product Operations Specialist — Trade
Your mission is to turn real customs operations into software: take errors, regulation and user feedback, and convert them into improvements that make Camtom learn faster than any competitor.
Apply for this roleAbout Camtom
Camtom is an AI platform for international trade in Mexico. We automate critical workflows for customs agencies, importers and compliance teams: tariff classification, value manifestation, COVE/VUCEM, KYB, document review, dossiers and operational validations.
Our goal is not just to digitize processes. We want to build a system that learns from every operation, every correction and every error to reduce rework, risk and operational time.
The role
This role is for someone who understands the operational pain of international trade and has the discipline to convert it into product. We're not looking for someone who just cites rules, captures information or chases deadlines. We're looking for someone who can look at a real case, understand what went wrong, identify the pattern and translate it into a concrete improvement for engineering and product.
You'll work with
- Value Manifestation (MVE) and VUCEM.
- COVE, proformas, invoices and receipts.
- Anexo 22 and pedimento validations.
- KYB of importers, suppliers and dossiers.
- RRNA, NOMs and operational rules.
- Automations and product skills.
Expected impact
- Less manual rework for users.
- Fewer errors before signing or transmitting.
- Clearer tickets for engineering.
- Better validations and flows.
- Insights about error patterns.
- Modules that improve with real use.
Responsibilities
Product and users
- Talk to users to understand real friction in operations.
- Separate surface requests from problems that cause errors, blockers, rework or risk.
- Convert feedback into rules, flows, validations and prioritized improvements.
- Document learnings per module: KYB, MVE, Anexo 22, COVE, RRNA and Digital Dossier.
Operations and compliance
- Review operational cases with real documents.
- Validate that outputs make customs sense, not just that the system responds.
- Translate criteria from Anexo 22, MVE, VUCEM and RRNA into functional checks.
- Detect when a flow should block, warn or request user confirmation.
Engineering and functional QA
- Write clear tickets with context, example, expected behavior and acceptance criteria.
- Create functional test cases from real operations.
- Test fixes before release and confirm they resolve the original case.
- Help prioritize bugs and improvements by operational impact.
Data and insights
- Analyze patterns: why cases fail, how frequently and in which clients.
- Build error matrices and automation opportunities.
- Measure whether an improvement reduced errors, rework or manual support.
- Convert user corrections into product learning.
Experience we're looking for
The ideal profile comes from a customs agency, freight forwarder, importer/exporter, trade operations consultancy or compliance team. Must have lived real operations and understood what happens when data is wrong, a document doesn't add up or VUCEM rejects.
An example profile we'd notice
Customs Compliance Analyst with 5 years at a customs agency. Responsible for document review and dossier validation for IMMEX and retail clients. Experience in A1 pedimentos, VUCEM/COVE, Value Manifestation, increment review, NOMs/RRNA and rejection follow-up. Led the internal implementation of a digital checklist to reduce capture errors and built incident reports per client in Excel or Power BI.
Must be able to produce
- Clear engineering tickets.
- Functional test cases.
- Operational checklists.
- Error matrices.
- Validation rules.
- User briefs.
- Automation proposals.
- Pattern reports.
- Acceptance criteria.
- Actionable insights per module.
Evaluation scorecard
| Criterion | What we look for | Weight |
|---|---|---|
| Customs operations | Has lived real operations and understands where MVE, COVE, pedimento, dossier and VUCEM break. | 25% |
| Product thinking | Converts problems into flows, validations, rules, UX and acceptance criteria. | 25% |
| Written clarity | Can write tickets, light specs and reports that engineering can execute without guessing. | 20% |
| Data and analysis | Can quantify patterns and prioritize with evidence, not just opinions. | 15% |
| Regulatory judgment | Reads rules, annexes and manuals without inventing and knows when to ask for confirmation. | 10% |
| Ownership | Orders chaos, follows up and closes loops with users and engineering. | 5% |
Interview exercise
During the process we'll ask you to analyze 5 real anonymized cases:
- A COVE incorrectly extracted from a proforma.
- An MVE blocked by contradictory VUCEM status.
- A KYB marked as 100% complete but with failed analysis.
- An Excel of tariff codes to obtain RRNA.
- A pedimento with dubious Anexo 22 fields.
We want to see how you identify risk, group patterns, propose product improvements, write a ticket and define how to measure if the fix worked.
What we're not looking for
- We're not looking for a pure lawyer who only gives regulatory opinions.
- We're not looking for a data-entry person who only follows instructions.
- We're not looking for generic support that only answers chats.
- We're not looking for a project manager who only chases deadlines.
- We're not looking for a developer for this role.
What success looks like
In the first 90 days, this person should have converted real client cases into concrete improvements: fewer repeated errors, better tickets, stronger functional tests, better-defined automations and modules that better reflect real customs operations.
Sound like you?
Apply for this roleEmail us at hello@camtomx.com. We read every application.