BI Developer at Tezza Business Solutions Ltd

As a BI Developer, you are the bridge between raw data and strategic action. Your mission is to transform complex datasets into actionable insights that help the organisation make smarter, faster decisions. You won’t just be “developing and running reports” rather creating stories of our business through data visualization and reporting. Stories that build journeys of information discovery that spot opportunities, identify problems and mitigate risks.

Role Objectives

• Move beyond static reporting by translating complex financial datasets into persuasive, narrative-driven insights.
• Build sophisticated, interactive visualizations that reveal deep-seated patterns that standard out-of-the-box tools cannot detect by leveraging python wide range of free-to-use libraries
• Democratise information access, empowering non-technical departments to self-serve through intuitive, well-governed dashboards while maintaining 100% accuracy for audit and compliance.
• Be an advocate for advanced data technologies, best practices and continuous learning.

Core Responsibilities

• Data Visualization & Reporting: Design, develop, and maintain interactive dashboards and reports using tools like Tableau, Power BI, or Qlik Sense.
• Advanced Visualization with Python: Utilize Python libraries like Matplotlib, Seaborn, and Plotly to transform complex data into actionable insights for risk management, fraud detection, and customer behavioural analysis.
• Data Pipeline Maintenance: Partner with Data Engineers to ensure that data pipelines deliver accurate and consistent datasets that meet business needs and requirements.
• Collaboration: Work closely with other business teams to understand reports/visualization requirements and deliver solutions within agreed timelines.
•  Documentation & Knowledge Management: Maintain a comprehensive reports/visualizations catalogue defining purpose, sources, generation, and target audience.
• Incident Management & Root Cause Analysis (RCA): Lead investigation into report failures, data discrepancies, and information delivery outages and consequently author formal RCA reports that move beyond “what happened” to “how to prevent repeat occurrence.”