A BI (Business Intelligence) Developer focuses on designing, building, and optimizing dashboards, reports, and semantic models that deliver insights to business users. While Data Analysts focus on analysis and interpretation, BI Developers focus on how insights are packaged, delivered, and consumed at scale.

BI Developers ensure that data is not only accurate—but also usable, intuitive, and performant for decision-makers.

The Core Purpose of a BI Developer

At its core, the role of a BI Developer is to:

• Turn data into clear, usable dashboards and reports
• Design semantic models that support consistent metrics
• Optimize performance and usability
• Enable data consumption across the organization

BI Developers focus on the last mile of analytics.

Typical Responsibilities of a BI Developer

While responsibilities vary by organization, BI Developers typically work across the following areas.

Designing Dashboards and Reports

BI Developers:

• Translate business requirements into visual designs
• Choose appropriate charts and layouts
• Focus on clarity, usability, and storytelling
• Design for different audiences (executives, managers, operators)

Good BI design reduces cognitive load and increases insight adoption.

Building and Maintaining Semantic Models

BI Developers often:

• Define relationships, measures, and calculations
• Implement business logic in semantic layers
• Optimize models for performance and reuse
• Ensure metric consistency across reports

This layer is critical for trusted analytics.

Optimizing Performance and Scalability

BI Developers:

• Improve query performance
• Reduce unnecessary complexity in reports
• Manage aggregations and caching strategies
• Balance flexibility with performance

Slow or unreliable dashboards quickly lose trust.

Enabling Self-Service Analytics

By building reusable models and templates, BI Developers:

• Empower users to build their own reports
• Reduce duplication and rework
• Provide guardrails for self-service
• Support governance without limiting agility

They play a key role in self-service success.

Collaborating Across Data Teams

BI Developers work closely with:

• Data Analysts on requirements and insights
• Analytics Engineers on data models
• Data Engineers on performance and data availability
• Data Architects on standards and platform alignment

They often act as a bridge between technical teams and business users.

Common Tools Used by BI Developers

BI Developers typically work with:

• BI & Data Visualization Tools
• Semantic Modeling and Metrics Layers
• SQL for validation and analysis
• DAX or Similar Expression Languages
• Performance Tuning and Monitoring Tools
• Collaboration and Sharing Platforms

The focus is on usability, performance, and trust.

What a BI Developer Is Not

Clarifying boundaries helps avoid role confusion.

A BI Developer is typically not:

• A data engineer building ingestion pipelines
• A data scientist creating predictive models
• A purely business-facing analyst
• A graphic designer focused only on aesthetics

They combine technical skill with analytical and design thinking.

What the Role Looks Like Day-to-Day

A typical day for a BI Developer may include:

• Designing or refining dashboards
• Validating metrics and calculations
• Optimizing report performance
• Responding to user feedback
• Supporting self-service users
• Troubleshooting data or visualization issues

Much of the work is iterative and user-driven.

How the Role Evolves Over Time

As organizations mature, the BI Developer role evolves:

• From static reports → interactive analytics
• From individual dashboards → standardized platforms
• From report builders → analytics product owners
• From reactive fixes → proactive design and governance

Senior BI Developers often lead analytics UX and standards.

Why BI Developers Are So Important

BI Developers add value by:

• Making insights accessible and actionable
• Improving adoption of analytics
• Ensuring consistency and trust
• Scaling analytics across diverse audiences

They turn data into something people actually use.

Final Thoughts

A BI Developer’s job is not just to build dashboards—it is to design experiences that help people understand and act on data.

When BI Developers do their job well, analytics becomes intuitive, trusted, and embedded into everyday decision-making.

A Machine Learning (ML) Engineer is responsible for turning machine learning models into reliable, scalable, production-grade systems. While Data Scientists focus on model development and experimentation, ML Engineers focus on deployment, automation, performance, and lifecycle management.

Their work ensures that models deliver real business value beyond notebooks and prototypes.

The Core Purpose of a Machine Learning Engineer

At its core, the role of a Machine Learning Engineer is to:

• Productionize machine learning models
• Build scalable and reliable ML systems
• Automate training, deployment, and monitoring
• Ensure models perform well in real-world conditions

ML Engineers sit at the intersection of software engineering, data engineering, and machine learning.

Typical Responsibilities of a Machine Learning Engineer

While responsibilities vary by organization, ML Engineers typically work across the following areas.

Deploying and Serving Machine Learning Models

ML Engineers:

• Package models for production
• Deploy models as APIs or batch jobs
• Manage model versions and rollouts
• Ensure low latency and high availability

This is where ML becomes usable by applications and users.

Building ML Pipelines and Automation

ML Engineers design and maintain:

• Automated training pipelines
• Feature generation and validation workflows
• Continuous integration and deployment (CI/CD) for ML
• Scheduled retraining processes

Automation is critical for scaling ML across use cases.

Monitoring and Maintaining Models in Production

Once deployed, ML Engineers:

• Monitor model performance and drift
• Track data quality and feature distributions
• Detect bias, degradation, or failures
• Trigger retraining or rollback when needed

Models are living systems, not one-time deployments.

Optimizing Performance and Reliability

ML Engineers focus on:

• Model inference speed and scalability
• Resource usage and cost optimization
• Fault tolerance and resiliency
• Security and access control

Production ML must meet engineering standards.

Collaborating Across Teams

ML Engineers work closely with:

• Data Scientists on model design and validation
• Data Engineers on data pipelines and feature stores
• AI Engineers on broader AI systems
• Software Engineers on application integration
• Data Architects on platform design

They translate research into production systems.

Common Tools Used by Machine Learning Engineers

ML Engineers commonly work with:

• Machine Learning Frameworks
• Model Serving and API Frameworks
• ML Platforms and Pipelines
• Feature Stores
• Monitoring and Observability Tools
• Cloud Infrastructure and Containers

Tool choice is driven by scalability, reliability, and maintainability.

What a Machine Learning Engineer Is Not

Clarifying this role helps avoid confusion.

A Machine Learning Engineer is typically not:

• A data analyst creating reports
• A data scientist focused only on experimentation
• A general software engineer with no ML context
• A research scientist working on novel algorithms

Their focus is operational ML.

What the Role Looks Like Day-to-Day

A typical day for a Machine Learning Engineer may include:

• Deploying or updating models
• Reviewing training or inference pipelines
• Monitoring production performance
• Investigating model or data issues
• Improving automation and reliability
• Collaborating on new ML use cases

Much of the work happens after the model is built.

How the Role Evolves Over Time

As organizations mature, the ML Engineer role evolves:

• From manual deployments → automated MLOps
• From isolated models → shared ML platforms
• From single use cases → enterprise ML systems
• From reactive fixes → proactive optimization

Senior ML Engineers often lead ML platform and MLOps strategy.

Why Machine Learning Engineers Are So Important

ML Engineers add value by:

• Bridging the gap between research and production
• Making ML reliable and scalable
• Reducing operational risk
• Enabling faster delivery of AI-powered features

Without ML Engineers, many ML initiatives fail to reach production.

Final Thoughts

A Machine Learning Engineer’s job is not to invent new models—it is to make machine learning work reliably in the real world.

When ML Engineers do their job well, organizations can confidently deploy, scale, and trust machine learning systems as part of everyday operations.

Overview

Document processing workloads use Artificial Intelligence (AI) to extract, analyze, and organize information from documents. These documents are often semi-structured or unstructured and may include scanned images, PDFs, forms, invoices, receipts, or contracts.

For the AI-900: Microsoft Azure AI Fundamentals exam, the emphasis is on recognizing document processing scenarios, understanding what problems they solve, and identifying which Azure AI services are typically used—not on implementation or coding.

This topic falls under:

• Describe Artificial Intelligence workloads and considerations (15–20%)
  • Identify features of common AI workloads

What Is a Document Processing Workload?

A document processing workload focuses on extracting structured information from documents that are primarily text-based but may also contain tables, forms, handwriting, and images.

These workloads often combine capabilities from:

• Computer vision (reading text from images)
• Natural language processing (understanding extracted text)

Common inputs:

• Scanned PDFs
• Images of receipts or invoices
• Forms and applications
• Contracts and reports

Common outputs:

• Extracted text
• Key-value pairs
• Tables and line items
• Structured data stored in databases

Common Document Processing Use Cases

On the AI-900 exam, document processing workloads are usually described through business automation scenarios.

Optical Character Recognition (OCR)

What it does: Extracts printed or handwritten text from images or scanned documents.

Example scenarios:

• Digitizing paper documents
• Reading text from scanned contracts
• Extracting text from images of receipts

Key idea: OCR converts visual text into machine-readable text.

Form Processing

What it does: Extracts structured information such as fields, key-value pairs, and tables from standardized or semi-standardized forms.

Example scenarios:

• Processing loan applications
• Extracting data from tax forms
• Reading insurance claim forms

Key idea: Form processing focuses on structured data extraction, not just raw text.

Receipt and Invoice Processing

What it does: Extracts common fields such as vendor name, date, total amount, and line items.

Example scenarios:

• Automating expense reporting
• Processing supplier invoices
• Auditing financial documents

Key idea: This is a specialized form of document processing optimized for common business documents.

Table Extraction

What it does: Identifies and extracts tabular data from documents.

Example scenarios:

• Extracting tables from PDFs
• Importing spreadsheet-like data from scanned reports

Handwritten Text Recognition

What it does: Extracts handwritten content from documents.

Example scenarios:

• Processing handwritten forms
• Digitizing handwritten notes

Azure Services Commonly Associated with Document Processing

For AI-900, you should recognize these services at a high level.

Azure AI Document Intelligence (formerly Form Recognizer)

Supports:

• OCR
• Form processing
• Invoice and receipt analysis
• Table extraction

This is the primary service associated with document processing workloads on the exam.

Azure AI Vision

Supports:

• Basic OCR

Used when scenarios mention simple text extraction from images rather than full document understanding.

How Document Processing Differs from Other AI Workloads

Understanding these distinctions is essential for AI-900.

Exam tip: If the scenario mentions forms, invoices, receipts, PDFs, or document automation, think document processing first.

Responsible AI Considerations

Document processing workloads often involve sensitive information.

Key considerations include:

• Protecting personal and financial data
• Ensuring secure document storage
• Limiting access to extracted information

AI-900 focuses on awareness, not technical controls.

Exam Tips for Identifying Document Processing Workloads

• Look for keywords like invoice, receipt, form, contract, PDF, scanned document
• Identify whether the goal is extracting structured data, not just reading text
• Choose document processing over NLP if the input is primarily a document
• Remember that OCR alone may not be sufficient for full document understanding

Summary

For the AI-900 exam, you should be able to:

• Recognize document processing scenarios
• Identify common document processing capabilities such as OCR and form extraction
• Associate document processing workloads with Azure AI Document Intelligence
• Distinguish document processing from vision and NLP workloads

A solid understanding of document processing workloads will help you answer several scenario-based questions with confidence.

Go to the Practice Exam Questions for this topic.

Go to the PL-300 Exam Prep Hub main page.