• Primary point of contact for HCPs and stakeholders • Build business account strategies with practical insight from the field • Align and embed projects and plans to the overall brand plan • Develop local account plans and execute core strategy • Project manage agreed plans to deliver patient-focused outcomes • Organize and act as a speaker in clinical sessions in hospitals

• Work cross-functionally with the BlueLabs project teams to design our polling solutions. • Manage other members of the polling team, reviewing their work, and providing regular and ongoing feedback, coaching, mentorship, and learning and development opportunities. • Oversee the polling process from end-to-end, including programming survey questionnaires, pulling samples, tracking and monitoring surveys while in the field, and weighting the results. • Help to prepare and deliver client deliverables such as toplines and crosstabs. • Determine final results in concert with the team and develop insights for clients in presentation materials. • Coordinate with team members on experiments, modeling, and other analytics surveys. • Collaborate with our Data Science team on polling methodology and to work on research questions to improve our operations and polling processes. • Work with the Director of Polling to suggest and implement polling process improvements and keep a pulse on new innovations in the industry. • Help oversee relevant vendor relationships; regularly interacting with and evaluating our vendors. • Other duties as assigned

• Lead and manage critical IT and cloud modernization initiatives • Establish technical roadmaps and ensure alignment with strategic goals and technical requirements • Drive initiatives that reduce technical debt, modernize legacy systems, and deliver high-quality technical solutions • Act as the technical execution lead for task orders, ensuring technical solutions are in alignment with overall system solution and achieve technical quality delivery outcomes • Develop and manage project timelines, budgets, and deliverables • Coordinate with stakeholders to gather requirements and evaluate modernization opportunities • Facilitate collaboration between task order owners and cross-functional teams • Foster a culture of continuous improvement by incorporating lessons learned into future efforts • Mentor team members, conduct performance evaluations, and identify training opportunities.

• Define and manage MNO acceptance strategies aligned with market launch, beta, and regional activation plans. • Develop standardized acceptance test plans using approved probe packs, test cases, and operator‑defined acceptance criteria. • Ensure acceptance scope aligns with CIQs, contractual obligations, and regional regulatory requirements. • Lead execution of operator acceptance testing across lab, controlled field, and live network environments. • Validate end‑to‑end service behavior including attach success, session persistence, mobility, throughput, latency, and service continuity. • Ensure acceptance execution is repeatable, traceable, and comparable across markets. • Track acceptance defects, deviations, and gaps against defined acceptance thresholds. • Coordinate with Service Acceptance engineering, RF teams, platform teams, and Service Assurance counterparts to drive resolution. • Clearly distinguish acceptance blocking issues from post‑acceptance optimization items. • Validate acceptance KPIs against operator‑defined SLOs and CIQ thresholds. • Ensure KPI definitions, measurement methods, and thresholds are consistent with OSS instrumentation. • Confirm that acceptance KPIs can be monitored post‑launch through NOC and Service Assurance tooling. • Produce acceptance artifacts including test plans, probe logs, KPI reports, defect summaries, and acceptance sign‑off packages. • Publish acceptance status and readiness reports for internal leadership and MNO stakeholders. • Ensure acceptance documentation supports governance, audits, and regulatory reviews. • Align acceptance results with OSS hooks, alarm definitions, and monitoring dashboards. • Ensure NOC playbooks and operational runbooks reflect validated acceptance scenarios. • Reduce post‑launch incidents and rework by ensuring acceptance outputs are operationally actionable. • Operator acceptance test strategies and execution plans. • Probe‑based acceptance results and KPI validation reports. • Defect logs, resolution tracking, and acceptance sign‑off artifacts. • OSS and NOC alignment inputs supporting operational readiness. • Acceptance documentation supporting pre‑launch, beta, and market activation milestones.