Associate Director, Business Systems (Hybrid)

Wayne, United States of America | Full time | Hybrid | R1540482 We are seeking an Associate Director, Business Systems to partner closely with Product Managers, stakeholders and development teams on the Scion Delivery Platform portfolio. This Associate Director will translate stakeholder and client needs into clear, actionable product requirements for product development—bridging stakeholder requirements, client access, analytics experiences, and platform administration with engineering, design, and quality teams. This role is hands‑on in discovery, specification, and delivery support, with enough technical depth to validate feasibility, document behavior, and keep builds aligned to intent. Requirements and discovery Partner with the Product Manager to run discovery: stakeholder interviews, workflow mapping, pain‑point analysis, and scope definition for data delivery, client access, analytics, and administration capabilities. Strong understanding of pharmaceutical data and business applications. Good understanding of technical product development and methodology. Understanding of technologies and willingness to learn. Document as‑is / to‑be processes for client onboarding, delivery, configuration, access and analytics. Clear understanding of overall business needs and dependencies. Maintain a prioritized backlog of business needs, assumptions, open questions, and decisions with clear owners and dates. Support product discovery activities: problem statements, success metrics, MVP scope, and release phasing recommendations. Support requirement gathering for different types of applications to meet the delivery of data and analytics to the IQVIA stakeholders and customers. Product specification Author and maintain business requirements, functional specifications, and user stories with testable acceptance criteria aligned to the team’s delivery model. Produce structured specification artifacts: process flows, data definitions, screen/API behavior, error cases, and edge scenarios (including multi‑organization access patterns). Align requirements with API contracts and service boundaries—review OpenAPI definitions, flag gaps between business rules and documented endpoints, and track contract changes across releases. Define preconditions, process steps, and expected outcomes for key capabilities. Partner with engineering on data and integration touchpoints: what is created, updated, or provisioned downstream when a client or workspace is onboarded. Delivery support Refine backlog items for sprint planning; clarify scope, dependencies, and acceptance criteria with developers and testers before build starts. Support epic and feature breakdown into implementable units with clear sequencing (foundation → lifecycle → provisioning/observability). Participate in backlog refinement, sprint planning, demos, and retrospectives; capture decisions and change logs. Triage clarification requests during development; elevate scope or policy conflicts to the Product Manager with options and impact. Quality and validation Develop test scenarios, sample requests/responses, and validation checklists from requirements (positive, negative, and permission‑based cases). Partner with QA on test coverage mapping: trace requirements → stories → test cases; identify gaps before release. Support user acceptance testing: test scripts, defect triage, severity/impact notes, and sign‑off evidence. Verify delivered features against acceptance criteria and documented client/access rules. Governance and standards Apply the team’s product development standards: consistent story format, requirement templates, decision logs, and versioned specification storage. Help maintain a single source of truth between analysis‑design artifacts, API contracts, and implementation—reducing ambiguity and rework. Track cross‑team dependencies (access, analytics apps, admin, shared platform services) and surface risks early in the delivery cycle. Contribute to release notes and internal enablement materials for operations and client‑facing teams. Stakeholder collaboration Facilitate working sessions with engineering, architecture, security, operations, and client success. Translate technical constraints and delivery trade‑offs into business language for the Product Manager and stakeholders. Capture and communicate non‑functional expectations where relevant: security, auditability, performance, and regulated‑environment considerations. Qualifications Bachelor’s degree in Life Sciences, Information Systems, Computer Science, Business Analytics, or related field. 4+ years as a Business Analyst, Systems Analyst, or similar role in software product development (not IT‑only ticket intake). 2+ years in healthcare, life sciences, pharma, analytics platforms, or regulated B2B environments preferred. Demonstrated ability to write clear functional specs, user stories, and acceptance criteria used directly by engineering and QA. Working knowledge of API‑based products (REST, request/response validation, error models) and comfort reading OpenAPI or similar contract documentation. Familiarity with Agile/Scrum ceremonies and backlog refinement practices. Strong analytical, documentation, and facilitation skills; detail‑oriented with sound judgment on scope. Experience with multi‑client / multi‑organization access models, SaaS administration, or data/analytics products is a plus. Preferred attributes Comfortable working in ambiguous, fast‑moving product teams; proactive in closing gaps rather than waiting for perfect inputs. Able to go deep enough technically to challenge assumptions. Structured thinker who enjoys process, data, and behavior documentation more than slide‑only deliverables. Collaborative style with Product Managers, engineers, and testers; receptive to feedback and iterative refinement. Interest in analytics and client access domains; curiosity about how platform capabilities connect end‑to‑end. What success looks like (first 6–12 months) Requirements are implementation‑ready with minimal mid‑sprint rework. Strong traceability from business need → story → test scenario → release validation. Product Manager spends less time on spec drafting and clarification firefighting. Cross‑team dependencies and access/provisioning rules are documented before build, not after defects. Releases ship with clear acceptance evidence and updated specification artifacts. The potential base pay range for this role, when annualized, is $91,000.00 - $253,700.00. The actual base pay offered may vary based on a number of factors including job‑related qualifications such as knowledge, skills, education, and experience; location; and/or schedule (full or part‑time). Dependent on the position offered, incentive plans, bonuses, and/or other forms of compensation may be offered, in addition to a range of health and welfare and/or other benefits. IQVIA is proud to be an equal opportunity employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability, status as a protected veteran, or any other status protected by applicable law. IQVIA is committed to integrity in our hiring process and maintains a zero tolerance policy for candidate fraud. All information and credentials submitted in your application must be truthful and complete. Any false statements, misrepresentations, or material omissions during the recruitment process will result in immediate disqualification of your application, or termination of employment if discovered later, in accordance with applicable law. We appreciate your honesty and professionalism. #J-18808-Ljbffr IQVIA Argentina