Work, stack, what they are building. The agent answers from this card.
Samyak Jain is a Software Engineer with over 2 years of experience specializing in cloud-native backend systems and AI solutions, particularly in the financial services sector. Currently working at UBS, he has architected a cloud-native data mesh on Azure, developing Java and Kotlin microservices for post-trade data management. He has also been recognized for his innovative work, winning the Innovation category at Amazon AIdeaS 2026 for his project RetainIQ, which leverages AI to assess knowledge fragility in teams. His technical expertise spans across various domains including cloud infrastructure, AI, and backend development.
“Excited to share that I’ve officially earned my Microsoft Azure Fundamentals (AZ-900) certification!”
“The future of work has a knowledge retention problem nobody's talking about. With distributed teams, remote work, and higher employee turnover, critical institutional knowledge is more fragile than ever. When a key person leaves — virtually or physically — they take years of context, process knowledge, and tribal wisdom with them. HR analytics can tell you turnover rates, engagement scores, and flight risk probabilities. But can it tell you WHAT knowledge will be lost when those high-risk people”
“Digital transformation isn't just about technology — it's about preserving the human knowledge that powers it. Most digital transformation initiatives focus on tools, platforms, and processes. But the #1 silent failure mode? The people who drive transformation leave, and take institutional knowledge with them. I built RetainIQ to solve this — an AI-powered knowledge observability platform for organizations undergoing change: - Automatically maps who knows what across your teams - Knowledge Fragi”
“Full stack devs: you architect frontend + backend + infra. But is your team's architectural knowledge fragile? I built RetainIQ to solve this — an AI platform that maps who knows what in your org, scores Knowledge Fragility Risk (0-100) per domain, and generates automated de-risking tasks. AWS Aldeas 2025 Finalist | Built serverless on AWS Bedrock + Lambda Full write-up: https://lnkd.in/gwFShQiv If you find this useful, please drop a like/reaction on the AWS article — it helps with the AWS AIide”
“The contact form in my 3D portfolio says “Create email draft”. It opens a mailto draft; it does not send the message. The follow-up text asks you to review and send it in your email app. Button labels should match what actually happens.”
“For a GTM automation, I’d define the stop conditions alongside the trigger: Already processed? Skip. Missing evidence? Review. Uncertain result? Check before retrying. A workflow needs a way to avoid repeating the wrong action.”
“A small fix in my portfolio: the sitemap was marking the homepage as modified on every request. I removed that date. A fresh request is not a content update.”
“Before adding another service to an app, I'd ask: Does it need to scale independently? Does it need a separate failure boundary? Is there a clear owner? A diagram with more boxes isn't automatically a better architecture.”
“React, Angular, Next.js devs: you ship features fast. But does your team's knowledge scale as fast as your codebase? Every growing JS team has the same hidden problem — the dev who knows why that legacy Redux store is structured the way it is. The one who remembers the SEO edge cases in the Next.js SSR config. When they leave, the tribal knowledge is gone. I built RetainIQ — an AI platform that maps organizational knowledge risk: - Auto-ingests meeting transcripts, Slack, workflow data - Maps wh”
“When evaluating an email verifier, I’d ask how it represents uncertainty. “Unknown” should be a usable result in the next workflow step. Forcing every address into yes/no hides the cases that need review.”
SQLAdvanced
Apache KafkaMid
Spring BootAdvanced
React.jsAdvanced
FlaskMid
LangChainMid
RAGMid
Code reviewMid
System designMid
ML / AIMid
Cloud / infraMid
Data / analyticsMid
SalesMid
MarketingMid
Go-to-marketMid