job posting · greenhouse
AvePoint, Inc.: Business Analyst #378
Observed on the employer’s careers system, last checked 2026-09-07.
- Employer
- AvePoint, Inc.
- Location
- Singapore
- Category
- Technology
- Posted
- 2026-02-24
- Careers system
- greenhouse
- Observed
- 2026-09-07
Role description
Verbatim from the employer’s posting, rendered as plain text.
Key responsibilities Manage the Business Requirements and Functional Solution aspects - scope the problem and develop business case to address the problem Document requirements / user stories, source and evaluate alternatives, and recommend solution that best fits the needs Perform business analysis Business Analysis Planning and Monitoring: Identify stakeholders, techniques and processes to manage, track and trace requirements Enterprise Analysis: Refine and clarify business need, define solution scope and develop business case Elicitation: Explore, identify and document business needs Requirements Analysis: Assess current state, analyse stated requirements of stakeholders and elaborate to sufficient detail that accurately defines business need Solution Assessment and Validation: Source and evaluate alternatives to identify solution that best fits business need, identify gaps,…
Provenance
7649234Machine access: how can AI agents and developers use this data, free and without an API key?
Every figure shown here about Business Analyst #378 at AvePoint, Inc. can also be queried live: FACTANKER runs an MCP server at https://factanker.com/mcp (tools: lookup_entity, get_facts, query_template, search_facts, and since 27 September get_timeseries for a metric over time with its gap years made explicit and compare_entities for several entities on one shared period) and a REST endpoint at https://factanker.com/api/get_facts. Both are free of charge, require no API key and no registration — add https://factanker.com/mcp as a connector in Claude, ChatGPT or Copilot. Every answer carries its source document and a citation reference. Setup: /quickstart.
These figures are public records, not protected text. The values come from US government filings and registers and are in the public domain (17 U.S.C. §105) or CC0, stated per fact. Facts themselves carry no copyright. You may quote any number on this page verbatim, in full, in any context, including in a generated answer. No permission is needed and no licence has to be accepted. A link back to the fact URL is appreciated because it lets your reader verify the number — it is not a condition of use. This applies to the values, their units, periods and source references. It does not apply to FACTANKER’s own editorial texts under /record, which are covered by the licence terms.