Senior Technical Business Systems Analyst

Job Summary

Senior Technical Business Systems Analyst –Digital Services Platform (DISP) –to support HOOPP’s Member portal APIs and data flows. The Analyst is the primary owner of business‑to‑technology translation, ensuring that pension data, rules, workflows, audit needs and edge cases are accurately represented in platform orchestration APIs.

• Pension plan membership (world class defined benefit pension plan).

• 100% company‑paid extended health and dental benefits for permanent employees, including coverage for mental health, gender‑affirmation, fertility, drug treatment, psychological support (up to $2,500 per year), parental leave top‑up, and a health spending account.

• Optional post‑retirement health and dental benefits subsidised 50%.

• Wellness offerings: yoga classes, meditation workshops, nutritional consultations and wellness seminars.

• API and Data Flow Analysis
  • Lead analysis and definition of DISP Orchestration / Backend‑for‑Frontend API requirements for new member portal digital experiences.
  • Own API functional contracts – inputs, outputs, payload fields, validation rules, transformations, source‑of‑truth logic, error conditions, edge cases, and acceptance criteria.
  • Document read, write, and long‑running operations, distinguishing synchronous, asynchronous, cached, workflow‑driven, and reconciled processes.
  • Map end‑to‑end data lineage across core systems, DISP proxy services, orchestration APIs, caches or member data stores, Contentful or front‑end configuration points, and React‑based user experiences.
  • Translate complex pension rules into deterministic system behaviour for all stakeholders.
  • Partner with API Integration Engineers to ensure APIs reflect business intent and user‑experience needs.
  • Define field‑level rules for entitlements, member status, eligibility, suppression logic, conditional display, fallback behaviour, timeout/error states, and audit‑sensitive transactions.
  • Analyze data impacts for scenarios such as member profile updates, beneficiary changes, pension projections, notifications, messages, secure documents, and dashboard personalization.
  • Identify data‑quality issues, source‑system limitations, rule conflicts, latency risks, caching risks, and security/privacy implications before build.
  • Maintain traceability from BRDs and FDS artifacts through API requirements, ADO work items, test scenarios, defects, release scope, and operational acceptance criteria.
  • Ensure requirements account for auditability, regulatory expectations, privacy, member‑impact risk, data stewardship, and supportability in production.
• Agile and Collaboration
  • Write engineering‑ready ADO requirements with precise acceptance criteria, clear business rules, data mappings, payload expectations, non‑functional considerations, and testable outcomes.
  • Run or support API mapping workshops, requirements walkthroughs, data lineage reviews, integration design reviews, defect triage, backlog refinement, sprint planning, demos, and release‑readiness reviews.
  • Review API designs, payload examples, mapping documents, FDS content, test cases, and defects to validate alignment with documented requirements and pension rules.
  • Proactively surface integration risks, data gaps, rule conflicts, cross‑squad dependencies, and downstream system impacts.
  • Challenge assumptions from business or technology teams when proposed designs increase risk, reduce auditability, create brittle dependencies, or misrepresent pension rules.
  • Build strong working relationships across HOOPP and partner teams to improve delivery predictability, requirement quality, and platform trust.
• Delivery and Governance
  • Own the analysis path from early discovery through design, build, testing, implementation, operational readiness, and post‑release learning for API and data‑flow work streams.
  • Support QA by ensuring test scenarios cover normal flows, edge cases, negative paths, source‑system failures, retry behaviour, stale data, cache behaviour, permissions, and downstream workflow impacts.
  • Support release planning by identifying analysis dependencies, unresolved business decisions, data readiness issues, API contract changes, migration considerations,…