# Project Pitch Framework: HR ko apna project samjhao > Final-year project non-tech interviewer ko kaise batayein: Problem, Solution, Result ka 3-step frame, 2 bhare hue examples aur 60-second practice plan Free guide by bloopcommits (@bloopcommits) ยท https://bloopcommits.pages.dev/project/ HR ya non-tech manager ko React, API ya database se matlab nahi hota. Unhe dikhta hai ki kisi ka kya masla solve hua. Is guide mein wahi 3-step frame hai jo reel mein bola gaya, saath mein bharne ke liye template aur do examples. > **Pehle ye padho** > > - Ye general advice hai, guarantee nahi. > - Result wahi bolo jo sach mein tumhare paas hai. Number banane ki zaroorat nahi. > - Neeche ke dono examples banaye hue hain: unhe apne asli project se badal do. ## Jargon se shuru mat karo Tech stack bolne se pehle asli problem batao: kisko kya dikkat thi. Tech ke shabd follow-up sawaal ke liye bacha ke rakho. ## 3-step frame 1. Problem: kisko, kya dikkat thi. 2. Solution: tumne kya banaya, sirf ek line mein. 3. Result: kya nikla, ya kya seekha (jo sach mein hai). ## Bolne ka template **Template** ``` Hamara project [problem] ko solve karta hai. Maine [tech] use karke [solution] banaya, jisse [result] mila. ``` ## Banaya hua example 1: notes app | Step | Kya bolna hai | | --- | --- | | Problem | College students ke notes bikhre hue rehte hain. | | Solution | Maine ek simple web app banayi, jisme saare notes ek jagah milte hain aur subject ke hisaab se search hote hain. | | Result | Dost aasaani se notes dhoondh paaye, aur mujhe seekhne ko mila ki users ki baat pehle sunni chahiye. | ## Banaya hua example 2: attendance tracker | Step | Kya bolna hai | | --- | --- | | Problem | Class mein attendance haath se likhne mein time jaata hai aur galtiyan hoti hain. | | Solution | Maine ek chhota tool banaya jisme teacher ek click mein present ya absent mark kar sakta hai. | | Result | Hamare testing mein attendance lene ka kaam saaf aur tez laga. Seekha ki chhoti cheez bhi kaam ki ho sakti hai. | ## Interviewer kya dekhta hai - Baat saaf hai ya nahi: ek line mein samajh aati hai? - Kaam kyun zaroori tha: tumhe pata hai ya nahi. - Tumne kya seekha, bina badhaye. ## Aam galtiyan - Tech stack ki lambi list se shuru karna. - Result mein jhoota number likhna. - Sirf 'maine banaya' bolna, 'kyun banaya' nahi. - Bina practice ke pehli baar interview mein bolna. ## 60-second practice plan 1. Apne project ke Problem, Solution, Result teen alag line mein likho. 2. Template mein bharo aur zor se bol ke dekho: 60 second se kam. 3. Phone mein record karo aur khud sun lo. 4. Ek dost se pucho: 'kya samajh aaya?' Jo samajh na aaye, use saral karo. 5. Tech ki detail ek alag note mein rakho, follow-up ke liye. > **Yaad rakho** > > - Problem, Solution, Result. Teen line, ek minute. > - Tech ke shabd follow-up ke liye bacha ke rakho. --- More free guides: https://bloopcommits.pages.dev/