Associate Product Manager (Systems Thinking)

Jetbro Private LimitedAhmedabad, GujaratOn-siteFull-timeNew grad, 0–1 yearsListed 9 hours ago

Apply now

About this role

Company Overview

Jetbro is a technology consulting and systems integration firm. We build reliable, scalable digital systems for organizations where technology is central to operations. Our clients range from Fortune 500 companies to high-growth startups across India, Australia and Canada.

Our 50-member team works across custom product development, enterprise applications and infrastructure-led digital transformation. That spans systems integration, business process automation, cloud, data and applied AI, for industries including FMCG, supply chain, energy, healthcare and education.

Our philosophy is simple: build systems that work quietly, predictably and under pressure. We value clarity over complexity and reliability over noise. Function over flash. Always.

Every engagement starts with understanding how the business actually runs. Process Docs , our in-house method, takes a project from raw site notes to observations, process maps, PRDs, screen specs and a signed-off scope. That way the tech team builds exactly what the business needs.

About the Role

In this role, you turn how a business works into a precise blueprint a tech team can build from. We call this systems thinking: seeing a business as connected parts (people, operations, rules, data and handoffs) and designing how they should work together. The role sits close to a product manager, but starts earlier and goes deeper: on the operations floor.

You will sit with operators, managers and finance teams, capture what really happens, and map it as a process. Then you will design the better version: the data it needs, the rules it must enforce, the screens people use, and what happens when something fails. Your output is the PRD, BRD and screen specs our engineers implement.

You will do this work with AI as your main tool. Our Process Docs method runs inside Claude Code, and you will use it daily to capture, structure, review and refine documentation.

This role suits someone early in their career who wants to learn how real businesses run and how good software is designed for them.

Key Responsibilities

- Observe and capture. Visit client sites, shadow work and interview people. Record each activity's inputs, outputs, people, timing and problems, including the workarounds and exceptions nobody mentions at first.
- Map processes. Turn observations into step-by-step flows with every handoff, decision point and exception path named. A new employee should be able to follow your map on day one.
- Analyze and decide. Compare options, dig into the hard parts of a problem, and help settle the tech stack and implementation approach before design begins.
- Write PRDs and BRDs. Translate processes into requirements with IDs, business rules, data entities and acceptance criteria. Design the improved process, not a digital copy of the old one.
- Specify screens. For each screen, define entry points, layout, data shown, actions, validations, and empty, loading, error and restricted states.
- Design for correctness. Define the source of truth for each balance and status. Spell out how the system handles concurrent users, duplicate requests, partial fulfilment, cancellations and integration failures.
- Write the scope. Produce a self-contained scope document clients can read and sign off without opening anything else.
- Review and close gaps. Audit documentation for completeness, consistency and depth. Turn every gap into a specific question someone can answer.
- Stay with the build. Answer engineers' questions, review shipped work against acceptance criteria, and keep the PRD in step with what was built.

Requirements

Mandatory Requirements

- 0–2 years of work experience. Freshers with strong projects (in intern roles) are welcome.
- A degree in engineering, computer science or business, or equivalent proof of ability. We care more about how you think than what you studied.
- Strong critical thinking. You break a problem into parts, test assumptions, and spot what doesn't add up.
- You think beyond the obvious. You look past the process as described to the exceptions, workarounds and knock-on effects behind it.
- You ask sharp questions. In a room with a client, you ask the questions that reveal how the business really works: "Who decides that?", "Why is it done this way?", "What happens when this fails?"
- Strong communication, written and spoken. You can describe a process so someone who wasn't there understands it, and explain a design to a client and an engineer alike.
- Curiosity to learn, by nature. When something is outside your territory, you dive in with confidence and interest rather than waiting to be taught.
- Comfort reasoning about state and rules. Given "available = on-hand − held − reserved", you can trace balances through a sequence of actions without error.
- Basic software building ability. You can build and run a small application with persistent storage, using any stack you can defend.
- Hands-on use of AI coding tools, ideally Claude Code. You can direct an AI, check its output, and reject a wrong recommendation.
- Ability to read API contracts, sequence flows and acceptance criteria.
- Willingness to travel to client sites and spend time on factory floors, warehouses and offices.

Good to Have

- Experience as an Associate Product Manager, or on a team building digital products. This is the strongest signal we look for. An internship in such a role counts.
- Exposure to operations domains: procurement, inventory, warehousing, sales order management, logistics or finance.
- An internship or project with a consulting, ERP or operations team.
- Familiarity with ERPs or low-code platforms such as SAP, Tally, Zoho, Odoo or Mendix, and how they integrate with custom systems.
- Understanding of transactions, idempotency, concurrency and audit trails in business software.
- Working knowledge of data modelling: entities, relationships, keys and constraints. You can sketch a schema for orders, stock and dispatches.
- Experience writing PRDs, user stories, wireframes or test cases.
- Comfort with Markdown, Git and diagram tools.
- Hindi, Gujarati or another regional language, for conversations on client sites.

What we care about

- Reality over assumption. We document what actually happens, not what the SOP says. Workarounds and edge cases matter more than the happy path.
- Honest gaps. "I don't know yet" written down beats a confident guess. We mark unknowns and turn them into answerable questions.
- Specifics, not adjectives. "3–5 minutes per batch" beats "takes some time". Name the person, the system, the number.
- Failure is part of the design. A good spec says what happens when the network drops, the request repeats, or two people act at once.
- Accountability for AI output. AI makes us fast. You own every line it helps you produce, and you verify it.
- Builds, not decks. Our work is done when an engineer can build from it without guessing.

About You

You are at the start of your career and hungry to learn how businesses really work. You ask "how many?", "how often?" and "what happens when it breaks?" without being prompted.

You enjoy untangling messy systems. You like both the conversation with a warehouse supervisor and the precision of a data model. You notice when two documents disagree on a number, and you fix it.

You are curious by nature. A new industry, a new tool or an unfamiliar problem excites you more than it worries you, and you pick things up fast.

You write clearly and briefly. You use AI tools well and are honest about what they got wrong. You would rather ship a spec that holds up under questioning than one that looks polished.

Benefits

Benefits

This role is a strong first step toward a career in product management, consulting, tech sales or technology more broadly.

- Range of experience. You will talk to many clients across industries, and help design and build the systems they run on. Few early-career roles offer this breadth.
- Exposure to top-tier tech. You will work hands-on with modern AI tools, enterprise platforms and the engineering practices behind reliable systems.
- Real product work from the start. You will do the core work of a product manager: discovery, requirements, design, and seeing it through the build.
- Skills that travel. Understanding a business, asking the right questions and turning the answers into buildable systems are valued in product, consulting, sales and engineering alike.

How we hire

Our process has four stages. Each one decides whether you move to the next.

- Application review. We read your resume and your answers to a few short questions.
- HR round. A conversation about you, how you work, and whether Jetbro is the right fit.
- Assessment. A take-home exercise built around a real-world operations problem. You will design or build software for it using Claude Code, and submit a repository with your documentation and decisions.
- Technical round. You walk us through your assessment, defend your choices and answer questions on your experience and technical ability.