🧠 AI Computer Institute
Content is AI-generated for educational purposes. Verify critical information independently. A bharath.ai initiative.

Ethics in AI: When Machines Make Unfair Decisions

📚 AI and Society⏱️ 17 min read🎓 Grade 8

📋 Before You Start

To get the most from this chapter, you should be comfortable with: foundational concepts in computer science, basic problem-solving skills

Ethics in AI: When Machines Make Unfair Decisions

An AI system denies a loan to a qualified applicant because of their zip code. Another AI fails to recognize people with darker skin tones in a photo app. A third AI recommends longer jail sentences to people of a certain race. These are not fictional scenarios—they are real problems that have happened in the world of artificial intelligence.

Ethics in AI is not abstract philosophy; it's a practical issue that affects millions of real people.

Key Concept: Bias in AI systems typically comes from biased training data. If your training data reflects historical discrimination, your AI model will learn and perpetuate that discrimination. The problem is: "Garbage in, garbage out."

The Bias Problem: Real Examples

Example 1: Facial Recognition and Darker Skin Tones

In 2018, it was discovered that facial recognition systems (used by law enforcement, airports, banks) had error rates of:

  • 0.3% for white men
  • 34% for dark-skinned women

Why? The training data used to build these systems contained mostly photos of white people. The AI learned facial features primarily from lighter skin tones and performed poorly on darker skin.


# Example: Biased training data

training_data_faces = {
    "light_skin": 950000,      # 95% of training data
    "dark_skin": 50000         # 5% of training data
}

# When AI is trained with imbalanced data, it performs better on the majority class
# This is a real problem in many facial recognition systems

# Impact: A dark-skinned person is misidentified as someone else
# Real world: Wrong people arrested, denied jobs, etc.

Example 2: Loan Approval Algorithm

A bank's AI system denies loans to people from certain neighborhoods, even if they have good credit scores. Why? Historical data shows that people from those neighborhoods defaulted more often. But this data itself reflects historical discrimination—those neighborhoods were systematically denied loans 50 years ago, leading to economic hardship today.

Real World: Amazon stopped using an AI hiring tool because it was biased against women. The AI learned from historical hiring decisions, and since tech companies historically hired more men, it learned to prefer male candidates. Amazon could not remove the bias without changing the data or algorithm.

The Aadhaar Challenge in India

India's Aadhaar system is the world's largest biometric database with over 1.3 billion people. While innovative, it raises ethical questions:

  • Privacy: Should the government have everyone's biometric data?
  • Accuracy: Does it work equally well for all skin tones and ages? (Elderly people have low match rates)
  • Scope Creep: Originally for welfare distribution, now used for everything. Should it be?
  • Exclusion: If Aadhaar authentication fails, people are denied services (food, bank access)

These are hard questions with no easy answers. But they must be asked and debated by society.

Types of Bias in AI

Type of Bias Example Impact
Training Data Bias Facial recognition trained mostly on white faces Poor accuracy for other races
Selection Bias Hiring AI trained on past employees (mostly men in tech) AI discriminates against women applicants
Algorithmic Bias Recidivism algorithm (predicts re-offense) assigns higher risk to minorities Longer jail sentences for protected groups
Feedback Loop Bias Loan denials → harder economic situation → more defaults → "validated" bias Perpetuates historical discrimination

How to Reduce Bias in AI Systems

1. Diverse Training Data


# Bad: Training data skewed towards majority
training_data = {
    "positive_examples": 9000,      # Mostly one class
    "negative_examples": 100        # Minority severely underrepresented
}

# Good: Balanced or representative training data
training_data_balanced = {
    "positive_examples": 5000,      # Representative of real-world distribution
    "negative_examples": 5000
}

# Solution: Collect diverse data
# For facial recognition: Include all skin tones, ages, genders equally
# For hiring: Include diverse pool of candidates

2. Test for Bias


# Measure accuracy separately for each demographic group
# If one group has much lower accuracy, there's bias

facial_recognition_accuracy = {
    "light_skin_male": 0.98,
    "light_skin_female": 0.97,
    "dark_skin_male": 0.64,        # BIAS DETECTED!
    "dark_skin_female": 0.66       # BIAS DETECTED!
}

# Action: This system should NOT be deployed until accuracy is equalized

3. Diverse Teams

Teams that build AI should include people from diverse backgrounds. They catch biases that homogeneous teams miss.

4. Explainability and Transparency

AI decisions affecting people (loan denials, job rejections, bail recommendations) should be explainable. People should know why they were rejected and be able to appeal.

Code Challenge: Imagine you're building an AI to predict house prices in Mumbai. Your training data has 1000 houses, but 900 of them are from posh neighborhoods (South Mumbai) and only 100 are from middle-class areas. Describe: (1) What bias might this create? (2) How would this bias appear when the model makes predictions? (3) How would you fix it?

Responsible AI Principles

Principles that major tech companies now follow:

  1. Fairness: AI should not discriminate. Accuracy should be similar across all demographic groups.
  2. Transparency: People should understand how AI makes decisions.
  3. Accountability: Someone should be responsible if AI causes harm.
  4. Privacy: AI should not unnecessarily collect or expose personal data.
  5. Safety: AI should be robust and not cause unexpected harm.

Google, Microsoft, Apple, Amazon, and major Indian tech companies (TCS, Infosys, Wipro) now have dedicated ethics teams reviewing AI systems before deployment.

India's Role in Ethical AI

India has unique opportunities and challenges:

  • Opportunity: India's diverse population (22 official languages, many religions, regions) can help build AI that works for everyone
  • Challenge: Historical biases based on caste, religion, gender must be actively addressed
  • Data Privacy: India's data protection is evolving (DPDP Act, 2023). India should lead in privacy-protecting AI

As a student entering the AI field, you have a choice. You can either build AI systems that inadvertently perpetuate discrimination, or you can be the generation that builds AI systems that are fair, transparent, and ethical.

Remember: With great power comes great responsibility. AI is powerful. Use it responsibly.

📝 Key Takeaways

  • ✅ This topic is fundamental to understanding how data and computation work
  • ✅ Mastering these concepts opens doors to more advanced topics
  • ✅ Practice and experimentation are key to deep understanding

From Concept to Reality: Ethics in AI: When Machines Make Unfair Decisions

In the professional world, the difference between a good engineer and a great one often comes down to understanding fundamentals deeply. Anyone can copy code from Stack Overflow. But when that code breaks at 2 AM and your application is down — affecting millions of users — only someone who truly understands the underlying concepts can diagnose and fix the problem.

Ethics in AI: When Machines Make Unfair Decisions is one of those fundamentals. Whether you end up working at Google, building your own startup, or applying CS to solve problems in agriculture, healthcare, or education, these concepts will be the foundation everything else is built on. Indian engineers are known globally for their strong fundamentals — this is why companies worldwide recruit from IITs, NITs, IIIT Hyderabad, and BITS Pilani. Let us make sure you have that same strong foundation.

Neural Networks: Layers of Learning

A neural network is inspired by how your brain works. Your brain has billions of neurons connected to each other. When you see, hear, or think something, electrical signals flow through these connections. A neural network simulates this with layers of mathematical operations:

  INPUT LAYER          HIDDEN LAYERS          OUTPUT LAYER
  (Raw Data)           (Feature Extraction)    (Decision)

  Pixel 1 ──┐
  Pixel 2 ──┤    ┌─[Neuron]─┐
  Pixel 3 ──┼───▶│ Edges &   │───┐
  Pixel 4 ──┤    │ Corners   │   │    ┌─[Neuron]─┐
  Pixel 5 ──┤    └───────────┘   ├───▶│ Face     │──▶ "It's a cat!" (92%)
  ...       │    ┌─[Neuron]─┐   │    │ Features │      "It's a dog" (7%)
  Pixel N ──┤    │ Shapes & │───┘    │ + Body   │      "Other" (1%)
             └───▶│ Textures │───────▶│ Shape    │
                  └───────────┘       └──────────┘

  Layer 1: Detects simple features (edges, gradients)
  Layer 2: Combines into complex features (eyes, ears, whiskers)
  Layer 3: Makes the final decision based on all features

Each connection between neurons has a "weight" — a number that determines how important that connection is. During training, the network adjusts these weights to minimise errors. This is done using an algorithm called backpropagation combined with gradient descent. The loss function measures how wrong the network is, and gradient descent follows the slope downhill to find better weights.

Modern networks like GPT-4 have billions of parameters (weights) and are trained on massive GPU clusters. India's Sarvam AI is training models specifically for Indian languages — Hindi, Tamil, Telugu, Bengali, and more — because global models often perform poorly on Indic scripts and cultural contexts.

Did You Know?

🚀 ISRO is the world's 4th largest space agency, powered by Indian engineers. With a budget smaller than some Hollywood blockbusters, ISRO does things that cost 10x more for other countries. The Mangalyaan (Mars Orbiter Mission) proved India could reach Mars for the cost of a film. Chandrayaan-3 succeeded where others failed. This is efficiency and engineering brilliance that the world studies.

🏥 AI-powered healthcare diagnosis is being developed in India. Indian startups and research labs are building AI systems that can detect cancer, tuberculosis, and retinopathy from images — better than human doctors in some cases. These systems are being deployed in rural clinics across India, bringing world-class healthcare to millions who otherwise could not afford it.

🌾 Agriculture technology is transforming Indian farming. Drones with computer vision scan crop health. IoT sensors in soil measure moisture and nutrients. AI models predict yields and optimal planting times. Companies like Ninjacart and SoilCompanion are using these technologies to help farmers earn 2-3x more. This is computer science changing millions of lives in real-time.

💰 India has more coding experts per capita than most Western countries. India hosts platforms like CodeChef, which has over 15 million users worldwide. Indians dominate competitive programming rankings. Companies like Flipkart and Razorpay are building world-class engineering cultures. The talent is real, and if you stick with computer science, you will be part of this story.

Real-World System Design: Swiggy's Architecture

When you order food on Swiggy, here is what happens behind the scenes in about 2 seconds: your location is geocoded (algorithms), nearby restaurants are queried from a spatial index (data structures), menu prices are pulled from a database (SQL), delivery time is estimated using ML models trained on historical data (AI), the order is placed in a distributed message queue (Kafka), a delivery partner is assigned using a matching algorithm (optimization), and real-time tracking begins using WebSocket connections (networking). EVERY concept in your CS curriculum is being used simultaneously to deliver your biryani.

The Process: How Ethics in AI: When Machines Make Unfair Decisions Works in Production

In professional engineering, implementing ethics in ai: when machines make unfair decisions requires a systematic approach that balances correctness, performance, and maintainability:

Step 1: Requirements Analysis and Design Trade-offs
Start with a clear specification: what does this system need to do? What are the performance requirements (latency, throughput)? What about reliability (how often can it fail)? What constraints exist (memory, disk, network)? Engineers create detailed design documents, often including complexity analysis (how does the system scale as data grows?).

Step 2: Architecture and System Design
Design the system architecture: what components exist? How do they communicate? Where are the critical paths? Use design patterns (proven solutions to common problems) to avoid reinventing the wheel. For distributed systems, consider: how do we handle failures? How do we ensure consistency across multiple servers? These questions determine the entire architecture.

Step 3: Implementation with Code Review and Testing
Write the code following the architecture. But here is the thing — it is not a solo activity. Other engineers read and critique the code (code review). They ask: is this maintainable? Are there subtle bugs? Can we optimize this? Meanwhile, automated tests verify every piece of functionality, from unit tests (testing individual functions) to integration tests (testing how components work together).

Step 4: Performance Optimization and Profiling
Measure where the system is slow. Use profilers (tools that measure where time is spent). Optimize the bottlenecks. Sometimes this means algorithmic improvements (choosing a smarter algorithm). Sometimes it means system-level improvements (using caching, adding more servers, optimizing database queries). Always profile before and after to prove the optimization worked.

Step 5: Deployment, Monitoring, and Iteration
Deploy gradually, not all at once. Run A/B tests (comparing two versions) to ensure the new system is better. Once live, monitor relentlessly: metrics dashboards, logs, traces. If issues arise, implement circuit breakers and graceful degradation (keeping the system partially functional rather than crashing completely). Then iterate — version 2.0 will be better than 1.0 based on lessons learned.


Algorithm Complexity and Big-O Notation

Big-O notation describes how an algorithm's performance scales with input size. This is THE most important concept for coding interviews:

  BIG-O COMPARISON (n = 1,000,000 elements):

  O(1)        Constant     1 operation          Hash table lookup
  O(log n)    Logarithmic  20 operations        Binary search
  O(n)        Linear       1,000,000 ops        Linear search
  O(n log n)  Linearithmic 20,000,000 ops       Merge sort, Quick sort
  O(n²)       Quadratic    1,000,000,000,000    Bubble sort, Selection sort
  O(2ⁿ)       Exponential  ∞ (universe dies)    Brute force subset

  Time at 1 billion ops/sec:
  O(n log n): 0.02 seconds    ← Perfectly usable
  O(n²):      11.5 DAYS       ← Completely unusable!
  O(2ⁿ):      Longer than the age of the universe

  # Python example: Merge Sort (O(n log n))
  def merge_sort(arr):
      if len(arr) <= 1:
          return arr
      mid = len(arr) // 2
      left = merge_sort(arr[:mid])      # Sort left half
      right = merge_sort(arr[mid:])     # Sort right half
      return merge(left, right)         # Merge sorted halves

  def merge(left, right):
      result = []
      i = j = 0
      while i < len(left) and j < len(right):
          if left[i] <= right[j]:
              result.append(left[i]); i += 1
          else:
              result.append(right[j]); j += 1
      result.extend(left[i:])
      result.extend(right[j:])
      return result

This matters in the real world. India's Aadhaar system must search through 1.4 billion biometric records for every authentication request. At O(n), that would take seconds per request. With the right data structures (hash tables, B-trees), it takes milliseconds. The algorithm choice is the difference between a working system and an unusable one.

Real Story from India

The India Stack Revolution

In the early 1990s, India's economy was closed. Indians could not easily send money abroad or access international services. But starting in 1991, India opened its economy. Young engineers in Bangalore, Hyderabad, and Chennai saw this as an opportunity. They built software companies (Infosys, TCS, Wipro) that served the world.

Fast forward to 2008. India had a problem: 500 million Indians had no formal identity. No bank account, no passport, no way to access government services. The government decided: let us use technology to solve this. UIDAI (Unique Identification Authority of India) was created, and engineers designed Aadhaar.

Aadhaar collects fingerprints and iris scans from every Indian, stores them in massive databases using sophisticated encryption, and allows anyone (even a street vendor) to verify identity instantly. Today, 1.4 billion Indians have Aadhaar. On top of Aadhaar, engineers built UPI (digital payments), Jan Dhan (bank accounts), and ONDC (open e-commerce network).

This entire stack — Aadhaar, UPI, Jan Dhan, ONDC — is called the India Stack. It is considered the most advanced digital infrastructure in the world. Governments and companies everywhere are trying to copy it. And it was built by Indian engineers using computer science concepts that you are learning right now.

Production Engineering: Ethics in AI: When Machines Make Unfair Decisions at Scale

Understanding ethics in ai: when machines make unfair decisions at an academic level is necessary but not sufficient. Let us examine how these concepts manifest in production environments where failure has real consequences.

Consider India's UPI system processing 10+ billion transactions monthly. The architecture must guarantee: atomicity (a transfer either completes fully or not at all — no half-transfers), consistency (balances always add up correctly across all banks), isolation (concurrent transactions on the same account do not interfere), and durability (once confirmed, a transaction survives any failure). These are the ACID properties, and violating any one of them in a payment system would cause financial chaos for millions of people.

At scale, you also face the thundering herd problem: what happens when a million users check their exam results at the same time? (CBSE result day, anyone?) Without rate limiting, connection pooling, caching, and graceful degradation, the system crashes. Good engineering means designing for the worst case while optimising for the common case. Companies like NPCI (the organisation behind UPI) invest heavily in load testing — simulating peak traffic to identify bottlenecks before they affect real users.

Monitoring and observability become critical at scale. You need metrics (how many requests per second? what is the 99th percentile latency?), logs (what happened when something went wrong?), and traces (how did a single request flow through 15 different microservices?). Tools like Prometheus, Grafana, ELK Stack, and Jaeger are standard in Indian tech companies. When Hotstar streams IPL to 50 million concurrent users, their engineering team watches these dashboards in real-time, ready to intervene if any metric goes anomalous.

The career implications are clear: engineers who understand both the theory (from chapters like this one) AND the practice (from building real systems) command the highest salaries and most interesting roles. India's top engineering talent earns ₹50-100+ LPA at companies like Google, Microsoft, and Goldman Sachs, or builds their own startups. The foundation starts here.

Checkpoint: Test Your Understanding 🎯

Before moving forward, ensure you can answer these:

Question 1: Explain the tradeoffs in ethics in ai: when machines make unfair decisions. What is better: speed or reliability? Can we have both? Why or why not?

Answer: Good engineers understand that there are always tradeoffs. Optimal depends on requirements — is this a real-time system or batch processing?

Question 2: How would you test if your implementation of ethics in ai: when machines make unfair decisions is correct and performant? What would you measure?

Answer: Correctness testing, performance benchmarking, edge case handling, failure scenarios — just like professional engineers do.

Question 3: If ethics in ai: when machines make unfair decisions fails in a production system (like UPI), what happens? How would you design to prevent or recover from failures?

Answer: Redundancy, failover systems, circuit breakers, graceful degradation — these are real concerns at scale.

Key Vocabulary

Here are important terms from this chapter that you should know:

Neural Network: An important concept in AI and Society
Gradient: An important concept in AI and Society
Epoch: An important concept in AI and Society
Loss Function: An important concept in AI and Society
Backpropagation: An important concept in AI and Society

💡 Interview-Style Problem

Here is a problem that frequently appears in technical interviews at companies like Google, Amazon, and Flipkart: "Design a URL shortener like bit.ly. How would you generate unique short codes? How would you handle millions of redirects per second? What database would you use and why? How would you track click analytics?"

Think about: hash functions for generating short codes, read-heavy workload (99% redirects, 1% creates) suggesting caching, database choice (Redis for cache, PostgreSQL for persistence), and horizontal scaling with consistent hashing. Try sketching the system architecture on paper before looking up solutions. The ability to think through system design problems is the single most valuable skill for senior engineering roles.

Where This Takes You

The knowledge you have gained about ethics in ai: when machines make unfair decisions is directly applicable to: competitive programming (Codeforces, CodeChef — India has the 2nd largest competitive programming community globally), open-source contribution (India is the 2nd largest contributor on GitHub), placement preparation (these concepts form 60% of technical interview questions), and building real products (every startup needs engineers who understand these fundamentals).

India's tech ecosystem offers incredible opportunities. Freshers at top companies earn ₹15-50 LPA; experienced engineers at FAANG companies in India earn ₹50-1 Cr+. But more importantly, the problems being solved in India — digital payments for 1.4 billion people, healthcare AI for rural areas, agricultural tech for 150 million farmers — are some of the most impactful engineering challenges in the world. The fundamentals you are building will be the tools you use to tackle them.

Crafted for Class 7–9 • AI and Society • Aligned with NEP 2020 & CBSE Curriculum

← Databases: Where All the World's Information LivesPython Dictionaries and Sets: Organizing Data Smartly →
📱 Share on WhatsApp