class YusraBatool:
def __init__(self):
self.role = "ML Engineer"
self.university = "CS @ Sukkur IBA University '28"
self.location = "Pakistan"
self.focus = [
"Multi-Agent AI Systems",
"Medical Imaging and Explainable AI",
"Cloud-Native ML Pipelines",
"Responsible AI Design"
]
self.current_work = {
"building" : "Agentic AI systems with LangGraph and Google ADK",
"deploying" : "Production ML on Google Cloud Run",
"researching" : "Knowledge graphs for organizational cognition",
"exploring" : "Explainable medical imaging with Grad-CAM"
}
self.philosophy = "Ship fast, ship responsibly, ship things that matter."
def daily_routine(self):
return ["coffee", "research", "build", "deploy", "repeat"]I started with data analytics, moved into machine learning, and found my place building multi-agent AI systems that solve real problems for real people. I care about the full loop — from research to cloud deployment to responsible design. Every project I build goes through the same filter: does it ship, does it work, and does it do right by its users.
Right now I am deep into agentic AI architectures, medical imaging pipelines, and knowledge graph systems. I build with Python, deploy on Google Cloud, and think carefully about guardrails, PII redaction, and human-in-the-loop design in everything I put into production.
I pick tools based on what the problem needs, not what is trending. PyTorch for anything that needs custom model control. Google ADK and LangGraph when orchestration complexity demands a graph-based agent framework. FastAPI when I need a backend that ships today. Cloud Run when I want zero-ops deployment. Neo4j when relationships matter more than rows.
|
Building graph-based memory and multi-agent risk surfacing for teams that need to think together at scale. |
I believe the best AI engineers are not just model builders — they are system designers. An agent that hallucinates costs more than one that says "I don't know." A pipeline without guardrails is a liability, not a feature. I think about failure modes before I think about demos.
I do not build projects to fill a portfolio. I build them because I see a gap — a workflow that could be automated, a diagnosis that should be explainable, a user group that technology forgot about. The project list is a side effect of caring about the right problems.
|
Jun 2025 - Present |
May 30 - Jun 22 |
Jan 3 - Feb 18 |
88% uptime |
avg daily |
I do not chase credentials — but when programs align with what I am already building, I show up and deliver. Here is what that looks like:
{
"certifications": [
{
"name": "Generative AI Leader Professional Certificate",
"issuer": "Google Cloud",
"status": "verified"
},
{
"name": "Google Data Analytics Professional Certificate",
"issuer": "Google",
"status": "verified"
},
{
"name": "Data Analytics Certificate",
"issuer": "IBM SkillsBuild",
"status": "verified"
},
{
"name": "Excel Essentials for Data Analytics",
"issuer": "IBM",
"status": "verified"
},
{
"name": "McKinsey Forward Program",
"issuer": "McKinsey and Company",
"status": "verified"
},
{
"name": "SQL Intermediate",
"issuer": "HackerRank",
"status": "verified"
},
{
"name": "Java Basic",
"issuer": "HackerRank",
"status": "verified"
}
]
}Additional completed work: Deloitte Data Analytics Job Simulation, AWS Aurora MySQL Basics, Microsoft AI Skills Fest, Google Arcade Facilitator Program.
[2026-06-22] Currently exploring:
- Advanced multi-agent memory architectures
- Graph neural networks for knowledge representation
- Production observability for ML pipelines
- Android accessibility services for inclusive AI
- Responsible AI evaluation frameworks
[NEXT] On the radar:
- MLOps pipeline automation with Vertex AI
- Federated learning for privacy-preserving medical AI
- Building evaluation harnesses for agentic systems
- Contributing to open-source AI safety tooling
I treat learning the same way I treat engineering — systematically, with clear intent, and always tied to something I am building. Courses are inputs. Shipped projects are outputs. The ratio matters.
yusra@dev ~
-----------
OS : Builder, not just a learner
Uptime : Since 2024, shipping consistently
Shell : Python, Java, Kotlin, C++, SQL, R
Terminal : VS Code + Google Cloud Shell + Android Studio
Packages : 9 projects shipped, 3 live in production
Resolution: Build AI that is useful, explainable, and safe

