Product Manager

Why this role exists We run an unusual stack for an unusual business. Three surfaces have to feel like one product: 1. HRMS 24*7 where CPA/accounting firms & businesses manage their offshore staff, services, jobs, HR Management and billing etc.

A complete HRMS/EOR system which help businesses and firms to manage their HR operations effectively. 2. Team Hub - where our internal staff run delivery and people ops. 3. ERP Core - The system of record that ties clients, services, invoices, Admin, HR, accounts, IT & Assets, and employees together.

The PM who thrives here is equally comfortable talking to a CPA client about why an invoice looks wrong and talking to engineering about a database query. What you'll own 1. The connective tissue.

Define how data and workflows flow between the client portal, team portal, and the CRM core — client → service → job → invoice → employee. Most of our highest-leverage work lives in these seams, not inside any one app. 2. Decision-support surfaces.

Own the dashboard/reporting layer (CEO, HR, CTM, L&D, KPI, cross-sell). Decide what each stakeholder needs to act on, kill vanity metrics, and make sure the numbers are trustworthy. 3. Billing & service-delivery workflows.

From service catalogues to manual-invoice flows , the parts of the product where a mistake costs real money and trust. 4. People-ops & talent products. Recruitment (skill/Boolean search, IJP), L&D, onboarding, and HR analytics, the internal products that let us scale headcount without scaling chaos. 5.

The AI roadmap, pragmatically. We already use LLMs at multiple places, you'll decide where AI earns its place (summarization, sentiment, search, drafting) and where it's a distraction. What we expect you to do 1.

Live in the data. This platform's truth is in its tables. You don't need to write production code, but you must be able to read a schema, sanity-check a query, and catch when a "USD vs INR" mistake is silently corrupting a report.

Data literacy here is non-negotiable, not a nice-to-have. 2. Work the full surface area. Trace a problem from a client complaint in the portal, through the CRM record, to the team-portal workflow that caused it. 3.

Write specs people can build from. Clear PRDs/BRDs, crisp acceptance criteria, mock-ups when words aren't enough. We ship from specs, so the spec must be right. 4.

Inspect before you redesign. We have a lot of existing modules and prototypes. Default to understanding and completing what's there before proposing a rebuild. 5.

Ship in slices. Thin v1s that prove value, then iterate — not 18-month grand plans. 6. Talk to all the humans.

CPA-firm clients, CTMs, HR, recruiters, finance, leadership. Each speaks a different dialect; translate between them. Requirements 1. 5–6 years in product, ideally on B2B SaaS, ops/internal platforms, or fintech/accounting-adjacent tools. 2.

Genuine comfort with relational data, SQL reading-level minimum; you can navigate a CRM/ERP schema and reason about joins, aggregation, and currency/units. 3. Track record of shipping workflow-heavy software where correctness matters (billing, HR, finance, compliance) not just consumer-y feature work. 4. Strong written communication; your specs and your Slack messages both lands. 5.

Stakeholder range: you can hold your own with both a CFO and a senior engineer.