System Analyst
OpenLM · Kolkata, India ·
- Category
- Business analysis
OpenLM is hiring a System Analyst in Kolkata to keep its software licensing/SAM product coherent across squads: aligning APIs and data models, turning leadership and customer needs into testable specs, and defining metrics and reporting. Core work involves requirements authoring, data analysis (SQL, BI tools), and SAM/ITAM domain fluency.
OpenLM is hiring a System Analyst to act as the connective tissue between product squads, leadership, and the realities of the software licensing / SAM domain we operate in. The role exists to ensure that what we design, build, and report on stays coherent across teams — and operationally efficient as we scale.
WHAT THE ROLE COVERS
Cross-squad design integration. Sit across squads to align APIs, data models, workflows, and user-facing interfaces so the product behaves as one system, not a federation of features. Identify integration risks early and broker resolution between squads before they become rework.
Business analysis & requirements. Translate leadership intent and customer needs into clear, testable specifications squads can build from. Maintain the chain of traceability from a business decision through to a delivered feature, and push back when scope and intent drift apart.
Software licensing / SAM domain expertise. Bring (or rapidly develop) working fluency in engineering software ecosystems, license models (named-user, floating, token, cloud-metered), ITAM/SAM workflows, and the data shapes our customers care about. Use that domain understanding to challenge assumptions and improve specs.
Data & reporting analysis. Define the metrics, dashboards, and operational reports leadership and customers need. Make sure data definitions are consistent across squads, surface anomalies, and turn raw usage data into decisions.
CORE RESPONSIBILITIES
- Partner with squad leads to map current-state vs. target-state designs and own the integration roadmap between them.
- Author requirements documents, user stories, and acceptance criteria that engineering and QA can act on without ambiguity.
- Maintain a working model of the OpenLM product surface — entities, flows, integration points — and keep it current.
- Lead requirements discovery sessions with customers, support, and CS; convert findings into prioritized backlog input.
- Define and validate reporting and analytics requirements; partner with engineering on the data model that supports them.
- Flag operational and licensing-domain risks to leadership early, with options rather than just problems.
WHAT WE'RE LOOKING FOR
- Strong analytical and structured-thinking skills; comfort moving between business framing and technical detail.
- Experience writing requirements / functional specs that engineering teams actually use.
- Familiarity with software licensing, SAM, ITAM, or adjacent enterprise-software domains (or demonstrated ability to ramp fast).
- Comfort with data: SQL or equivalent, BI tools, and reasoning about data models and metrics.
- Excellent written and verbal English; able to facilitate discussions across squads and time zones.
- Self-directed — this role reports to leadership and is expected to operate without close supervision.
HOW SUCCESS LOOKS IN THE FIRST 6 MONTHS
- Integration friction between squads is visibly reduced; fewer cross-team surprises at release time.
- Requirements quality has improved — measured by reduced clarification cycles and rework.
- A shared, documented view of the product's system design exists and is maintained.
- Leadership has a reliable analyst they can hand ambiguous problems to and expect a structured answer back.