Technical Writer Ka IT Background Se Freelance Journey
This post is also available in EnglishRead in English →

Technical Writer Ka IT Background Se Freelance Journey

Ram Ashare··6 min read

Mere purane laptop pe ek folder tha jiska naam tha runbooks. Usme 40-50 text files padi thi, sab meri likhi hui, sab raat 2 baje ki shift ke doraan.

Main IT support mein tha. L2, Bangalore, ek mid-size company. Jab bhi koi server issue repeat hota tha, main uska step-by-step note bana leta tha taaki agli baar sochna na pade. Ye notes kisi ne mujhe banane ko nahi kaha tha. Main sirf lazy tha aur dobara same cheez debug nahi karna chahta tha.

Teen saal baad mujhe pata chala ki ye exactly wahi kaam hai jiske liye log paise dete hain. Usko technical writing kehte hain.


Pata kaise chala

Ek din team mein ek naya banda aaya. Onboarding ke doraan maine usko apne runbooks ka folder de diya. Do din baad woh aaya aur bola: "Yaar, ye company ki official wiki se better likha hua hai."

Maine usko mazak samjha. Par baat dimaag mein atak gayi.

Us hafte maine LinkedIn pe "technical writer" search kiya. Jo job descriptions dikhi unme likha tha: API documentation, user guides, release notes, knowledge base articles. Main teen saal se yahi cheezein bana raha tha, bas unka naam nahi jaanta tha aur unke paise nahi le raha tha.

Honestly, us waqt thoda bura laga. Teen saal.


Pehli galti: maine socha IT background hi kaafi hai

Ye sabse badi galatfehmi thi meri.

Maine socha ki main technical hoon, main likh bhi leta hoon, toh bas job apply kar dunga aur mil jaayegi. Pehle mahine mein maine 14 applications bheji. Ek bhi reply nahi. Doosre mahine 20 aur bheji. Do rejection emails aaye, baaki silence.

Problem ye thi ki mere resume pe "IT Support Engineer" likha tha aur portfolio mein kuch nahi tha. Hiring manager ko dikh raha tha ek support banda jo career change karna chahta hai. Usko ye nahi dikh raha tha ki main likh sakta hoon.

Mere runbooks kisi ke kaam ke nahi the, kyunki woh internal servers ke baare mein the. Main unhe share bhi nahi kar sakta tha.

Toh technical skill thi, proof nahi tha.


Aisi hi ek real earning story har hafte, seedhe WhatsApp pe.

Join Karo

Portfolio banane wala hissa, jo sabse boring tha

Dekho, yahan koi shortcut nahi mila mujhe.

Maine GitHub pe chhote-chhote open source tools dhoondhne shuru kiye jinki documentation ganda thi. Aisa dhoondhna aasan hai, honestly. Zyadatar developer tools ka README ek hi paragraph hota hai aur baaki sab assume kar liya jaata hai.

Maine teen cheezein banayi:

Ek CLI tool ka getting started guide, 1,100 words. Maine khud tool install kiya, har ek step likha, jo error aaye woh bhi likhe. Ye last wali baat matter karti hai. Zyadatar documentation happy path likhti hai. Real user happy path pe nahi hota.

Ek API reference page ek small open source project ka. Endpoints, request body, response body, error codes. Boring, par yahi cheez clients maangte hain.

Ek troubleshooting article jo maine apne hi purane support experience se likha, bina company ka naam liye. "Why your Docker container exits immediately" type ka. Generic, par real.

Teeno milake shayad 25 ghante lage. Weekend pe. Aur main honestly beech mein do baar chhod chuka tha. Ek baar toh 11 din tak file khola hi nahi.

Par jab teeno ready ho gaye, maine ek chhota sa Notion page banaya aur teeno links daal diye. Bas. Koi fancy website nahi.


Pehli client, aur woh kaise aayi

Ab main soch raha tha ki job apply karunga. Par woh nahi hua.

Ek Twitter thread mein ek indie developer ne likha tha ki uske tool ke docs itne kharab hain ki users same sawaal baar baar poochte hain. Maine reply nahi kiya. Maine DM kiya, aur DM mein sirf teen line likhi: uske tool ka getting-started page maine padh liya hai, usme 4 jagah assumptions hain jo naya user nahi samjhega, aur agar woh chahe toh main ek rewrite bhej doon.

Usne kaha bhej do.

Maine ek section rewrite karke bheja, free. Agle din usne poocha rate kya hai.

Ab yahan par main honest rahunga: mujhe rate pata hi nahi tha. Maine Google kiya, confuse ho gaya, aur ek number bol diya jo baad mein lagta hai kam tha. Usne turant haan bol di, aur jab client turant haan bolta hai toh matlab aapne kam maanga.

Sabak mila. Dukh bhi hua. Par pehli client thi, aur mere Notion page pe ab ek real name tha.


Jo IT background se sach mein kaam aaya

Waise, ek baat clear kar doon. Maine upar likha ki IT background kaafi nahi hai. Woh sahi hai. Par ye nahi ki woh useless hai. Actually wahi mera sabse bada advantage nikla.

Client ne mujhe kabhi ye nahi samjhana pada ki environment variable kya hota hai. Jab usne kaha "yeh endpoint 429 return karta hai rate limiting pe", main samajh gaya. Ek non-technical writer ko woh poora concept explain karna padta.

Terminal comfort ka bhi bada role hai. Main tool khud install karta hoon, khud chalata hoon, khud tod ke dekhta hoon. Isi wajah se meri documentation mein woh errors hote hain jo real users ko aate hain.

Aur teesri cheez: main ticket dekhna jaanta hoon. Support mein teen saal baithne ke baad aapko andaza ho jaata hai ki log kahan atakte hain. Documentation likhte waqt yahi sabse zyada kaam aata hai.


Kya nahi kaam aaya

Meri certifications. Bilkul nahi. Kisi ne nahi poocha.

Mera technical vocabulary shuru mein oolta problem tha. Main jargon mein likhta tha. Pehle client ne mere draft pe comment kiya tha: "This reads like a Stack Overflow answer." Woh compliment nahi tha.

Technical banda hone ka nuksan ye hai ki aapko cheezein aasan lagti hain. Aap bhool jaate ho ki reader ko nahi lagti. Ye unlearn karne mein mujhe kaafi mahine lage, aur honestly abhi bhi kabhi kabhi slip ho jaata hoon.


Ab kya chal raha hai

Abhi main teen clients ke saath kaam kar raha hoon. Do developer tools hain, ek fintech company ka internal knowledge base. Full-time job maine 9 mahine baad chhodi thi, jab do mahine consecutive freelance income job ki salary ke aas paas aa gayi.

Kaam roz ka roz nahi aata. Kuch hafte khaali jaate hain. Pichle mahine ek client ne project pause kar diya bina bataye aur maine 3 hafte bas emails bhejta raha.

Par ab wapas support ticket queue mein baithne ka mann nahi karta. Raat 2 baje ki shift ki woh feeling yaad hai abhi bhi.

Agar aap bhi IT mein ho aur likhna aata hai, toh technical writer bina engineering degree ke bhi bana ja sakta hai, par aapke paas jo technical background hai woh kaafi bada head start hai. Bas usko dikhana padega, aur uske liye portfolio banana hi ek raasta hai.

Main abhi bhi runbooks likhta hoon. Ab bas unke paise aate hain.

Aksar Pooche Jaane Wale Sawaal

IT background wale ko technical writing mein shift karne mein kitna time lagta hai?

Sirf likhna seekhne mein 2-3 mahine kaafi hain agar aap already documentation padhte ho. Par pehli paid client tak pahunchne mein usse zyada lagta hai. Mere case mein gap roughly 7 mahine ka tha, aur usme se 4 mahine sirf portfolio banane aur pitch karne mein gaye.

Kya technical writer banne ke liye coding aani zaruri hai?

Zaruri nahi, par bahut madad karti hai. Agar aap API response padh sakte ho, terminal command run kar sakte ho, aur git clone samajh sakte ho toh aap 80% developer-facing kaam handle kar loge. Poora developer hona zaruri nahi.

Technical writing ke liye portfolio kaise banayein jab client hi nahi hai?

Kisi open source tool ki existing documentation uthao jo kharab likhi hui hai aur usko dobara likho. Maine ek CLI tool ka getting-started page rewrite kiya tha, 1,100 words ka. Wahi sample mere pehle teen pitches mein gaya aur teesre pe kaam mila.

Technical writer ka rate India mein kya chalta hai?

Ye experience aur client location pe depend karta hai. Indian startups usually per-page ya per-hour dete hain, US clients per-hour prefer karte hain. Beginners ko shuru mein kam milta hai, aur pehle saal mein rate revise karna normal hai. Fixed number batana galat hoga kyunki ye niche se niche badal jaata hai.

Technical writing aur content writing mein kya difference hai?

Content writing mein aap reader ko convince karte ho, technical writing mein aap usko kaam karwa dete ho. Ek blog post padh ke banda sochta hai. Ek installation guide padh ke banda install karta hai. Dusre mein creativity kam aur accuracy zyada chahiye.

👤

Ram Ashare

Founder, Simple Kamai

2023 se online earning ke tarike personally try kar raha hoon — freelancing, digital products, affiliate marketing aur zyada. Jo actually kaam kiya wohi yahan likhta hoon.

Aur jaano →

Free: Pehli Kamai Checklist (7-Din Ka Action Plan)

Subscribe karo aur turant paao 7-din ki checklist jo "shuru karunga" se "pehla proposal bhej diya" tak le jaati hai. Saath mein har hafte ek tested tip — koi fluff nahi.

WhatsApp Channel Join Karo

Har hafte earning tips seedhe WhatsApp pe

Free Join Karo →

Dosto ko share karo. Kisi ke kaam aa sakta hai.