Product Manager

About TORCH & the Business OSTORCH is a Baghdad-based software company building the next generation of business software. We exist to simplify how organizations operate — cutting through complexity so teams can move faster and grow. Innovation for simpler business.We're building the TORCH Business OS — one super platform where organizations run everything, from finance and sales to supply chain, HR, documents, and communication, instead of stitching together a dozen disconnected tools. One platform, one data truth, one experience — with AI embedded across every app.The OpportunityWe're hiring a Product Manager to own Business OS apps end-to-end.You'll take an app from a one-line idea to a specification engineers build from — and then stay with it through testing and refinement until it's genuinely good. Not a feature here and a ticket there: the whole app. Its structure, its data model, its workflows, its packaging, and the judgment calls in between.That means studying how the world's best products solve the same problem, then deciding what TORCH does differently. Proposing competing architectures for how the app should be organised and defending the trade-offs. Defining every entity, every state a record can move through, and every event the app publishes to the rest of the platform. Specifying pages down to the field level. Then walking the whole thing as a real user — an accountant closing the month, an HR officer onboarding a hire — to find the gaps that only appear when you actually try to use it.We have a documented product methodology, so you won't be inventing the process. Ten phases, from competitive research through to a milestone roadmap, module specifications approved page by page, flow testing, and a dedicated simplification pass that cuts clicks and complexity before engineering starts. You will need to execute it with precision, and sharpen it where it's weak.The apps live in one ecosystem, so the hardest part of the job is usually not the app itself — it's the boundaries. What data does this app own, and what does it borrow from another? What happens when the app it depends on isn't installed? What belongs in the Core package versus a paid add-on? Getting these right is what makes the platform feel like one product instead of twelve.What You'll Work OnResearch and positioning — Analyse the global leaders in your app's domain, identify what's coming next, and decide where TORCH competes and where it deliberately doesn't.App architecture — Propose and defend the app's module structure, navigation, and page inventory. Argue for the simpler version; consolidate five screens into one when they're really the same thing.The specification — Write the App Charter: entities, fields, state machines, roles and permissions, the events the app publishes and consumes, and the flows that cross into other apps. Then the module-level specs, page by page, field by field.Roadmap and milestones — Break the app into shippable increments and sequence them so every milestone leaves a working product, not a half-built one.Flow testing — Walk every workflow as specific user personas and find what's missing: the undefined edge case, the state with no exit, the setup step nobody specified. This routinely surfaces dozens of gaps per app, and catching them here is far cheaper than catching them in code.Simplification — Count the clicks in the daily workflows and cut them. Merge pages that differ only by a filter. Add bulk actions where users repeat themselves.The AI layer of your app — Define which actions AI is allowed to take on real records, which ones need a confirmation before they commit, and where an inline suggestion beats a chat conversation.Working with the team — With engineering on what's buildable, design on how it surfaces, and the people who actually run finance, HR, and operations on whether it solves a real problem.What You Bring (Must-Have)At least 1 year in product management shipping software, ideally B2B — ERP, SaaS, fintech, or internal business platforms.Real understanding of business workflows. You know what an approval chain is, why permissions are hard, what a state machine on a document looks like, and why "just add a field" is rarely just adding a field.Exceptional written specification skills. This role produces documents engineers build from directly. Precise, testable, unambiguous — vague requirements are the failure mode here, and you should hate them.Systems thinking. You can hold a data model and a permission matrix in your head at once and spot the contradiction between them.Technical fluency. You don't need to code, but you should be comfortable discussing APIs, events, and data models with engineers without translation — and be able to tell when a technical answer is a real constraint versus a preference.UX judgment. You can look at a flow and count the clicks, spot the dead end, and argue for the simpler version.The instinct to cut. Good product work here is mostly deciding what not to build. If your first draft of anything is always the biggest version, this will be a difficult role.Clear communication in Arabic and English, and the confidence to push back on a bad idea regardless of who suggested it.Nice to HaveBackground in a domain the Business OS covers — finance, HR, supply chain, CRM, procurementPrior work as a business analyst, solution consultant, or ERP implementerFamiliarity with permission and role models (RBAC) in multi-tenant softwareExperience with pricing and packaging decisions (core vs. add-on)Experience running user research or usability testingInterest in how AI is changing business softwareComfort with design tools (Figma) at a reading levelWhy This Role Is DifferentMost product roles in the region mean maintaining features someone else designed. This one means owning a product. You decide the structure, you write the specification, you find the gaps, and you see it ship — with a small team, a documented method, and a direct line to the people making the calls.Location & TypeFull-timeOn-site in Baghdad, IraqWorking language: Arabic and English