Russian hacker, Vladimir Leonidovitch Levin, attempted the biggest bank heist the world had ever seen via dial-up internet in 1994, Zia Hayat, Callsign CEO and founder, was hooked - armchair fraud became a real possibility. From this moment, Zia knew he wanted to play a part in stopping the bad guys and securing the internet for all. Founded In 2012, Callsign's mission has been to make Digital Identity simple and secure for everyone and everything. In that time, we've grown to over 200 employees, opened offices in Singapore and Abu Dhabi, been recognised as a WEF Global Innovator and our technology is being used by many of the world's leading financial institutions to keep millions of consumers safe. But we aren't stopping here. The identity revolution has only just begun, and we are looking to hire the brightest and inquisitive minds to help us make every web, mobile and physical Interaction seamless and secure. If this sounds like you, lets chat. Responsibilities in detail: Requirements Gathering:
Responsible for eliciting the requirements - from multiple stakeholders - and uncover the underlying business issues that need addressed through the solution requirements.
This may also require reading technical specifications (to understand technical concepts) and give a broader understanding that will better inform pragmatic and logical user stories and acceptance criteria
From time-to-time attend external client meetings and facilitate elicitation of requirements from third parties
Communicating:
Responsible for analysing these requirements via organizing, specifying and communicating to ensure they are complete and unambiguous with Engineering and Stakeholders
Supporting Agile ceremonies and engineering
Delivery Artefacts:
Responsible for formalising requirements into understandable Epics, User Stories or Technical Stories following commonly prescribed formats for the scrum team to work on. These stories form the Product Backlog Items on JIRA/Confluence.
Elaborate the Acceptance Criteria for User Stories and Technical Stories enabling BDD and test automation.
Conducting post-mortems and defect management on technical issues.
Become an Expert:
In an advisory capacity to one or many Product Managers the Product Analyst should be the leading expert on requirements analysis, MVP, user stories and prioritisation methods
In an advisory capacity - and in some cases a Product Manager Proxy - the Product Analyst should build (ultimately bring) good product and systems understanding and be able to clearly support the team, communicate, answer questions OR own actions to clarify use cases, journeys, product capabilities that may arise during any Agile ceremony or Sprint. This does not mean they are Technical Solutions experts, but can speak more about logical expectations and clarify acceptance criteria and outcomes.
Management and Work Style:
He/She should still defer to the Product Manager or Product Head for final decision making (where appropriate).
Product Analysts are expected to work across Product Domains and utilise this cross-domain experience to drive consistencies in product and customer treatments
Support other members of the Product Team
Requirements
Analysing and validating business requirements, translating into technical specifications/requirements.
Evaluating core platform changes versus client specific requests.
Designing client solutions / architecture.
Collaborating with engineering, obtaining a deep technical understanding of Callsign and associated roadmap.
Co-ordinating impact and requirements across projects.
Supporting client staging and development instances.