Tech Roles and Career Paths

#The Tech Team: Who Does What?

There is a role for every kind of person. Whether you love art, math, talking to people, solving puzzles, or organizing chaos — there is a tech role that fits your personality. You do not have to be a "coder" to thrive in tech. This lesson will help you find your fit.

Software does not build itself. Behind every app you use (Instagram, Zomato, Paytm, Google Maps) there is a team of people with very different skills working together.

Think of it like making a Bollywood movie. You do not just need actors. You need a director, a cinematographer, set designers, sound engineers, editors, a music composer, and a producer to fund the whole thing. Everyone has a different job, but they all contribute to the final product.

Let us dive deep into each role. For every role, you will learn what they do, what a typical day looks like, what tools they use, what skills they need, how much they earn in India, and how AI is changing their work.

#Role Deep Dives

#1. Software Engineer / Developer

What they do in simple terms

Software engineers write the code that makes apps, websites, and software products work. They are the builders. When a product manager says "we need a search feature," the software engineer is the person who actually builds it.

There are three flavors:

• Frontend Developer. Builds what you see. The buttons, the layouts, the animations, the forms. When you scroll through Instagram and the feed loads smoothly, a frontend developer made that happen.
• Backend Developer. Builds what you don't see. The server that stores your data, the API that sends your messages, the logic that calculates your Uber fare. When you send a UPI payment and it reaches the right account in 2 seconds, a backend developer made that happen.
• Full-stack Developer. Does both. Common in startups where one person needs to handle everything.

A day in the life (9 AM to 6 PM)

Tools they use

• Editor: VS Code, Cursor, or JetBrains IDEs
• Version Control: Git + GitHub / GitLab
• Frontend: React, Next.js, TypeScript, Tailwind CSS
• Backend: Python (FastAPI/Django), Node.js, Java (Spring Boot), Go
• Database: PostgreSQL, MongoDB, Redis
• Communication: Slack, Jira, Notion
• AI Assistants: GitHub Copilot, Claude Code, Cursor AI

Skills required

• Technical: At least one programming language deeply (JavaScript/TypeScript or Python), data structures and algorithms, Git, API design, database basics
• Soft skills: Problem-solving, ability to break big problems into small ones, clear written communication (code reviews are essentially writing), patience for debugging

Salary range in India (per annum)

How AI is changing this role

AI coding assistants like GitHub Copilot and Claude Code can now write boilerplate code, suggest entire functions, and even fix bugs. This does NOT mean developers are being replaced. It means they are becoming faster. The skill is shifting from "writing every line by hand" to "reviewing AI-generated code, designing systems, and solving the hard problems that AI cannot." Think of it like calculators for mathematicians — the tool handles arithmetic so you can focus on higher-level thinking.

#2. Data Engineer

What they do in simple terms

If data is oil, data engineers build the pipelines that extract, transport, and refine it. They make sure the right data gets to the right place, at the right time, in the right format. Without data engineers, data scientists would have no clean data to analyze and ML models would have nothing to train on.

A day in the life (9 AM to 6 PM)

Tools they use

• Languages: Python, SQL (the most important skill), Scala
• Pipeline orchestration: Apache Airflow, Dagster, Prefect
• Data transformation: dbt (data build tool)
• Processing engines: Apache Spark, Apache Flink
• Cloud warehouses: BigQuery (GCP), Redshift (AWS), Snowflake
• Streaming: Apache Kafka, AWS Kinesis
• Monitoring: Datadog, Grafana, Great Expectations (data quality)

Skills required

• Technical: Advanced SQL (window functions, CTEs, optimization), Python, understanding of distributed systems, cloud platforms (AWS/GCP/Azure), data modeling (star schema, snowflake schema)
• Soft skills: Attention to detail (one wrong join can corrupt millions of rows), patience for debugging data issues at 2 AM, ability to communicate data architecture to non-technical stakeholders

Salary range in India (per annum)

How AI is changing this role

AI tools can now auto-generate SQL queries, suggest pipeline optimizations, and even detect data quality issues automatically. Tools like dbt with AI integration can write transformation logic from natural language descriptions. But data engineering is fundamentally about understanding messy real-world data systems — something AI struggles with. The role is shifting from "write ETL scripts by hand" to "design data architectures and use AI to accelerate pipeline development."

#3. Data Scientist

What they do in simple terms

Data scientists are the detectives of the tech world. They dig through data to find patterns, answer questions, and help the business make smarter decisions. "Which users are likely to cancel their subscription?" "Which product feature drives the most engagement?" "Is this marketing campaign actually working?" — a data scientist answers these questions with data, not gut feelings.

A day in the life (9 AM to 6 PM)

Tools they use

• Languages: Python (primary), R (some teams), SQL
• Notebooks: Jupyter Notebook, Google Colab
• Data manipulation: Pandas, NumPy
• ML libraries: Scikit-learn, XGBoost, LightGBM
• Visualization: Matplotlib, Seaborn, Plotly, Tableau, Power BI
• Experimentation: A/B testing frameworks, statistical testing
• Communication: PowerPoint / Google Slides (yes, really — presenting findings is half the job)

Skills required

• Technical: Statistics and probability (hypothesis testing, regression), Python, SQL, machine learning algorithms, data visualization, experimental design (A/B testing)
• Soft skills: Storytelling with data (the best data scientist is the one who can explain a complex finding to a CEO in 2 minutes), curiosity, business acumen (understanding what questions actually matter)

Salary range in India (per annum)

How AI is changing this role

This is the role most directly affected by AI. Tools like ChatGPT can now write exploratory data analysis code, generate visualizations, and even build basic ML models from natural language prompts. The routine parts of data science (cleaning data, running standard models) are being automated. But the strategic parts — figuring out what questions to ask, designing experiments, and translating insights into business decisions — still require a human who understands both the data and the business context. The role is evolving from "person who writes Python to analyze data" to "person who uses AI tools to analyze data 10x faster and focuses on strategy."

#4. AI/ML Engineer

What they do in simple terms

If a data scientist builds a model that works in a Jupyter notebook, the ML engineer is the person who makes it work in the real world — handling millions of requests per second, running on cloud servers, and not crashing at 3 AM. They bridge the gap between research and production. They also increasingly build AI-powered features using large language models, vector databases, and agent frameworks.

A day in the life (9 AM to 6 PM)

Tools they use

• ML frameworks: PyTorch (dominant), TensorFlow, JAX
• LLM tools: LangChain, LlamaIndex, Hugging Face Transformers, vLLM
• Experiment tracking: MLflow, Weights & Biases
• Model serving: TorchServe, Triton Inference Server, BentoML
• Vector databases: ChromaDB, Pinecone, Weaviate
• Infrastructure: Docker, Kubernetes, AWS SageMaker, GCP Vertex AI
• Languages: Python (primary), C++ (for optimization), Rust (emerging)

Skills required

• Technical: Deep understanding of neural networks and training, Python, PyTorch, Docker/Kubernetes, cloud platforms, model optimization (quantization, distillation, pruning), understanding of LLMs and prompt engineering
• Soft skills: Ability to translate research papers into production code, comfort with ambiguity (ML is inherently experimental), strong debugging skills (ML bugs are silent — the model just performs badly)

Salary range in India (per annum)

How AI is changing this role

Paradoxically, AI is making the ML engineer's job both easier and more complex. Tools like AutoML can handle routine model selection. LLM APIs (Claude, GPT-4) mean you do not always need to train a model from scratch — you can build powerful applications by orchestrating pre-trained models. But someone still needs to design the architecture, handle edge cases, optimize for cost and latency, and make sure the system is reliable. The role is expanding from "train and deploy models" to "architect AI systems using a mix of pre-trained models, fine-tuning, and custom training."

#5. DevOps / SRE Engineer

What they do in simple terms

DevOps (Development Operations) and SRE (Site Reliability Engineering) engineers are the people who keep your apps running. When you open Swiggy and it loads in under a second, that is because a DevOps engineer set up the infrastructure. When Netflix handles 200 million users streaming simultaneously without crashing, that is SRE at work. They automate deployments, manage cloud infrastructure, and wake up at 3 AM when things break.

A day in the life (9 AM to 6 PM)

Tools they use

• Containers: Docker, Kubernetes (the most important skill in modern DevOps)
• Cloud platforms: AWS (EC2, S3, Lambda, EKS), GCP, Azure
• Infrastructure as Code: Terraform, Pulumi, CloudFormation
• CI/CD: GitHub Actions, Jenkins, GitLab CI, ArgoCD
• Monitoring: Grafana, Prometheus, Datadog, PagerDuty
• Scripting: Bash, Python, Go
• Security: Vault (secrets management), Trivy (container scanning)

Skills required

• Technical: Linux administration, networking (TCP/IP, DNS, load balancers), Docker and Kubernetes, at least one cloud platform deeply, CI/CD pipeline design, scripting (Bash + Python), understanding of security principles
• Soft skills: Calm under pressure (you will get paged during outages), excellent documentation skills, systematic problem-solving, communication during incidents ("War room" coordination)

Salary range in India (per annum)

How AI is changing this role

AI is helping DevOps engineers by providing intelligent alerting (predicting incidents before they happen), auto-remediation (automatically fixing known issues), and AI-powered log analysis (finding the needle in a haystack of millions of log lines). Tools like Kubernetes copilots can generate YAML configurations from natural language. But infrastructure is fundamentally about reliability and security — areas where you cannot afford AI hallucinations. The human remains critical for architectural decisions, security posture, and incident response.

#6. Product Manager

What they do in simple terms

A day in the life (9 AM to 6 PM)

Tools they use

• Project management: Jira, Linear, Asana, Plane.so
• Analytics: Amplitude, Mixpanel, PostHog, Google Analytics
• Documentation: Notion, Confluence, Google Docs
• Design collaboration: Figma (for reviewing designs)
• Communication: Slack, Zoom, Loom (async video updates)
• Roadmapping: Productboard, Aha!, Notion
• User research: Hotjar (heatmaps), UserTesting, Typeform (surveys)

Skills required

• Technical: You do not need to code, but you need to understand how software is built (APIs, databases, trade-offs between speed and quality). Enough technical literacy to have informed conversations with engineers
• Analytical: SQL (basic to intermediate), understanding of metrics (DAU, MAU, retention, LTV, CAC), A/B testing methodology
• Soft skills: Communication (you are the glue between engineering, design, sales, and leadership), prioritization (saying "no" to 90% of ideas), empathy (deeply understanding user pain), storytelling (getting buy-in for your vision)

Salary range in India (per annum)

How AI is changing this role

AI is becoming the PM's superpower. PMs now use AI to summarize user feedback (reading 10,000 reviews in seconds), generate PRDs from rough notes, analyze metrics using natural language queries, and even prototype features with AI coding tools. The role is shifting from "spend 60% of your time on documentation" to "spend 60% of your time talking to users and thinking strategically, while AI handles the paperwork."

#7. QA / Test Engineer

What they do in simple terms

QA (Quality Assurance) engineers make sure the software actually works before it reaches users. They find bugs, write automated tests, and prevent broken features from shipping. Think of them as the last line of defense between buggy code and your users. Every time you use an app and it does NOT crash — thank a QA engineer.

A day in the life (9 AM to 6 PM)

Tools they use

• Test automation: Playwright (modern favorite), Cypress, Selenium
• API testing: Postman, Bruno, REST Client
• Bug tracking: Jira, Linear, GitHub Issues
• Performance testing: k6, JMeter, Locust
• Mobile testing: Appium, BrowserStack, Sauce Labs
• Languages: JavaScript/TypeScript (for test scripts), Python
• CI integration: GitHub Actions (running tests on every commit)

Skills required

• Technical: At least one programming language (JavaScript or Python), test automation frameworks, API testing, understanding of CI/CD pipelines, basic SQL (for verifying data in the database)
• Soft skills: Extreme attention to detail, adversarial thinking ("How can I break this?"), clear communication (writing bug reports that developers can actually reproduce), patience, systematic approach

Salary range in India (per annum)

How AI is changing this role

AI is transforming QA from primarily manual testing to intelligent test automation. AI tools can now auto-generate test cases from requirement documents, identify which tests to run based on code changes (intelligent test selection), and even perform visual regression testing by comparing screenshots. Self-healing tests (tests that automatically update when the UI changes) are becoming reality. The role is evolving from "write and run tests" to "design test strategies and supervise AI-powered testing systems."

#8. UI/UX Designer

What they do in simple terms

UI (User Interface) designers make the product look good. UX (User Experience) designers make the product feel good — easy to use, intuitive, and delightful. In practice, most designers do both. They decide where every button goes, what color it should be, what happens when you tap it, and how the entire flow feels from start to finish. If a software engineer builds a house, the designer is the architect who plans the floor layout and picks the paint colors.

A day in the life (9 AM to 6 PM)

Tools they use

• Design: Figma (industry standard), Sketch, Adobe XD
• Prototyping: Figma, Principle, ProtoPie
• Collaboration: Figma (comments), Slack, Loom
• User research: Maze, UserTesting, Hotjar (heatmaps and recordings)
• Whiteboarding: Miro, FigJam
• Design systems: Storybook (component library), Figma component libraries
• AI tools: Midjourney/DALL-E (for concept art), Galileo AI, Uizard

Skills required

• Technical: Figma proficiency, understanding of design systems, basic knowledge of HTML/CSS (to design within technical constraints), responsive design principles, accessibility (WCAG standards)
• Creative: Visual design (typography, color theory, layout), interaction design (micro-animations, transitions), information architecture
• Soft skills: Empathy (the whole job is understanding how humans think and feel), ability to take criticism on designs, communication (defending design decisions with data), user research skills

Salary range in India (per annum)

How AI is changing this role

AI design tools can now generate UI layouts from text prompts, create variations of designs instantly, and even convert wireframes to code. Tools like Galileo AI and Uizard can produce initial design mockups in seconds. But design is fundamentally about understanding human psychology, business goals, and crafting experiences that feel right, not just look right. AI accelerates the execution but cannot replace the thinking. The role is shifting from "spend 3 hours creating 5 layout variations" to "use AI to generate 50 variations in 5 minutes, then pick and refine the best one."

#Career Progression

Now that you know the roles, let us talk about how careers grow in tech. There are two main ladders you can climb:

#The Individual Contributor (IC) Track

This is for people who love doing the work — writing code, designing systems, analyzing data. You get promoted by becoming more skilled and taking on harder problems:

#The Management Track

This is for people who love leading teams and growing people:

#Which Role Is Right for You?

There is no wrong answer. And here is a secret: most people switch roles at least once in their career. Many great PMs were former engineers. Many ML engineers started as data scientists. Many DevOps engineers started as backend developers.

Here is a quick guide based on your personality:

#The Title Overlap Problem (And How to Pick the Right One)

These four titles confuse everyone:

• Data Scientist. Answers business questions with data. Builds models in notebooks. Presents findings. Lives in Jupyter + SQL + Pandas.
• ML Engineer. Takes a data scientist's notebook and turns it into a service handling 10M requests per day. Lives in PyTorch + Docker + Kubernetes.
• AI Engineer / LLM Engineer. A newer title (2023+). Builds applications using foundation models (Claude, GPT, Gemini). Lives in LangChain + vector databases + prompt engineering. Less ML theory, more API integration.
• Research Scientist. Invents new model architectures, publishes papers. Usually requires a PhD. Lives at Anthropic, DeepMind, FAIR. Highest salary ceiling, hardest to enter.

Same person, same skills, four very different titles. Here's how to pick:

#The Hidden Role: AI Product Manager

• Non-determinism: the same input can give different outputs. Traditional PMs aren't trained for this.
• Evaluation: how do you A/B test "the model writes better summaries"? You need eval frameworks, not just funnel metrics.
• Hallucinations: when do you trust the model? AI PMs design the guardrails.
• Cost economics: every call to an LLM costs money. PMs must understand unit economics in a way traditional PMs do not.

If you're a current PM, learning the AI side is the highest-ROI move you can make in 2026.

#What Each Role's First 90 Days Actually Looks Like

Recruiters never tell you this. Here's the truth.

• Week 1: get your machine set up. This takes longer than you'd think; expect 2-3 days.
• Week 2: read existing code, ask a senior to walk you through the architecture. Don't write production code yet.
• Week 3-4: pick up a "starter ticket" — a small bug or minor feature. Your first PR.
• Month 2: own a small feature end-to-end. Get used to code review feedback (it's brutal, but it's mentorship, not personal attack).
• Month 3: take part in on-call rotation (in some teams).

• Week 1-2: understand the data. Where it lives, how it's collected, what's clean, what's broken. This is 80% of the job.
• Week 3-4: replicate an existing dashboard or analysis. Validate you can produce the same numbers as the previous person.
• Month 2: design and run your first A/B test, or build your first model. Both intimidating; both done in iteration.
• Month 3: present findings to stakeholders. The hardest skill: making a complex analysis land with a non-technical executive in 2 minutes.

• Week 1: read code, understand the current training pipeline and serving infrastructure.
• Week 2-4: optimize something small — reduce inference latency by 10%, fix a memory leak, improve a CI test.
• Month 2: own a model in production. Watch it 24/7 for a week — drift, errors, edge cases.
• Month 3: ship a new model version with measurable improvements.

• Week 1-2: 30+ user interviews. Yes, really. You can't PM what you haven't talked to users about.
• Week 3-4: shadow the engineering team. Sit in standups, design reviews, sprint planning.
• Month 2: own a small feature spec. Get it past design review and into a sprint.
• Month 3: own a roadmap item that lands in front of the CEO.

• Week 1: get on-call shadow rotation. Watch the senior on-call handle real incidents.
• Week 2-4: own one piece of infrastructure (a CI/CD pipeline, a monitoring dashboard, a Kubernetes namespace).
• Month 2: take your first primary on-call shift. Yes, you'll get paged at 3 AM. Yes, you'll survive.
• Month 3: lead a post-mortem after an incident. The post-mortem (not the incident) is where careers are made.

#Skills That Matter in Every Role

No matter which role you choose, certain skills will make you successful everywhere in tech:

#Key Takeaways

• Building software is a team sport with distinct roles — developers build it, designers make it usable, PMs decide what to build, QA makes sure it works, DevOps keeps it running, and data professionals make it smart
• Each role has a clear day-to-day rhythm — from standups and Jira tickets to Figma mockups and Grafana dashboards. No two roles look the same on a daily basis
• Career growth follows two tracks — the IC (Individual Contributor) track for people who love doing the work, and the Management track for people who love leading teams. Both can reach senior levels
• T-shaped skills win. Go deep in one area, then broaden. The most valuable professionals understand their specialty deeply AND can collaborate across disciplines
• AI is transforming every role, not replacing them. It is making routine tasks faster and shifting focus to higher-level thinking, strategy, and creativity. Learning to work with AI tools is now a core skill for every tech professional
• Communication and continuous learning are universal — no matter your role, the ability to explain complex ideas simply and the habit of always learning new things will set you apart

#See Also

• The Software Industry — understand the business context these roles operate in
• How Software Gets Built — see how these roles collaborate through the software development lifecycle
• AI Solving Real Problems — discover the real-world AI applications these roles are building

Each role you read about above maps to a learning path on this platform. Use these forward-links to jump straight to the technical foundations for the seat you want.