Senior Business Analyst

As a Senior Business Analyst at DMI, your main responsibilities include translating business requirements into user stories and acceptance criteria, collaborating with product management and technical teams, and participating actively during release and sprint planning. With experience in Pharma and Clinical settings, particularly around eCOA and 21 CFR Part 11, you'll play a crucial role in ensuring solutions meet both technical and business needs.

To qualify for the Senior Business Analyst role at DMI, candidates should have 5-9 years of relevant experience, particularly in the Pharma and Clinical sectors. A solid understanding of Agile methodologies, excellent communication skills, and experience delivering software products are essential. Familiarity with 21 CFR Part 11 regulated environments is also highly desired.

Yes, the Senior Business Analyst position at DMI is mainly a remote role, although candidates are required to be on-site at the Lilly Bangalore office at least three days a week, contributing to a hybrid working environment.

As a Senior Business Analyst at DMI, you'll engage in a variety of projects primarily focused on delivering innovative software solutions for the Pharma and Clinical sectors. Your expertise in eCOA and clinical trial software development will be pivotal in driving our projects to success while ensuring user satisfaction and technical compatibility.

DMI offers a comprehensive benefits package to Senior Business Analysts, including healthcare options, wellness programs, professional development opportunities, and generous financial benefits like 401k matching and tuition assistance. We prioritize your well-being and strive to enrich your personal and professional growth.

When gathering requirements as a Senior Business Analyst, I focus on collaborative discussions with stakeholders to understand their needs fully. By utilizing techniques like interviews, surveys, and workshops, I ensure that all voices are heard, and I prioritize creating user stories that accurately reflect the project objectives.

Handling ambiguity in business requirements involves asking the right questions and conducting thorough research. I work closely with stakeholders to clarify uncertainties and break down large tasks into manageable user stories, facilitating a clearer direction for the team.

In my previous roles, I have had extensive experience with Agile methodologies, participating in daily stand-ups, sprint planning, and retrospectives. I believe in the iterative development process and have refined my skills in adapting requirements based on feedback to ensure continuous improvement.

One complex project I worked on was the integration of a new eCOA solution for clinical trials. I collaborated with various stakeholders to define the requirements, led sprint planning sessions, and developed user stories to ensure the project met regulatory standards while satisfying user needs.

Effective communication is crucial, and I make it a point to foster an open environment where team members feel comfortable sharing their thoughts. Regular check-ins, utilizing collaboration tools, and encouraging feedback help me maintain alignment throughout the project's lifecycle.

I utilize MoSCoW prioritization and engage in discussions with stakeholders to assess business value when prioritizing user stories. This allows me to focus on high-impact features that align with project goals and user needs.

In the event of conflicts within a project team, I believe in addressing the issue directly. I facilitate conversations to allow team members to express their viewpoints and work together towards a collaborative solution, emphasizing the common goals we share.

I commonly use tools like JIRA for project management, Confluence for documentation, and various prototyping tools to visualize requirements. These tools enhance collaboration and maintain transparency among team members.

I assess project success through stakeholder feedback, analyzing performance metrics, and ensuring that the project goals were met. Post-implementation reviews are crucial for identifying lessons learned and areas for improvement in future projects.

User experience is at the forefront of my analysis process. I actively involve users in the requirements phase to ensure their needs are captured, and I focus on creating user stories that enhance usability and engagement with the final product.