1. What do you currently do and what’s your favorite part about it?I’m a Staff Software Engineer based in San Jose, focused on distributed systems, cloud-native platforms, event-driven architecture, and real-time data engineering. A lot of my work lives in the space where software has to be correct, observable, and repairable under real production pressure: Kafka pipelines, Java and Spring services, APIs, CDC systems, Kubernetes, infrastructure automation, and reliability practices. My favorite part is taking something complex and making it understandable enough that a team can operate it with confidence. I like the moment when architecture stops being a diagram and becomes a set of useful guarantees: this is how data moves, this is how we recover, this is what we can prove, and this is where a human should stay in the loop.2. How did you get started with your Tech Career?I got started the way many engineers do: curiosity first, then increasingly serious debugging. I was drawn to systems that did not just work on one machine, but had to coordinate across services, data stores, queues, APIs, and people. Early in my career, I spent time with backend services, search infrastructure, security analytics, and high-volume data pipelines, which gave me a practical respect for latency, failure modes, and operational visibility. Over time, that grew into work across fintech, retail supply chain systems, billing platforms, inventory systems, and event-driven architectures. The pattern that stuck with me is that good engineering is not only about making something work once; it is about making it explainable, recoverable, and maintainable when conditions are less than perfect.3. If Utopia were a color what color do you think it’d be and why?I think Utopia would be a deep living green with a thin line of electric blue running through it. The green is for something breathable, regenerative, and human, because a perfect future that feels sterile does not sound perfect to me. The blue is for curiosity, systems, invention, and the spark of technology when it is pointed toward something useful. I do not imagine Utopia as a place with no problems; I imagine it as a place where problems can be surfaced early, understood clearly, and repaired without turning people against each other. So the color would need to feel alive and intelligent at the same time.4. If everything about HackerNoon changed drastically, what is one detail you’d like to keep exactly the same? OR What’s your favorite thing to do with HackerNoon and why?I would keep the writer-to-reader energy the same. HackerNoon has always felt like a place where technical people can write with personality, not just publish sterilized corporate documentation. My favorite thing to do with HackerNoon is take a production engineering lesson and turn it into something other practitioners can actually use, especially around distributed systems, recovery, and AI-assisted engineering. I like that a piece about Kafka replay safety or recovery contracts can still have a human voice. The internet has plenty of polished surfaces; HackerNoon is valuable because it still feels like builders talking to builders.5. Tell us more about the things you write/make/manage/build!I build backend platforms and data systems where reliability matters: Java services, Kafka pipelines, cloud infrastructure, APIs, observability, CDC flows, and event-driven systems. My project background includes a cloud-native usage-based billing platform at PayPal, marketplace inventory and fulfillment systems at Nordstrom, Oracle RMS CDC to Kafka work for cost accounting, and security intelligence search infrastructure at Securonix. I also write and speak about practical engineering topics like replay-safe architecture, Recovery Contracts, AI-assisted incident response, and what I call AI Gardening: managing context, memory, and entropy in long-running agentic systems. On the leadership side, I spend time in architecture reviews, API contract discussions, schema governance, Kafka topic design, mentoring, incident readiness, and design validation. The common thread is helping teams build systems that can scale, recover, and be reasoned about by humans.6. What’s your favorite thing about the internet?My favorite thing about the internet is how quickly curiosity can become participation. You can start with a strange production bug, a niche systems question, or a half-formed idea, and within a few hours you can find documentation, code, old forum threads, research papers, and people who have wrestled with the same thing. Then you can add your own lesson back into the commons. That loop is still magical to me: learn from strangers, build something, write it down, and help the next person move faster. At its best, the internet makes knowledge feel alive instead of locked away.7. It’s an apocalypse of ‘walking dead’ proportions and you can only own a singular piece of technology, what would it be?I would choose a rugged, solar-powered tablet loaded with offline maps, medical references, repair manuals, survival guides, and a local knowledge base. In a scenario where the normal internet and power grid are unreliable, raw access to practical information becomes more valuable than most flashy technology. I would want something durable, low-power, searchable, and useful for decision-making under stress. If it also had local radio or mesh communication capability, even better, but the main point would be knowledge you can carry. In an apocalypse, the best technology is probably not the most futuristic one; it is the one that helps you solve real problems without depending on a fragile supply chain.8. What is your least favorite thing about the internet?My least favorite thing about the internet is the incentive system that rewards heat over clarity. The platforms often push people toward outrage, speed, performance, and certainty, even when the subject deserves patience and nuance. That is especially painful in technical spaces, where a half-true explanation can travel faster than the careful version. I do not think the problem is simply that people are careless; I think the structure of attention trains us to compress everything into a reaction. The internet is incredible when it helps people understand each other, and exhausting when it turns every topic into a scoreboard.9. If you were given $10 million to invest in something today what would you invest in and why?I would invest in open-source infrastructure for trustworthy AI-assisted software engineering and public-interest reliability tooling. AI is moving into development workflows, incident response, documentation, code review, and operational decision-making faster than many organizations can properly govern it. We need better tools for evaluation, audit trails, context management, reproducibility, human approval loops, and evidence-first reasoning. I would also put part of that investment into education, because teams do not just need another dashboard; they need shared judgment about where automation helps and where it can cause harm. The goal would be practical: help engineers use AI to improve reliability without turning production systems into experiments with unclear accountability.10. What’s something you’re currently learning or excited to learn?I’m especially excited about agentic AI systems that can stay useful over long-running workflows without drifting away from the problem they were created to solve. That means learning more about context engineering, memory design, evaluation harnesses, tool boundaries, and the operational controls that make AI-assisted systems reviewable. I am also interested in AI-assisted incident response, where the system should assemble evidence before reasoning and rank hypotheses instead of guessing. The hard part is not making an agent sound confident; the hard part is making its work inspectable enough that an engineer can trust the next step. That intersection of distributed systems, observability, and AI reliability feels like a very real frontier.11. Would you rather travel 10 years into the past or 10 years into the future? Give reasons for your answer.I would rather travel 10 years into the future. The past is tempting because it gives you the fantasy of fixing mistakes, but the future gives you feedback about the choices we are making right now. I would want to see what happened with AI, software labor, education, climate resilience, and the shape of the internet after another decade of acceleration. Not because I expect the future to be clean or simple, but because seeing consequences clearly would make today’s priorities sharper. Then I would come back and build with a little more urgency and a little less noise.12. How do you feel about AI?I feel cautiously excited about AI, with real respect for both its power and its failure modes. It can be an amazing collaborator for software design, documentation, code review, research, and operational triage, especially when it helps people see options they might have missed. But AI can also amplify confusion, hide uncertainty, and produce confident answers without enough evidence. The version of AI I want is not magic autopilot; it is a disciplined assistant that surfaces context, shows its reasoning boundaries, and keeps humans accountable for production decisions. For developers, I think AI is becoming a serious extension of the engineering toolkit, but taste, judgment, safety, and responsibility still belong to us.Check out Ishan’s HackerNoon profile here, and read more of his amazing stories!https://hackernoon.com/u/ishan301190