Aishwarya Srinivasan

AI@Fireworks AI | Global Speaker(100+ talks)| EB1-A Recipient| 570k+ Followers| AI Engineer| GenAI/LLM Inference| LinkedIn Top Voice| Author-What's Your Worth?| Startup AI Advisor| Angel Investor| Ex-Google,Microsoft,IBM

𝗙𝗼𝗿 𝗽𝗮𝗿𝘁𝗻𝗲𝗿𝘀𝗵𝗶𝗽 𝗶𝗻𝗾𝘂𝗶𝗿𝗶𝗲𝘀, 𝗰𝗼𝗻𝘁𝗮𝗰𝘁 𝗺𝘆 𝘁𝗲𝗮𝗺 𝗮𝘁 💌 partnerships@illuminate-ai.org

I write about:
- AI engineering
- Applied machine learning
- Generative AI Applications
- LLM/ LLMOPs (Training, post-training, inferencing)
- Fundamentals of Data science/ ML/ AI
- ML roles interview tips
- Learning roadmaps (beginner to advanced)
- Importance of personal branding for career growth

**All the posts reflect my own views and do not represent my employer.**

AI Advisor || Responsible AI Advocate || LinkedIn Top Voice - Data & AI  || Top 10 AI Influencer || EB1-A Receipt


Bio: 
Aishwarya currently leads the Developer Relations - Growth at Fireworks AI. She was previously at Microsoft for Startups as a Senior AI Advisor to help Y Combinator startups build machine learning solutions, leveraging core Microsoft/ OpenAI products. Prior to this, Aishwarya was working as a Data Scientist in Google Cloud and before that an AI & ML Innovation Leader at IBM Data & AI, where she was working cross-functionally with the product team, data science team and sales to research AI use-cases for clients by conducting discovery workshops and building assets to showcase the business value of the technology. She holds a post-graduate in Data Science from Columbia University. 

Aishwarya has been awarded Trailblazer of the Year by Women in AI in 2022 and Women of Influence by Business Journal in 2022. She was awarded EB1A - extraordinary ability visa for her contributions in the AI field.

She is an advocate for open-source technologies, and was an open source Developer Advocate for Deepchecks and Lightning AI, and a contributor to Scikit Learn. 


She holds a Patent Award (2018) for developing a Reinforcement Learning model for Machine Trading.

She has over 500,000+ follower base on LinkedIn and actively organizes events and conferences to inspire budding data scientists. She has been spotlighted as a LinkedIn Top Voice 2020 for Data Science and AI, which features Top 10 Machine Learning influencers across the world. 

She is an ardent reader and has contributed to the scholastic community. To spread her knowledge in the space of data science, and to inspire budding Data Scientists, she actively writes blogs related to machine learning on LinkedIn and Instagram: www.instagram.com/the.datascience.gal

Besides being a data junkie, she is a fitness fanatic who is into martial arts (Krav Maga) and yoga.

Senior AI Advisor

As an AI engineer, LLM Twin is an important architecture to understand.

An LLM Twin refers to a system where a language model is designed to represent the knowledge, writing patterns, and decision logic of a specific person, team, or organization. The goal is consistency and reliability, not novelty.

At its core, an LLM Twin is built around how information flows. Think of it as 4 steps:

1️⃣ First, content is collected from real sources: blogs, internal documents, posts, code repositories, or knowledge bases. This data reflects how the person or organization actually thinks and communicates.

2️⃣ Next, the data is structured for two purposes.
One path prepares instruction-style examples that help the model learn how to respond.
Another path prepares retrieval data so the system can pull relevant context at inference time. This ensures responses stay grounded in real material.

3️⃣ Then comes training and evaluation. Models are fine-tuned where appropriate, tested against clear criteria, and versioned before deployment. This step looks very similar to traditional ML workflows, just adapted for language models.

4️⃣ Finally, at inference time, user requests are combined with retrieved context and passed through the deployed model. Monitoring is critical here: quality, latency, and cost all need to be observed continuously.

Where is this used in practice?

✦ Personal or creator assistants that help scale writing and communication
✦ Company-wide assistants that maintain a consistent product or brand voice
✦ Internal tools that answer questions based on code, docs, or prior decisions
✦ Support systems that reflect how experienced engineers respond to issues

Why should AI Engineers understand this?
This architecture reflects how GenAI systems are actually built and maintained. It forces you to think beyond prompts and focus on data quality, retrieval design, evaluation, and long-term system behavior.

My 2 cents 🤌
This is a GREAT topic to build a portfolio project around!! 

Credit: LLM Engineer’s Handbook by Paul Iusztin  and Maxime Labonne. I really like how this book breaks down AI engineering clearly and goes deep into different GenAI system architectures without hand-waving.

Over the past few months, Arvind and I've delivered seven deep technical workshops across agentic AI, RAG, context engineering, AI evals, MCP, vibe coding, and more.

One theme kept coming up: you want something more structured. Not just standalone sessions, but a clear end-to-end roadmap from A to Z.

So that’s what we’re building.

A structured, comprehensive course for:
- Hands-on builders: software, AI, and ML engineers
- AI product managers
- Tech leaders and CXOs looking to upskill meaningfully

Before we finalize it, I’d love your input. I’ve created a short survey to understand where you are, what you want to learn, and your career goals.

It takes under 10 minutes.

As a thank you, you’ll receive an additional 10% discount when we launch the course soon 🫶

Survey: https://lnkd.in/gQYeBCRP

No alternative text description for this image

Here’s my honest pattern with almost every AI tool I try.

I end up using a lot of tools, usually early access. After repeating this cycle enough times, I realized my reactions are almost predictable.

👉First hour
There’s real excitement.
I’m clicking around, testing odd prompts, trying things that used to fail. No strategy yet, just my curiosity and momentum.

👉Next few hours
I start comparing.
Where would this actually fit in my work?
What would I stop using if I kept this?
Is this clearly better, or just new?

👉Later that day
I experiment without guidance.
I skip the docs and examples on purpose. I try incomplete ideas, messy workflows, prompts I would never put in a demo. This tells me more than any tutorial ever could.

👉Day two
Then I look at the examples the team shared.
They usually work smoothly. They’re polished. They show the tool at its best, which is exactly what they’re meant to do.

👉After a few days
This is where the real understanding kicks in.
I start tweaking those examples. Changing assumptions. Using it in ways that feel realistic, not ideal. That’s when the boundaries show up. Not frustration. Just clarity.

Here’s the takeaway I’ve learned the hard way:
If you haven’t noticed limitations yet, you probably haven’t pushed the tool very far.

And honestly, if I use something consistently for three days and still can’t find a meaningful flaw, that’s rare. That earns real respect.
I haven’t experienced that yet.

Curious how others see this.
Are there tools you’ve used deeply where the limits still haven’t shown up?

Just a couple of weeks ago, Arvind and I hosted an in-person AI meetup with The Hub Bengaluru.

Over 300 people showed up in person.

Every single one of them was either already working in AI or actively trying to break into the space. The energy in the room was unreal. It genuinely felt like a room full of builders, practitioners, and people who are curious enough to go deep.

During the event, we rolled out a small challenge. We asked attendees to share a recap of what they learned, and we said we would pick one winner.

Really excited to share that Suraj V is that lucky winner 🎉
Suraj gets free access to all the The Gen Academy workshops we have hosted so far.

Huge congratulations, Suraj V!! 

Building The Gen Academy has always come from a very real observation that Arvind and I see every single day in our work. The adoption of generative AI and LLMs is moving incredibly fast, but the depth of AI engineering skills needed to build reliable systems is not keeping up.

There is a very real skill gap in AI engineering right now! There are so many curious souls who want to become AI engineers- but they aren't able to get those opportunities; and there are so many companies out there who  want to hire, but aren't finding the right talent. 

Our mission is to bridge that skill-gap!

As people who are deeply involved in this space, we felt a responsibility to help bridge that gap. Not just for people who are already experienced, but also for entry-level folks who want to build strong foundations the right way.

That is why our workshops are intentionally designed to be both intuitive and practical. We focus on theory that actually helps you reason about systems, and we pair that with hands-on demos where you build real things using modern toolkits and frameworks.

So far, we have hosted 6 workshops, and the response has been incredibly encouraging. We have trained 1500+ people already ❤️ 

Our next workshop is coming up on February 15th, and it will be focused on AI evaluations (link in comments)

Do follow The Gen Academy to stay updated on all our upcoming workshops.

Six months ago, Arvind and I started The Gen Academy with one simple goal- to create workshops that are deeply-technical, practical, cuts through the ton of noise out there, and that provides people clarity on building productive-grade AI systems.

So far we have trained 2100+ people. We’ve hosted 7 workshops, and consistently we’ve had 300–400 builders join us live.

The audience has been incredible.
- Software engineers moving into AI.
- AI engineers building LLM systems in production.
- Product leads thinking about reliability and evaluation.
- Directors and VPs from top tech and Fortune 500 companies who want to truly understand what’s under the hood.
- Even people from non-tech background who wanted to strengthen their technical fundamentals 

Recently, we hosted a workshop on AI Evaluations.

And this one felt especially important.

Because evaluating non-deterministic generative systems is fundamentally different from traditional ML evaluation.

We covered:

✦ How to evaluate non-deterministic generative AI systems
✦ How to think about benchmarks and what they actually tell you
✦ How to design your own evaluation dataset
✦ How to choose the right metrics for qualitative and system-level evaluation
✦ How to combine human evals, code-based evals, and LLM-as-a-judge
✦ A hands-on walkthrough so this isn’t just theory

If you’re building LLM applications, RAG pipelines, or agentic systems, evaluation is not optional. It is the difference between a demo and a reliable product.

If you missed the live session, we’ve shared the recording here: https://lnkd.in/gzMdbfWH

We’ll continue building these workshops for engineers who want to go beyond experimentation and into production.

More coming soon, so do follow us & The Gen Academy to get updates on our next workshops.

5 days to go! 
Arvind and I are super excited to be hosting an AI evals hands-on workshop on February 15.

It’s a 90-minute session where we’ll cover the fundamentals of AI evaluations and then actually do it together. You’ll walk away having built and reasoned through real evals yourself. 

If you’re aspiring to be an AI engineer or planning to upskill for AI roles in 2026, understanding how to evaluate LLM applications is critical.

Building an LLM app is often the easy part. Knowing whether it truly works in production is where most teams struggle.

LLM evaluation is not just about correctness anymore. You are judging usefulness, safety, faithfulness to sources, consistency across runs, cost, latency, and real user outcomes across prompts, RAG pipelines, tools, and agentic workflows.

Because this is hard, many teams fall back to vibe-evals. If a few outputs look good, they ship. That approach breaks quickly when models change, prompts regress, retrieval fails, or user behavior shifts. Without evals, problems surface only after users complain.

Why learning evals matters:
✦ Evals turn LLM development from guesswork into engineering
✦ They help catch regressions as models, prompts, or tools evolve
✦ They are essential for scaling RAG systems and agentic workflows
✦ In 2026, strong teams use hybrid evals combining automated metrics, LLM-as-a-judge, and targeted human review

Evals are no longer optional. They are a core AI skill.

In this workshop, Arvind and I will walk through how AI evals are done in real systems, with hands-on exercises so you build intuition.

This is designed for AI engineers and tech leads building systems, and even business leaders who want intuition for what “good” really means in production. Even if you are a beginner, don't worry, we will give you the foundations for you to understand everything comprehensively, and enough resources that you can review at your own pace.

If you want to level up your AI skills for 2026, register here:
https://lnkd.in/dQSR7yhU

Evaluation Resources

Fine-tuning is going to be one of the biggest focus areas for AI engineering teams this year.

We’re past the stage where calling an API is enough. The teams creating real leverage are the ones adapting models to their own data, workflows, and edge cases. Out-of-the-box models are powerful, but they are generic. Fine-tuning is where enterprises unlock meaningful efficiency gains and build real differentiation.

If you want to upskill in AI engineering, this is a topic you cannot skip.
Arvind and I are hosting a deep, hands-on workshop on Fine-Tuning LLMs.

In 90 minutes, you’ll learn:
✦ When fine-tuning makes sense and when it does not
✦ How SFT, RLHF, and DPO fit into real-world pipelines
✦ An end-to-end, code-based demo from raw data to a specialized model
✦ How to evaluate true performance improvements and avoid production pitfalls

This session is designed for software engineers, AI engineers, and data scientists, and it is equally valuable for product managers, solutions architects, tech leads, and executives working closely with model ecosystems.

If you want to move from using LLMs to actually optimizing them, this workshop will give you a practical framework to do it: https://lnkd.in/g-5gHrsY

In 2026, AI isn’t judged by a wow factor anymore.
It’s judged by whether it actually improves your workflows.

One of the most common questions I get from founders and teams I advise is how to automate go-to-market and sales properly. Real GTM automation needs deep ICP research, clear definitions, personalized messaging, and credible sources. This isn’t a one-prompt problem.

Normally, building a solid GTM or sales report would take me several hours, even with existing AI tools helping with research.

I recently got early access to Airtable’s new Superagent, and what impressed me was the approach. It didn’t treat my request as a single task. It broke it into ~16 steps, ran multiple agents in parallel, did deep research per subtask, cited sources, and stitched everything together into one structured output called a Super Report.

I used it to build a technical, informational report on AI for GTM/Sales in minutes. No fluff. No hallucinations. Just deeply researched content I could actually use with business leaders.

If your work involves building reports, decks, or MVP websites that need accuracy and depth, this feels less like “AI that makes things pretty” and more like AI that does real work.

Do check it out here: https://lnkd.in/gDkfSSG2

PS: You can get 2 months free for @Superagent, using code: AISH2FREE

#SuperagentPartner, #ad, #SuperagentbyAirtable

𝐖𝐢𝐭𝐡 𝟐𝟐+ years of industry experience, I help businesses architect, optimize, and secure their cloud infrastructure—ensuring scalability, automation, and cost-efficiency at every step.

As Director of Cloud Engineering at OSTTRA, I lead global teams in Cloud, DevOps, and DevSecOps, driving innovation and transforming IT landscapes for enterprise-scale success.
What I Bring to the Table:

✔ 𝐂𝐥𝐨𝐮𝐝 𝐒𝐭𝐫𝐚𝐭𝐞𝐠𝐲 & 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞 – Crafting resilient, high-performing cloud ecosystems across AWS, Azure, and GCP.

✔ 𝐃𝐞𝐯𝐎𝐩𝐬 & 𝐃𝐞𝐯𝐒𝐞𝐜𝐎𝐩𝐬 𝐌𝐚𝐬𝐭𝐞𝐫𝐲 – Automating workflows, enforcing security, and streamlining CI/CD with Kubernetes, Helm, Terraform & more.

✔ 𝐓𝐞𝐜𝐡𝐧𝐨𝐥𝐨𝐠𝐲 𝐋𝐞𝐚𝐝𝐞𝐫𝐬𝐡𝐢𝐩 – Scaling high-impact engineering teams, fostering innovation, and ensuring delivery excellence.

✔ 𝐄𝐧𝐭𝐞𝐫𝐩𝐫𝐢𝐬𝐞 𝐂𝐥𝐨𝐮𝐝 𝐌𝐢𝐠𝐫𝐚𝐭𝐢𝐨𝐧𝐬 – Successfully leading multi-million-dollar cloud transformations with agility and precision.

✔ 𝐂𝐱𝐎-𝐋𝐞𝐯𝐞𝐥 𝐄𝐧𝐠𝐚𝐠𝐞𝐦𝐞𝐧𝐭 – Aligning technology with business goals, driving ROI, and shaping digital-first strategies.

Beyond my role, I am a DZone contributor, mentor, and passionate advocate for continuous learning and knowledge sharing.

Let’s connect if you’re looking to discuss cloud transformation, automation, or IT strategy—or if you just love talking tech!

Jaswindder Kummar

𝐓𝐡𝐞 𝐃𝐞𝐯𝐎𝐩𝐬 𝐥𝐞𝐚𝐫𝐧𝐢𝐧𝐠 𝐩𝐚𝐭𝐡 𝐄𝐯𝐞𝐫𝐲𝐨𝐧𝐞 𝐚𝐬𝐤𝐬 𝐚𝐛𝐨𝐮𝐭. 
Here's the Roadmap that actually works in Production.

After mentoring 100+ engineers, 
I've seen too many get lost in tutorial hell. 
This landscape shows the progression that builds production-ready skills.

𝐌𝐲 𝐫𝐞𝐜𝐨𝐦𝐦𝐞𝐧𝐝𝐞𝐝 𝐥𝐞𝐚𝐫𝐧𝐢𝐧𝐠 𝐬𝐞𝐪𝐮𝐞𝐧𝐜𝐞:

𝟏. 𝐅𝐨𝐮𝐧𝐝𝐚𝐭𝐢𝐨𝐧 (𝐌𝐨𝐧𝐭𝐡𝐬 𝟏-𝟑):
• One language: Python, Go, or Ruby—pick one, master fundamentals
• Linux OS concepts: processes, memory, file systems
• Terminal mastery: bash scripting, text tools (awk, sed, grep)
• Ubuntu or CentOS—stick with one until you can troubleshoot blindfolded

𝟐. 𝐈𝐧𝐟𝐫𝐚𝐬𝐭𝐫𝐮𝐜𝐭𝐮𝐫𝐞 𝐁𝐚𝐬𝐢𝐜𝐬 (𝐌𝐨𝐧𝐭𝐡𝐬 𝟒-𝟔):
• Networking: HTTP/HTTPS, SSH, DNS—you'll debug these weekly
• Web servers: Nginx or Apache, reverse proxy patterns
• Security: SSL/TLS, firewalls, port forwarding

𝟑. 𝐈𝐚𝐂 & 𝐂𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫𝐬 (𝐌𝐨𝐧𝐭𝐡𝐬 𝟕-𝟗):
• Docker fundamentals before Kubernetes
• Ansible or Puppet for config management
• Terraform for infrastructure provisioning
• Kubernetes only after mastering Docker

𝟒. 𝐂𝐈/𝐂𝐃 (𝐌𝐨𝐧𝐭𝐡𝐬 𝟏𝟎-𝟏𝟐):
• GitLab or GitHub Actions
• Jenkins—legacy but everywhere
• Build automation and testing pipelines

𝟓. 𝐌𝐨𝐧𝐢𝐭𝐨𝐫𝐢𝐧𝐠 (𝐎𝐧𝐠𝐨𝐢𝐧𝐠):
• ELK or Splunk for logs
• Prometheus + Grafana for metrics
• APM tools: Jaeger, New Relic

Critical insights:

DO:
• Build real projects, not just tutorials
• Automate everything you do twice
• Break things in safe environments
• Get on-call experience

DON'T:
• Skip fundamentals to jump to K8s
• Collect certs without hands-on work
• Try learning everything at once

Truth: 
Senior DevOps isn't knowing every tool. 
It's debugging production at 3 AM and building systems that scale without you.

Tools change every 18 months. Principles don't.
Where are you on this journey?

♻️ Repost if you found it valuable
➕ Follow Jaswindder for more insights on Cloud Strategy, DevOps, and AI-led Engineering.

#DevOps #CloudEngineering #SRE

𝐇𝐨𝐰 𝐀𝐈 𝐢𝐬 𝐂𝐨𝐦𝐩𝐥𝐞𝐭𝐞𝐥𝐲 𝐑𝐞𝐰𝐫𝐢𝐭𝐢𝐧𝐠 𝐭𝐡𝐞 𝐃𝐞𝐯𝐎𝐩𝐬 𝐏𝐥𝐚𝐲𝐛𝐨𝐨𝐤

AI is changing the way we think about DevOps. 
With AI-driven DevOps, you’re looking at a new world where the delivery lifecycle is largely automated, with anticipatory action and self-healing systems.

𝐖𝐡𝐚𝐭 𝐈𝐬 𝐀𝐈-𝐃𝐫𝐢𝐯𝐞𝐧 𝐃𝐞𝐯𝐎𝐩𝐬?
It’s the integration of AI across every phase of the DevOps lifecycle, from failure anticipation to self-healing pipelines. 
In short, it’s DevOps on autopilot.

𝐂𝐨𝐫𝐞 𝐀𝐈 𝐂𝐨𝐧𝐜𝐞𝐩𝐭𝐬 𝐘𝐨𝐮 𝐍𝐞𝐞𝐝 𝐭𝐨 𝐊𝐧𝐨𝐰:
1. LLMs (Large Language Models): These AI models provide powerful code assistance and automation for DevOps tasks.
2. RAG (Retrieval-Augmented Generation): Real-time data retrieval to improve accuracy in responses.
3. AIOps: Using AI for anomaly detection and automated problem resolution.
4. MLOps: Managing the entire ML lifecycle, from model training to deployment.
5. Prompt Engineering: Crafting inputs to control AI outputs with precision.
6. Vector Databases: Storing embeddings for semantic search to boost AI's efficiency.

𝐓𝐡𝐞 𝐀𝐧𝐚𝐭𝐨𝐦𝐲 𝐨𝐟 𝐚𝐧 𝐀𝐈-𝐃𝐫𝐢𝐯𝐞𝐧 𝐖𝐨𝐫𝐤𝐟𝐥𝐨𝐰:
1. Define the scope of your work.
2. Choose or train the model to meet your needs.
3. Integrate the AI system via APIs or agents for smoother processes.
4. Automate CI/CD and ensure continuous monitoring.
5. Continuously learn from logs to improve the process.
6. Optimize and retrain to stay ahead of issues.

𝐃𝐨'𝐬 & 𝐃𝐨𝐧'𝐭𝐬 𝐢𝐧 𝐀𝐈-𝐃𝐫𝐢𝐯𝐞𝐧 𝐃𝐞𝐯𝐎𝐩𝐬:
• Do: Leverage AI for proactive solutions rather than reactive monitoring.
• Don’t: Trust AI blindly. Always validate the results.
• Do: Keep human oversight to ensure AI is working as expected.
• Don’t: Combine multiple AI tools without a proper integration plan.

𝐌𝐞𝐞𝐭 𝐘𝐨𝐮𝐫 𝐍𝐞𝐰 𝐃𝐞𝐯𝐎𝐩𝐬 𝐓𝐞𝐚𝐦𝐦𝐚𝐭𝐞𝐬: 𝐀𝐈 𝐀𝐠𝐞𝐧𝐭𝐬
These AI-powered tools are here to support your DevOps efforts:
1. Code Review Bots: Detect vulnerabilities and performance bottlenecks (SonarQube, Snyk).
2. Test Generation Agents: Automatically generate tests from new code (Mabl, EvoSuite).
3. Pipeline Optimizers: Resolve build failures before human intervention (Harness, CircleCI).
4. Auto-Deployment Bots: Handle redeployments and real-time monitoring (Kubernetes, Argo).
5. Security Agents: Detect exposed secrets in commits (Gryp, Trivy, Snyk).

These agents run 24/7, freeing up your team to focus on innovation, not firefighting.

♻️ Repost if you found it valuable
➕ Follow Jaswindder for more insights on Cloud Strategy, DevOps, and AI-led Engineering.

#GenAI #DevOps #AgenticAI

taplio

The Battle

Aishwarya Srinivasan

Jaswindder Kummar

Followers

Posts

Engagements

Likes

Performance ScoreAishwarya Srinivasan's LinkedIn Performance

Performance ScoreJaswindder Kummar's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Aishwarya Srinivasan

Jaswindder Kummar

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Aishwarya Srinivasan's LinkedIn Performance

Performance ScoreJaswindder Kummar's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreAishwarya Srinivasan's LinkedIn Performance