He sent 412 applications. Then he added 65 words to his resume.
📄 Arjun Venkata Reddy, 23, BSc Computer Science from a Kukatpally college, applied for jobs 412 times in 11 months. Naukri (320), Apna app (51), LinkedIn (22), company career pages (19). 67 acknowledgements. 18 shortlist calls. 12 phone screens. 7 interviews. 0 offers. His resume listed Python, SQL, HTML, CSS, "basic React." His Naukri profile score was 61%. His resume was not updated since August 2024—four months old, buried under 6,000 newer profiles every week. The Naukri algorithm wasn't being cruel. The algorithm was correct. The resume was honest. It was also algorithmically invisible. 📵

🚨 The problem
Arjun's resume didn't lie. But it didn't use the words the algorithm searches for. It said "basic React" instead of "REST API." It didn't mention "Git" or "Agile" or "Django," even though he had actually used Django in his Nizamabad textile-shop inventory project. He had assumed the framework was too small to mention. The algorithm assumed he had only ever used the skills he explicitly listed. 11 months later, he had answered technical questions correctly in 7 interviews and bombed the spoken English section in all 7.
🚀 How GabFORGE helped
His college friend Deepak, who had gotten a job via a relative's referral six months earlier, felt the weight of that unfairness. He showed Arjun an agent on his phone—switched it to Telugu—and asked: "This resume is honest, right?"
The agent read it and said in Telugu:
- 🎯 "Django use chesa—kaani cheppalisin antav anipinchindi." (You used Django. But you felt you shouldn't say it.) The agent explained: project scale doesn't matter. The keyword does. Algorithms see words.
- 📝 Add 65 exact words. Django, REST API, Git, Agile. Refresh the project descriptions with technical choices Arjun had actually made. Write a one-paragraph summary using job-description language. Update the resume that same evening.
- 📱 Register on two free portals in 40 minutes. NCS (National Career Service) and T-PRIDE Telangana. Both send government job alerts. Both integrate with Naukri. Registration takes names, qualifications, UAN number.
- 🗣️ Practice spoken English for two weeks. 15 minutes every night. The agent asked standard HR questions in Telugu and pointed to specific words to change. Not "what I was finding" but "what I found." Not "I did choose Django" but "I chose Django because."
Arjun's Naukri score jumped from 61% to 84%. In February 2026, he got a call from a Madhapur IT services company for a junior developer role (₹3.2 lakh per annum). He was asked the spoken English script he'd practiced. He gave the story of the inventory project clearly, sequentially, with correct tense and "I chose" instead of "I did choose." Offer came through. ✅
🇮🇳 Why this matters
The gap between doing work and documenting work is where first-generation graduates disappear. Arjun had done the work. He had used Django. The textiles shop in Nizamabad had the system running. But the resume said "basic knowledge of React" instead of the truth: "designed inventory system using Django REST API with Git version control." The algorithm was waiting for the words. So was the hiring manager. But he had to be told that the words mattered.
The long version shows the Kukatpally room, the notebook tracking 412 applications, the moment Deepak installed the agent and showed the resume vulnerability, Arjun's spoken English practice sessions, his sister Divya's question when he got the offer ("Is it more than papa's salary?"), and the ₹2,000 he now sends her for EAMCET coaching materials.