<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Priti Singh on Medium]]></title>
        <description><![CDATA[Stories by Priti Singh on Medium]]></description>
        <link>https://medium.com/@pritisingh0904?source=rss-247b2ec1aea0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Xh58VL1o9TF8zGaX</url>
            <title>Stories by Priti Singh on Medium</title>
            <link>https://medium.com/@pritisingh0904?source=rss-247b2ec1aea0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:28:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pritisingh0904/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The AI Opportunity Map: How I Turned Everyday Frustrations Into 10 Product Ideas]]></title>
            <link>https://medium.com/@pritisingh0904/the-ai-opportunity-map-how-i-turned-everyday-frustrations-into-10-product-ideas-e902535e1538?source=rss-247b2ec1aea0------2</link>
            <guid isPermaLink="false">https://medium.com/p/e902535e1538</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ai-product-management]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ideation]]></category>
            <dc:creator><![CDATA[Priti Singh]]></dc:creator>
            <pubDate>Thu, 22 Oct 2026 14:43:00 GMT</pubDate>
            <atom:updated>2026-10-22T14:43:00.078Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EclWHEtcw3PNkAvsCaom7w.png" /></figure><h4><em>An experiment in thinking like an AI Product Manager: starting with problems not technology.</em></h4><p>Every time a new AI tool launches, my first instinct is to think about what I could build with it. A smarter assistant. An automated workflow. A tool that turns one input into ten outputs.<br>But lately, I’ve been thinking about a different question:</p><p><strong>What if the most interesting AI products aren’t waiting for us to discover new technology but for us to notice problems we’ve learned to live with?</strong></p><p>The repetitive task we complain about every Monday. The spreadsheet we update manually. The information we know exists somewhere but can never find when we need it. The decision that takes an hour because the context is scattered across five different places. These frustrations might seem ordinary. But they can be the starting point for meaningful product opportunities.</p><p>So I wanted to try a small product discovery experiment: identify everyday frustrations, translate them into problems worth solving and brainstorm 10 possible AI product opportunities.</p><p>Ten problems worth investigating.</p><h3>My AI Opportunity Map</h3><p>I divided everyday frustrations into five areas:</p><blockquote>work<br>personal productivity<br>money <br>information overload <br>software development.</blockquote><p>Here are 10 opportunities that emerged from this brainstorming exercise.</p><h3>1. SayLess — From Messy Thoughts to Professional Communication</h3><p><strong>The problem:</strong> People know what they want to say but spend too much time turning rough thoughts into polished work messages, emails, updates and documentation.</p><p><strong>The opportunity:</strong> Transform rough notes into context-aware communication tailored to the recipient, format, tone and level of detail while preserving the user’s original intent.</p><h3>2. Prompt-to-Product — An AI Design Studio</h3><p><strong>The problem:</strong> Turning an app idea into a complete, consistent product design requires significant time spent creating screens, connecting user flows and maintaining a coherent design system.</p><p><strong>The opportunity:</strong> Generate interconnected, high-fidelity product screens from natural-language prompts with editable components, connected user flows and responsive previews. Allow users to refine individual screens through conversational instructions without unintentionally changing the rest of the product.</p><h3>3. SimuUser — Test Your Product With AI Users</h3><p><strong>The problem:</strong> Product teams often discover confusing navigation, unclear instructions and broken user journeys late in development because usability testing can be expensive and time consuming.</p><p><strong>The opportunity:</strong> Let teams upload a prototype, define target user personas and simulate task based user journeys to identify potential usability issues, dead ends and friction points. Generate journey replays and prioritised findings while clearly distinguishing simulated insights from validated feedback from real users.</p><h3>4. DealRoom — AI-Powered Advertising Deal Management</h3><p><strong>The problem:</strong> Advertisers, agencies and publishers manage deal information, pricing, requirements, approvals and communication across disconnected tools, making deals difficult to evaluate and coordinate.</p><p><strong>The opportunity:</strong> Build an intelligent workspace that centralises advertising deal discovery, evaluation, negotiation and activation. Use AI to summarise deal terms, match opportunities to campaign requirements, flag missing information and surface potential risks before activation.</p><h3>5. Design Debt Radar — Detect and Prioritise UI Inconsistencies</h3><p><strong>The problem:</strong> As digital products evolve, interfaces accumulate inconsistent components, spacing, typography, colours and interaction patterns, making products harder to maintain and redesign.</p><p><strong>The opportunity:</strong> Analyse supplied screenshots, designs and code to detect design system inconsistencies, identify recurring patterns and prioritise fixes based on their impact. Generate suggested corrections and previews that help teams reduce design debt systematically.</p><h3>6. Skill Swap — The Barter Network for Skills</h3><p><strong>The problem:</strong> People want to learn new skills or get help with projects but may not have the budget for courses, consultants or freelancers. At the same time they possess valuable skills they could exchange.</p><p><strong>The opportunity:</strong> Create a skill barter platform where users exchange expertise without requiring direct monetary payment. Use AI to match complementary skills, suggest fair exchanges, structure learning agreements and coordinate sessions even when two users need different skills from different people in the network.</p><h3>7. Context Recovery Assistant — Pick Up Where You Left Off</h3><p><strong>The problem:</strong> Returning to a project after several days can mean spending an hour reconstructing what happened, which decisions were made, why they were made and what still needs to be done.</p><p><strong>The opportunity:</strong> Generate project specific briefings from available discussions, documents, decisions and outstanding tasks. Provide source-linked summaries of recent changes, unresolved questions, blockers and next steps so users can resume work without reconstructing the entire project history.</p><h3>8. Brief Completeness Checker — Catch Missing Requirements Before Work Begins</h3><p><strong>The problem:</strong> Teams often begin design or development with incomplete briefs, ambiguous instructions and conflicting requirements only discovering the gaps after work has already started.</p><p><strong>The opportunity:</strong> Evaluate briefs against configurable requirements, identify missing information and ambiguities, detect contradictions and generate targeted clarification questions. Provide a readiness report that helps teams resolve critical gaps before implementation.</p><h3>9. Elder Care Coordination Hub — AI-Assisted Family Care</h3><p><strong>The problem:</strong> Families coordinating care for ageing parents often rely on scattered messages, paper records and memory to manage appointments, responsibilities, medical documents and follow-ups.</p><p><strong>The opportunity:</strong> Create a shared care coordination workspace that organises appointments, documents, family responsibilities and follow up tasks into one timeline. Use AI to extract actionable information from user-provided records, flag scheduling conflicts or missed follow-ups and help family members coordinate care while leaving medical decisions to qualified professionals.</p><h3>10. Medical Paperwork Advocate — Navigate Bills and Insurance Claims</h3><p><strong>The problem:</strong> Patients and caregivers struggle to understand medical bills, insurance denials, pre-authorisation requirements and complicated appeals processes.</p><p><strong>The opportunity:</strong> Help users interpret bills, denial letters and policy documents in plain language; identify potentially missing documentation or inconsistencies; draft appeal letters; and track deadlines. Link explanations to the supplied documents and flag cases that require confirmation from the insurer or a qualified professional.</p><p>These are hypotheses, not validated business opportunities. Each one would need research to establish whether the problem is frequent, painful, underserved and worth solving.</p><p>My next step would be to choose three ideas and investigate them more deeply. That means speaking to potential users, observing their existing workflows, understanding workarounds, examining competitors and testing whether the problem is significant enough to justify a solution.</p><p>Only then would I commit to an MVP.</p><h3>What this experiment taught me about product thinking</h3><p>Brainstorming ideas reminded me that ideation is only one part of product management. The more important work is turning vague frustrations into specific problems, understanding who experiences them, evaluating alternatives and identifying what evidence would justify building a solution.</p><h3>What’s next?</h3><p>I’d like to take one of these opportunities from a brainstormed hypothesis to a working prototype: define the user problem, investigate existing solutions, write a PRD, design the experience and establish how I would evaluate the AI component before shipping it.Because the real test of an AI product idea isn’t whether it sounds innovative. It’s whether it solves a problem people genuinely care about and whether it does so reliably enough to earn their trust.</p><p><em>This is the beginning of my exploration of AI product management: learning to identify opportunities, make deliberate trade-offs and turn promising ideas into useful products.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e902535e1538" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Book I Almost Didn’t Pick Up]]></title>
            <link>https://medium.com/@pritisingh0904/the-book-i-almost-didnt-pick-up-32017548cb03?source=rss-247b2ec1aea0------2</link>
            <guid isPermaLink="false">https://medium.com/p/32017548cb03</guid>
            <category><![CDATA[spirituality]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[Priti Singh]]></dc:creator>
            <pubDate>Sun, 27 Sep 2026 12:10:55 GMT</pubDate>
            <atom:updated>2026-09-27T12:10:55.303Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/687/1*55OdYwdjEpmzO8zYH7R6_g.png" /></figure><h4>The power of positve thinking</h4><p>There’s a particular kind of stillness that comes with rock bottom. Not dramatic not cinematic just quiet. The kind where you stop reaching for things you used to love including reading because your mind is too loud to let anything else in.</p><p>That’s where I was when I found <em>The Power of Positive Thinking</em>.</p><p>It wasn’t even mine. It was a birthday gift someone had given my sister years earlier, sitting untouched on a shelf collecting dust the way unread books do. I don’t fully know what made me pick it up that day. I think I just needed <em>something</em> , anything to distract me from the loop of self doubt and other people’s judgment that had taken up permanent residence in my head. I wasn’t looking for answers. I was looking for a way to stop thinking for a while. I didn’t expect the book to actually answer anything. I just wanted the noise to stop.</p><h4>The Lines That Stopped Me</h4><p>I don’t remember every chapter in order anymore but I remember exactly where I was when two lines stopped me mid page:</p><p><em>“build wholesome self esteem”</em></p><p><em>“If God be for us, who can be against us?”</em></p><p>I’d probably heard both before in passing, the way familiar words lose their weight from overuse. But this time they landed differently. I think it’s because I was finally quiet enough, empty enough to actually hear them instead of just reading them.</p><p>The lines in the book became something I returned to quietly over and over. Not as slogans but as something closer to permission. Permission to stop shrinking under other people’s opinions of me. Permission to believe I was allowed to rebuild.</p><h4>What Actually Changed</h4><p>It wasn’t instant. Nothing that matters usually is but slowly,</p><p>The judgment of others that used to control my choices started losing its grip.</p><p>I found my way back to spirituality not as an obligation but as something that genuinely held me up.</p><p>My self doubt didn’t disappear, but it stopped being the loudest voice in the room for me.</p><p>I started building something I hadn’t had in a long time, wholesome self-esteem. Not arrogance just a quiet , steady confidence that didn’t need anyone else’s approval to exist.</p><p>Mental peace, which had felt impossible slowly became normal again.</p><p>My beliefs got stronger and with them the whole shape of how I was living.</p><h4>Why This Book, Why Then.</h4><p>I’ve thought about this a lot why <em>this</em> book, found in <em>that</em> way at <em>that</em> exact moment. A gift originally meant for my sister, given by a friend sitting untouched until I needed it most.</p><p>Maybe that’s the real lesson underneath all of it: sometimes the things that save us aren’t things we go looking for. They’re already sitting quietly on a shelf waiting for the day we’re finally desperate enough or open enough to reach for them.</p><p>If you’re in your own version of rock bottom right now, I won’t pretend one book is a cure. But I will say this - sometimes healing doesn’t start with a plan. It starts with picking something up, dusting it off and letting yourself be surprised.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=32017548cb03" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI Product Management 101: Turning Models into Real Products]]></title>
            <link>https://medium.com/@pritisingh0904/ai-product-management-101-turning-models-into-real-products-7ba949cc2de9?source=rss-247b2ec1aea0------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ba949cc2de9</guid>
            <category><![CDATA[generative-ai]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[ai-products]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Priti Singh]]></dc:creator>
            <pubDate>Wed, 03 Jun 2026 11:50:33 GMT</pubDate>
            <atom:updated>2026-06-03T11:50:33.496Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yDOzgl4dAscX1syIUtbC-Q.png" /></figure><h4>Building an AI Product From Idea to Deployment</h4><h3>Introduction</h3><p>Every day new AI products are launched with the promise of transforming industries. Yet many of them fail to create real impact. The problem isn’t the technology ; AI today is more powerful than ever. The challenge is that teams often focus so much on building advanced models that they overlook the people and problems they’re meant to serve.</p><p>Building a successful AI product goes far beyond training a model. It requires understanding users, solving real problems, making the right technical choices and continuously improving through feedback. In this article we’ll explore the complete journey of building an AI product from a simple idea to a production ready solution.</p><h3>Step 1: Start with a Problem, Not AI</h3><p>Many founders make the mistake of starting with</p><blockquote><em>“I want to use AI.”</em></blockquote><p>Instead, start with</p><blockquote><em>“What problem am I solving?”</em></blockquote><p>Good AI products solve expensive, repetitive or data heavy problems.</p><h3>Problem Validation Checklist</h3><p>✓ Is the problem real?</p><p>✓ Does it occur frequently?</p><p>✓ Are users actively seeking solutions?</p><p>✓ Can AI perform the task better or faster?</p><p>If AI is not necessary, don’t use AI.</p><h3>Step 2: Define Your Users</h3><p>Understanding users is crucial.</p><p><strong>For example, if you’re building an AI powered news summarizer:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/926/1*LCslGxyp2Ac1wrIzAc1G7Q.png" /></figure><h3>Step 3: Define Product Requirements</h3><p>Convert user problems into features.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v_PvZFhR2pkQtg71XwuTwQ.png" /></figure><h3>Step 4: Collect and Prepare Data</h3><p>Data is the fuel of AI systems. The quality of your data often matters more than the complexity of your model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/913/1*ae1X-C8IuRgJQOdtle0K3A.png" /></figure><h3>Step 5: Choose the Right AI Approach</h3><p>Not every problem requires deep learning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/623/1*yITa5Ok7HkiEQhhGX9pfFg.png" /></figure><h4>Traditional Machine Learning</h4><p><em>Best for</em>: Fraud detection, Classification, Prediction</p><p><em>Examples</em>: Random Forest, XGBoost, Logistic Regression</p><h4>Deep Learning</h4><p><em>Best for: </em>Images , Audio, Complex text tasks</p><p><em>Examples: </em>CNNs, RNNs, LSTMs, Transformers</p><h4>Generative AI</h4><p><em>Best for: </em>Chatbots, Content creation, Summarization, Code generation</p><p><em>Examples: </em>GPT models, Claude, Gemini</p><h3>Step 6: Build the MVP</h3><p>The biggest mistake is overbuilding. Create the smallest version that solves the core problem.</p><p>For example:<strong> News Summarizer MVP</strong></p><p><strong>Features:</strong></p><p>✓ Upload article</p><p>✓ Generate summary</p><p>✓ Display output</p><p><strong>Avoid:</strong></p><p>✗ Complex dashboards</p><p>✗ Advanced personalization</p><p>✗ Enterprise integrations</p><p>Launch quickly and learn from users.</p><h3>Step 7: Design the AI Pipeline</h3><p>A typical <strong>AI pipeline</strong> looks like:</p><pre>User Input<br>      ↓<br>Preprocessing<br>      ↓<br>AI Model<br>      ↓<br>Post processing<br>      ↓<br>User Interface</pre><p>For Generative AI products:</p><pre>User Query<br>      ↓<br>Prompt Engineering<br>      ↓<br>LLM<br>      ↓<br>Response Validation<br>      ↓<br>Output</pre><h3>Step 8: Evaluate Performance</h3><p>AI systems need measurement.</p><h3>Model Metrics</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CG4XMlGSScX_pz1HuMVzwg.png" /></figure><h3>Step 9: Deploy to Production</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kDQJsNYNw-uIYeZCy-1wVw.png" /></figure><h3>Step 10: Monitor and Improve</h3><p>Deployment is not the finish line.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/683/1*S7U7L3ufRHGaFG7m3CAKIg.png" /></figure><h3>Modern AI Product Architecture</h3><pre>Frontend<br>    ↓<br>API Gateway<br>    ↓<br>Backend Services<br>    ↓<br>LLM / ML Model<br>    ↓<br>Vector Database<br>    ↓<br>Knowledge Base</pre><p><strong>Examples of technologies:</strong></p><ul><li>OpenAI, LangChain, Pinecone, Weaviate, PostgreSQL, AWS</li></ul><h3>Common Reasons AI Products Fail</h3><h3>1. No Real Problem</h3><p>Technology first thinking.</p><h3>2. Poor Data</h3><p>Garbage in, garbage out.</p><h3>3. Ignoring Users</h3><p>Building features nobody wants.</p><h3>4. Overengineering</h3><p>Complexity before validation.</p><h3>5. No Monitoring</h3><p>Models degrade over time.</p><h3>The Future of AI Products</h3><p>The next generation of AI products will move beyond simple chatbots.</p><h4>Key trends include:</h4><ul><li>AI Agents</li><li>Multimodal AI</li><li>Autonomous Workflows</li><li>Personalized AI Assistants</li><li>Human AI Collaboration Systems</li></ul><p>The companies that succeed will not necessarily have the best models they will have the best understanding of their users and workflows.</p><h3>Conclusion</h3><p>Building an AI product is not just a machine learning challenge; it’s a product challenge.</p><p>The winning formula is simple:</p><p><strong>Problem → Users → Data → Model → MVP → Deployment → Feedback → Improvement</strong></p><p>Teams that follow this cycle consistently are far more likely to build AI products that users genuinely love and use.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ba949cc2de9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When AI Took My Interview And It Felt Surprisingly Human]]></title>
            <link>https://medium.com/@pritisingh0904/when-ai-took-my-interview-and-it-felt-surprisingly-human-dc042479ca94?source=rss-247b2ec1aea0------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc042479ca94</guid>
            <dc:creator><![CDATA[Priti Singh]]></dc:creator>
            <pubDate>Sat, 02 May 2026 13:14:47 GMT</pubDate>
            <atom:updated>2026-05-02T13:14:47.268Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*--4FSdj_XrHC-ioCLDuBmw.png" /></figure><h3>When AI Took My InterviewAnd It Felt Surprisingly Human</h3><p>We’ve all heard about AI transforming industries, automating tasks and reshaping the future of work. But experiencing it firsthand in something as personal as an interview? That’s a different story.</p><p>Recently, I had the opportunity to go through an AI-powered interview conducted by ProofOfSkill and I walked in with pretty standard expectations.</p><p>I thought it would be robotic.<br> Predictable.<br> Maybe even a little awkward.</p><p>But it turned out to be none of those things.</p><h3>First Impressions: Expectation vs Reality</h3><p>Like most people, I assumed an AI interview would follow a fixed script asking generic questions, waiting for responses and moving on without context. Something more like a formality than an actual evaluation.</p><p>Instead, the experience felt… fluid.</p><p>The questions weren’t just relevant; they felt thoughtfully sequenced. One question led naturally to another, almost as if the system was actively listening and adapting. It didn’t feel like I was interacting with a machine , it felt like a conversation.</p><h3>It Wasn’t About “Right Answers”</h3><p>What stood out the most was that the interview didn’t feel like a test.</p><p>There was no pressure to deliver textbook perfect answers. Instead, it encouraged me to think, explain my reasoning and approach problems in my own way. It shifted the focus from <em>what I know</em> to <em>how I think</em>.</p><p>That’s something even traditional interviews don’t always get right.</p><h3>The Comfort Factor</h3><p>Interviews can be nerve wracking. There’s always that subtle pressure being judged, trying to read the interviewer’s reactions, dealing with pauses or interruptions.</p><p>This experience removed a lot of that friction.</p><p>There were no awkward silences.<br> No intimidating expressions.<br> No feeling of being rushed.</p><p>Just a clean space to think and respond.</p><p>And surprisingly, that made me perform better.</p><h3>So… What Does This Mean for the Future?</h3><p>This experience made me rethink how we view AI in hiring.</p><p>We often talk about AI replacing human roles but this felt more like <em>enhancement</em> than replacement. It showed how AI can make processes more structured, unbiased and even more comfortable for candidates.</p><p>Of course, human interaction will always have its place. But if AI can handle the initial stages with this level of quality, it could make hiring more efficient and accessible for everyone.</p><h3>Final Thoughts</h3><p>I didn’t expect to say this but an AI interview turned out to be one of the most engaging interview experiences I’ve had.</p><p>It was structured yet flexible.<br> Challenging yet comfortable.<br> Automated, yet surprisingly human.</p><p>And if this is where we are now, I’m genuinely curious to see what comes next.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc042479ca94" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Organized HackStomp 24 Hrs: A 24-hour College Hackathon]]></title>
            <link>https://medium.com/@pritisingh0904/how-i-organized-hackstomp-24-hrs-a-24-hour-college-hackathon-e31e428c6571?source=rss-247b2ec1aea0------2</link>
            <guid isPermaLink="false">https://medium.com/p/e31e428c6571</guid>
            <dc:creator><![CDATA[Priti Singh]]></dc:creator>
            <pubDate>Sun, 05 Apr 2026 13:46:28 GMT</pubDate>
            <atom:updated>2026-04-05T13:46:28.137Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/756/1*6w7-TNaCsBwtj2ACu1oH2w.png" /></figure><p>Hackathons changed my engineering life.<br>By my second year, I was already hooked: building projects, burning midnight oil and presenting ideas to strangers who later became mentors. I even got selected to the Smart India Hackathon finals, which showed me how powerful a well run hackathon can be for students, judges and industry together.</p><p>From that moment, I wanted to bring that energy to my own college.<br>Not just as a participant but as the person behind the scenes.<br>Two years later that dream became HackStomp 24 Hrs — a 24 hour hackathon I organized as part of the executive committee, hosted at Universal SkillTech University / Universal College of Engineering, Vasai.</p><p>You can check out the official event space here: <a href="https://hackstomp.com/">https://hackstomp.com</a></p><h3>From Participant to Organizer</h3><p>Before HackStomp, I had attended multiple hackathons both online and offline. The Smart India Hackathon finals was a turning point: I saw how careful planning, good mentoring and real industry judges could push students to build serious solutions, not just “demo day toys.”</p><p>I started asking:</p><blockquote><em>“What if our college had its own 24‑hour hackathon?”</em></blockquote><p>Then we tried to pitch HackStomp 24 Hrs — a social coding event that brings students from different colleges together to build or improve software over 24 hours, exactly as described on the official page.</p><h3>Building HackStomp, Step by Step</h3><p>At first, HackStomp was just a rough plan:</p><ul><li>A 24‑hour hackathon</li><li>Open to multiple colleges</li><li>Focus on real world problems</li><li>Judged by industry professionals</li></ul><p>Slowly, we turned it into a concrete plan:</p><ul><li>Timeline: Months of prep → weeks of promotions → final week logistics</li><li>Registration: Forms → WhatsApp groups → constant updates</li><li>Sponsorship and logistics: Food, Wi‑Fi, cloud credits, swag and certificates</li></ul><p>We leaned into the idea of HackStomp as a “social coding” event not just a competition but a place where students meet, collaborate and learn from each other.</p><h3>The Big Weekend: March 13–14 2026</h3><p>HackStomp 24 Hrs went live on March 13–14.<br>By the time the event kicked off, the campus felt like a small tech festival. Laptops everywhere, whiteboards scribbled with ideas and that unique smell of coffee and adrenaline.</p><p>For me, it all started on stage.<br>I’ve been anchoring events for four years in college — from farewells to convocations, from tech fests to cultural nights.<br>HackStomp was special because It was my first hackathon as an anchor, It was my last major event as an anchor before graduating.</p><p>Standing there under the lights, welcoming students, judges and faculty, I felt a mix of responsibility and excitement. From there, the 24‑hour coding marathon began.</p><h3>Inside the 24‑Hour Marathon</h3><p>The structure of HackStomp 24 Hrs was simple but intense.</p><p>As the event progressed, the energy shifted:</p><p><strong>Day </strong>: Idea curation, Mentoring sessions, Quick workshops</p><p><strong>Night </strong>: Debugging chaos, Last minute framework switches, Midnight snacks and memes</p><p>I walked around the venue, checking in on teams, making sure the Wi‑Fi and power were still alive and quietly cheering for the ones who were stuck on a single if‑else block at 3 am.</p><h3>Judges, Friends and That Night Out Vibe</h3><p>One of the most exciting parts of HackStomp was the judge lineup.<br>We had professionals from Google and other big tech / product companies, which gave students a rare chance to:</p><ul><li>Present to real industry experts</li><li>Get feedback on their architecture and UX</li><li>Think beyond “just passing the evaluation”</li></ul><p>Between mentoring sessions and judging rounds, the vibe felt like a night out with friends, except the destination was a hackathon.<br>We had:</p><ul><li>Late night conversations about careers, startups and side projects</li><li>Random introductions that turned into collab groups</li><li>Inside jokes about “sleep being a bug” and “coffee being the main dependency”</li></ul><p>It wasn’t just a coding event , it was a mini road trip of its own.</p><h3>What I Learned From Running HackStomp</h3><p>Organizing HackStomp 24 Hrs taught me more than most internships or projects. Here are the big lessons:</p><h3>1. Leadership is mostly logistics</h3><p>The “vision” part is easy; the execution is the real test.</p><h3>2. People matter more than perfection</h3><p>We didn’t get everything perfect some teams had last minute complaints, some judging sessions felt rushed.<br>But what worked was: Listening, Explaining , Fixing quickly</p><p>When students felt heard, they forgave the small glitches.</p><h3>3. Event running is project management in disguise</h3><p>Managing HackStomp was like running a software project:</p><ul><li>Scope: event structure, themes, duration</li><li>Timeline: months → weeks → days → hours</li><li>Risk plan: backup internet, backup mentors, backup food</li></ul><p>The executive committee was my core team and the college was the client.</p><h3>Why HackStomp Was My Most Special Event</h3><p>HackStomp 24 Hrs was special for three reasons:</p><ol><li>It was my first hackathon as an organizer not just a participant or volunteer.</li><li>It was my last major event as an anchor in college, giving closure to four years of stage time.</li><li>It was a 24 hour social coding marathon that brought together strangers, friends and mentors in one continuous night of learning.</li></ol><p>Looking back, it felt full circle:<br>From second year student attending hackathons to final year student running one.</p><h3>If You Want to Organize a Hackathon in Your College</h3><p>If you’re reading this and thinking about organizing a hackathon in your college, here’s how to start:</p><p><em>Start small: Even a 4 hour mini hackathon is enough.</em></p><p><em>Use existing platforms (Unstop, own website, WhatsApp, Discord).</em></p><p><em>Leverage your ecosystem: Professors, clubs, alumni and local startups are your early supporters.</em></p><p><em>Reach out to companies for small sponsorships or mentorship.</em></p><p><em>Focus on the experience, not just prizes</em></p><p><em>Good food, good Wi‑Fi and friendly mentors matter.</em></p><p><em>Create a “social coding” vibe , not just a competition.</em></p><p><em>Showcase it on the web</em></p><p><em>A simple event site like </em><a href="https://hackstomp.com/"><em>https://hackstomp.com</em></a><em> gives you credibility and makes registration smoother.</em></p><p><em>Use it to list: theme, dates, tracks, prizes and judge profiles.</em></p><p><em>If a student who once struggled to present a simple project in second year could now stand on stage, anchor a 24 hour hackathon and coordinate teams, judges and sponsors — you can too.</em></p><h3>Final Thoughts</h3><p>HackStomp 24 Hrs wasn’t just an event.<br>It was the culmination of my hackathon journey from participant to organizer, from stage fresher to lead anchor, from coding for myself to enabling others to build, ship and learn.</p><p>If you’re reading this and you’ve never been part of a hackathon team or event, let this be your nudge:</p><ul><li>Join the next hackathon your college announces Or better yet, start planning your own.</li></ul><p>Because the best way to understand the future of tech?<br><strong>Not just by watching it but by building it with your friends in 24 hours.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e31e428c6571" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI Is Not Stealing Jobs, Bad Career Advice Is.]]></title>
            <link>https://medium.com/@pritisingh0904/ai-is-not-stealing-jobs-bad-career-advice-is-0038fa95ae4c?source=rss-247b2ec1aea0------2</link>
            <guid isPermaLink="false">https://medium.com/p/0038fa95ae4c</guid>
            <category><![CDATA[students]]></category>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Priti Singh]]></dc:creator>
            <pubDate>Mon, 02 Feb 2026 07:12:57 GMT</pubDate>
            <atom:updated>2026-02-02T07:12:57.922Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z1k5G8yxaraGONCUo1R5Gw.jpeg" /></figure><h4>Technology evolves; bad guidance stays dangerously behind.</h4><p>Everyone keeps saying the same thing: <strong>“AI is taking over jobs.”</strong><br>But if you look closely, that’s not the real problem.</p><p>The real problem is <strong>bad career advice</strong> i.e.<strong> </strong>outdated, vague and dangerously misleading.</p><p>AI isn’t stealing jobs.<br>It’s exposing how poorly we’ve been preparing people for them.</p><h3>The Fear Around AI Is Understandable but Misplaced</h3><p>Every generation has faced a <strong>“job-killer”</strong> technology.</p><ul><li>Computers were supposed to kill office jobs</li><li>The internet was supposed to kill businesses</li><li>Automation was supposed to kill manufacturing</li></ul><p>Yet, jobs didn’t disappear, <strong>they evolved</strong>.</p><p>AI is doing the same thing.</p><p>The difference?<br> This time, people are being told to <em>either fear it</em> or <em>blindly chase it</em>.</p><p>Both are terrible advice.</p><h3>The Most Common (and Harmful) Career Advice Today</h3><p>Here’s what students and early professionals keep hearing:</p><ul><li>“Just learn AI, you’ll be safe”</li><li>“Coding is the only future”</li><li>“Pick one skill and master it forever”</li><li>“Follow the trend”</li></ul><p>This advice ignores one critical truth:</p><blockquote><strong><em>Careers don’t break because of technology.<br> They break because of rigidity.</em></strong></blockquote><h3>AI Isn’t Replacing People , It’s Replacing Tasks</h3><p>Let’s be honest.</p><p>AI doesn’t replace <em>roles</em>.<br> It replaces <strong>specific tasks</strong> inside roles.</p><ul><li>Writing boilerplate code</li><li>Drafting basic content</li><li>Generating reports</li><li>Analyzing repetitive data</li></ul><p><em>So what happens next?</em></p><p>The <strong>human part of the job becomes more important</strong>:</p><ul><li>Decision-making</li><li>Context understanding</li><li>Creativity</li><li>Communication</li><li>Ethics</li><li>Product thinking</li></ul><p>If your entire career is built on <em>just one repetitive task</em>, that’s risky, with or without AI.</p><h3>The Real Divide: Adaptable vs. Static Professionals</h3><p>AI is creating two groups of people:</p><h3>1. Those who use AI as a tool</h3><p>They:</p><ul><li>Learn faster</li><li>Build better solutions</li><li>Ask better questions</li><li>Focus on impact, not just execution</li></ul><h3>2. Those who avoid or fear AI</h3><p>They:</p><ul><li>Stick to outdated workflows</li><li>Rely on memorized skills</li><li>Resist change</li></ul><p>Guess who struggles more?</p><p>Not because AI took their job<br>but because <strong>they refused to evolve</strong>.</p><h3>Why Students Feel More Anxious Than Ever</h3><p>Students today aren’t scared of working hard.<br> They’re scared of <strong>working hard on the wrong thing</strong>.</p><p>And that fear is valid.</p><p>When advice lacks clarity, people:</p><ul><li>Overlearn without direction</li><li>Chase every trend</li><li>Feel “behind” all the time</li><li>Lose confidence</li></ul><p>AI didn’t create this confusion.<br><strong>Poor guidance did.</strong></p><h3>What Good Career Advice Looks Like in the AI Era</h3><p>Good advice sounds boring, but it works.</p><p>Instead of:</p><blockquote><em>“Learn AI or you’ll be irrelevant”</em></blockquote><p>Try this:</p><ul><li>Learn <strong>how your field uses AI</strong></li><li>Build <strong>problem-solving skills</strong></li><li>Combine <strong>technical + human skills</strong></li><li>Stay curious, not just certified</li></ul><p>The safest career path is not a single tool.<br> It’s the ability to <strong>learn, unlearn and relearn</strong>.</p><h3>Final Thought</h3><p>AI is not your enemy, blindly following trends is.</p><p>If your career advice hasn’t changed in 10 years, it’s already obsolete.</p><p>The future doesn’t belong to people who fear AI but<br> it belongs to people who <strong>think critically, adapt quickly and learn continuously</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0038fa95ae4c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Being a Fresher Really Feels Like]]></title>
            <link>https://medium.com/@pritisingh0904/what-being-a-fresher-really-feels-like-b2e1922681a8?source=rss-247b2ec1aea0------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2e1922681a8</guid>
            <category><![CDATA[early-career]]></category>
            <category><![CDATA[self-development]]></category>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[career-growth]]></category>
            <category><![CDATA[freshers-life]]></category>
            <dc:creator><![CDATA[Priti Singh]]></dc:creator>
            <pubDate>Fri, 02 Jan 2026 13:37:04 GMT</pubDate>
            <atom:updated>2026-01-02T13:37:04.161Z</atom:updated>
            <content:encoded><![CDATA[<h4>No one really prepares you for this phase.</h4><p>You graduate, update your LinkedIn headline, maybe add “Aspiring ___” to your bio and suddenly you’re a <em>fresher</em>.</p><p>On paper, it sounds exciting ; new beginnings, fresh opportunities, endless potential.</p><p>In reality?<br>It’s confusing, overwhelming and quietly exhausting.</p><p><strong>You’re Expected to Know Everything (Without Ever Being Taught).</strong></p><p>As a fresher, you’re constantly caught between two expectations:</p><blockquote><em>“You’re new, it’s okay if you don’t know.”</em></blockquote><blockquote><em>“Why don’t you already know this?”</em></blockquote><p>Job descriptions ask for <strong>entry-level experience</strong> with tools you’ve barely heard of. Interviews assume hands on exposure that college never gave. And tutorials online jump from “Hello World” straight to production level complexity. You start wondering: Did I miss something everyone else learned?</p><p>Most of the time, you didn’t. The system just skips steps.</p><p><strong>Everyone Looks Ahead of You (Especially Online).</strong></p><p>This is probably the hardest part. You open LinkedIn and see people your age announcing jobs, celebrating internships, posting “grateful to share” updates. Meanwhile, you’re refreshing job portals, rewriting resumes and questioning your abilities. What you don’t see is their rejections, their unpaid work, their months of confusion.</p><p>Being a fresher feels like standing still while everyone else is moving forward even though that’s rarely the full truth.</p><p><strong>You Start Doubting Yourself Constantly.</strong></p><p>You doubt your skills.<br> You doubt your degree.<br> You even doubt your interests.</p><p>One day you’re confident about your path. The next day, one rejection email makes you rethink everything. You ask yourself</p><ul><li><em>What if I never figure this out?</em></li><li><em>Did I choose the wrong field?</em></li><li><em>Am I good enough?</em></li></ul><p>This self doubt isn’t weakness. It’s uncertainty mixed with pressure and almost every fresher goes through it.</p><p><strong>You’re Learning Outside the Classroom (A Lot)</strong></p><p>College ends, but learning doesn’t.</p><p>As a fresher, most of your real learning happens through side projects, late night Google searches, YouTube tutorials, trial and error.</p><p>You realize grades matter less than skills but no one tells you <em>which</em> skills matter most. So you try everything sometimes too much at once and feel lost again. Still, this phase quietly builds something important and that is <strong>self learning discipline</strong>.</p><p><strong>You Feel Behind , Even When You’re Not.</strong></p><p>There’s an invisible clock ticking.</p><blockquote>“By this age, I should have a job.”</blockquote><blockquote>“By now, I should be settled.”</blockquote><blockquote>“Others already know what they’re doing.”</blockquote><p>But the truth is, being a fresher means you’re <em>at the beginning</em>, not late. No one masters a career in their first year. No one figures life out immediately after college , they just pretend better.</p><p><strong>Small Wins Start Meaning More</strong></p><ul><li>When you’re a fresher</li><li>finishing a project feels huge,</li><li>getting a reply email feels validating,</li><li>clearing one interview round feels like progress.</li></ul><p>And it <em>is</em> progress.</p><p>These small wins don’t look impressive on social media but they’re building confidence slowly, quietly, steadily.</p><p><strong>You’re Growing, Even When It Doesn’t Feel Like It.</strong></p><p>This phase teaches you things no syllabus ever could like patience, resilience, how to handle rejection, how to keep going without certainty.</p><p>You learn how to sit with discomfort. How to try again. How to believe in yourself when no one else is watching.</p><p>That growth isn’t visible yet but it’s real.</p><p><strong>What I Wish Someone Told Me Earlier</strong></p><p>If you’re a fresher reading this, here’s what you need to hear:</p><ul><li>You’re not behind.</li><li>Confusion doesn’t mean failure.</li><li>Rejections don’t define your potential.</li><li>It’s okay to take time to figure things out.</li><li>Everyone starts somewhere, even the people you admire.</li></ul><p>Being a fresher isn’t about having everything sorted.<br>It’s about <strong>showing up, learning and not quitting on yourself</strong>.</p><p>And one day, sooner than you think, you’ll look back and realize this uncertain phase was where everything actually began.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2e1922681a8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Chose AIML But I Didn’t Know What I Was Getting Into.]]></title>
            <link>https://medium.com/@pritisingh0904/i-chose-aiml-but-i-didnt-know-what-i-was-getting-into-1ee111959070?source=rss-247b2ec1aea0------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ee111959070</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[engineering-students]]></category>
            <category><![CDATA[learning-journey]]></category>
            <category><![CDATA[career-confusion]]></category>
            <category><![CDATA[personal-growth]]></category>
            <dc:creator><![CDATA[Priti Singh]]></dc:creator>
            <pubDate>Fri, 19 Dec 2025 22:10:03 GMT</pubDate>
            <atom:updated>2025-12-19T22:10:03.304Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*95h13lYENwD_-WrRa192eA.png" /></figure><h4><strong>What I expected from AI, what actually happened and why confusion became my biggest teacher</strong></h4><p>I chose Artificial Intelligence and Machine Learning because it sounded exciting, futuristic and if I’m being honest, IMPRESSIVE.</p><p>Back then AIML felt like the <em>smart choice</em>. Everyone around me talked about AI replacing jobs, machines learning on their own and how this field was “the future.” I imagined myself building intelligent systems, working on cutting edge tech and having everything figured out.</p><p>What I didn’t realize was that choosing AIML would confuse me, humble me and force me to learn things no syllabus ever mentioned.</p><p>This isn’t a success story.<br>It’s a learning story.</p><h3>What I Thought AIML Would Be</h3><p>When I entered my undergraduate program, I thought AIML meant:</p><ul><li>Writing cool machine learning models</li><li>Working only with Python and AI libraries</li><li>Clear career paths and certainty</li><li>Feeling confident about my skills</li></ul><p>I assumed that if I followed the syllabus, everything would fall into place. It didn’t.</p><h3>What AIML Actually Turned Out to Be</h3><p>Very quickly, I realized that AIML isn’t just about algorithms.</p><p>It’s about:</p><ul><li>Debugging code that refuses to work</li><li>Understanding data before training models</li><li>Writing SQL queries when you least expect it</li><li>Learning backend concepts, APIs, and databases</li><li>Reading error messages longer than the actual code</li></ul><p>I found myself learning <strong>SQL</strong>, exploring <strong>quality assurance concepts</strong>, working on <strong>projects and hackathons </strong>and trying to understand how real applications actually function.</p><p>At one point, I asked myself:</p><blockquote>“Am I even doing AIML anymore?”</blockquote><h3>The Phase No One Talks About: Confusion</h3><p>This was the hardest part. I saw people online becoming ML engineers, mastering DSA, launching startups, building insane projects. Meanwhile, I was switching between domains, Feeling like I knew a little of everything but nothing deeply. Constantly questioning my direction. There were days I felt behind. Days I felt I chose the wrong field. Days I wondered if everyone else had a roadmap except me.</p><h3>Hackathons Changed Everything</h3><p>Hackathons were a turning point. They didn’t care about my branch or my specialization. They cared about:</p><ul><li>Can you solve the problem?</li><li>Can you work with a team?</li><li>Can you learn fast?</li></ul><p>In hackathons, I learned:</p><ul><li>How messy real world problems are</li><li>How important communication is</li><li>That knowing <em>how to learn</em> matters more than knowing everything</li></ul><p>I learned more in those intense hours than I ever expected and that realization was both empowering and scary.</p><h3>What AIML Actually Taught Me (Beyond AI)</h3><p>Even though I didn’t become a “pure” AIML expert, this journey taught me something more valuable:</p><h3>1. Tech Is Interconnected</h3><p>AI doesn’t exist in isolation. It touches databases, backend systems, product thinking and user experience.</p><h3>2. It’s Okay to Explore</h3><p>Trying SQL, QA, analytics or business roles didn’t make me confused , it made me aware.</p><h3>3. Being a Beginner Is Not a Weakness</h3><p>You don’t need to be an expert to start. You just need to keep showing up.</p><h3>4. Clarity Comes From Action</h3><p>Not from thinking. Not from comparing. But from trying.</p><h3>If You’re a Student Feeling Lost, This Is for You</h3><p>If you’re an engineering student questioning your choices, Someone who feels late, slow or behind, Someone who doesn’t fit neatly into one role</p><p>Let me tell you this, You’re not failing.<br>You’re learning.</p><p>Most of us don’t have linear journeys. We have messy ones. And that’s okay.</p><h3>I’m Still Figuring It Out</h3><p>I don’t have all the answers yet. I’m still learning, still experimenting, still growing. But now, instead of fearing confusion, I see it as part of the process.</p><p>Choosing AIML didn’t give me clarity overnight but it gave me exposure, resilience and the courage to explore. And maybe that’s what education is really supposed to do.</p><h3>Final Thought</h3><p>You don’t need to have everything figured out at 20, 21, or even 25. Sometimes, choosing a field isn’t about mastering it immediately, it’s about discovering who you become along the way.</p><p>If you’re on a similar path, you’re not alone and this is just the beginning.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ee111959070" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>