Skip to content

Commit 621437d

Browse files
shadil-rayyanshadil-rayyan
committed
docs(job): overhaul job section with actionable guides
- Added internship_guide.md: cold emailing, platforms, timeline - Added interview_prep.md: DSA, core subjects, behavioral tips - Rewrote resume.md: focus on structure, action verbs, ATS tips - Rewrote portfolio-website.md: tech stack options, content structure
1 parent 6b5b650 commit 621437d

4 files changed

Lines changed: 160 additions & 77 deletions

File tree

‎docs/job/internship_guide.md‎

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
# 💼 Internship Hunting Guide
2+
### "How to Get Hired Before Your Degree"
3+
4+
Getting an internship is the single best thing you can do for your career. It counts 10x more than your GPA.
5+
6+
---
7+
8+
## 📅 When to Start?
9+
* **1st Year:** Focus on learning skills. Don't stress about internships yet. Build 1-2 small projects.
10+
* **2nd Year:** Apply for "Startup Internships" or Open Source programs (like GSSoC).
11+
* **3rd Year (Crucial):** This is the "Golden Year". You need a Summer Internship (May-July) to convert into a PPO (Pre-Placement Offer).
12+
* **4th Year:** Use your internship experience to sit for placements.
13+
14+
---
15+
16+
## 📨 The "Cold Email" Technique
17+
Applying on portals (LinkedIn/Naukri) is crowded. **Cold Emailing** is the cheat code.
18+
19+
### The Template
20+
> **Subject:** Internship Opportunity: Backend Developer | [Your Name]
21+
>
22+
> Hi [Founder/CTO Name],
23+
>
24+
> I’ve been following [Company Name] and love your recent work on [Specific Feature]. I noticed you are scaling your backend, and I’d love to contribute.
25+
>
26+
> I have experience with **Node.js, MongoDB, and Redis**. I recently built **[Project Name]** (Link: [github.com/...]) which handles [X] users.
27+
>
28+
> I am looking for a 2-month internship. I am willing to work hard and learn fast.
29+
>
30+
> Best,
31+
> [Your Name]
32+
> [Portfolio Link] | [Resume Link]
33+
34+
### Where to Find Emails?
35+
1. **Founder's LinkedIn:** Check "Contact Info".
36+
2. **Company About Page:** Look for `careers@company.com` or `founders@company.com`.
37+
3. **Twitter/X:** Many founders have DMs open.
38+
39+
---
40+
41+
## 🏆 Platforms to Apply On
42+
1. **LinkedIn:** Filter by "Posted in last 24 hours" + "Less than 10 applicants".
43+
2. **Internshala:** Good for local/small startups, but be careful of low-quality unpaid work.
44+
3. **Wellfound (AngelList):** The BEST place for startup internships. High quality, often remote.
45+
4. **Cuvette / Unstop:** Great for hiring challenges and hackathon-based hiring.
46+
47+
---
48+
49+
## 🚩 Red Flags (Avoid These!)
50+
* **"Pay to Intern":** If a company asks YOU for money for "training" before the internship, it is a **SCAM**. Run away.
51+
* **Unpaid (Exploitative):** Unpaid is okay *only* if you are learning a lot and it's your very first one. If you are writing production code that makes them money, you deserve to be paid.

‎docs/job/interview_prep.md‎

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
# 🧠 Interview Preparation
2+
### "Cracking the Coding Interview"
3+
4+
The interview process for Software Engineering is standardized. You don't need to be a genius; you just need to practice the specific patterns.
5+
6+
---
7+
8+
## 🧩 1. Data Structures & Algorithms (DSA)
9+
This is 70% of the interview.
10+
* **Language:** Choose C++ or Java (Python is okay, but C++/Java are preferred for core concepts).
11+
* **Platform:**
12+
* **LeetCode:** The gold standard.
13+
* **Blind 75:** A curated list of the 75 most common interview questions. **Solve these first.**
14+
* **Topics:** Arrays, Linked Lists, Trees, Graphs, Dynamic Programming.
15+
16+
## 💻 2. Core CS Subjects (The Theory)
17+
For Freshers, companies ask theoretical questions to check your basics.
18+
* **DBMS (Database):** Normalization, SQL vs NoSQL, Indexing, ACID Properties.
19+
* **OS (Operating Systems):** Processes vs Threads, Deadlocks, Memory Management.
20+
* **CN (Networks):** HTTP vs HTTPS, OSI Model, TCP/IP Handshake.
21+
* **OOPs:** Inheritance, Polymorphism, Encapsulation, Abstraction.
22+
23+
## 🎨 3. System Design (LLD)
24+
* **Freshers:** Rarely asked "High Level Design" (like Scale).
25+
* **Focus on:** "Design a Chess Game" or "Design a Parking Lot" (Low-Level / Class Design).
26+
27+
## 🗣️ 4. Behavioral (HR Round)
28+
* **"Tell me about yourself":** Have a 2-minute prepared pitch.
29+
* **"Why do you want to join us?":** Research the company.
30+
* **"Describe a challenge you faced":** Use the **STAR** method (Situation, Task, Action, Result).
31+
32+
---
33+
34+
## 📅 Study Plan (3 Months)
35+
* **Month 1:** Learn a language (C++/Java) + Basic DSA (Arrays/Strings).
36+
* **Month 2:** Advanced DSA (Trees/Graphs) + Core Subjects (DBMS/OS).
37+
* **Month 3:** LeetCode Grind (Blind 75) + Mock Interviews.
38+
39+
> **Tip:** Do NOT memorize code. Memorize the **pattern** (e.g., "Oh, this is a Sliding Window problem").

‎docs/job/portfolio-website.md‎

Lines changed: 33 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -1,53 +1,49 @@
1-
# 🌐 What is a Portfolio Website & Why Every Student Needs One
1+
# 🌐 Building Your Portfolio
2+
### "Show, Don't Just Tell"
23

3-
A **portfolio website** is your **personal website** where you showcase who you are, what you’ve built, and why someone (a recruiter, mentor, or collaborator) should notice you. Think of it as your **digital identity** — your online resume + project gallery + personal brand, all in one place.
4+
A resume tells them you *can* code. A portfolio **proves** it.
45

56
---
67

7-
## ✅ Why you need a portfolio website
8+
## 🛠️ How to Build It (The Right Way)
89

9-
* **First impression** — Before recruiters even see your resume, they often Google you. A portfolio website shows professionalism.
10-
* **Show, don’t just tell** — Instead of just saying “I know Python,” you can **show projects, GitHub repos, and live demos**.
11-
* **Proof of skills** — Projects, hackathons, blogs, open-source work — all displayed in one hub.
12-
* **Personal brand** — Stand out from thousands of other resumes by telling *your story*.
13-
* **Search visibility** — With your name + skills on a website, you’re discoverable online (LinkedIn/GitHub alone isn’t enough).
14-
* **Future-ready** — Tech interviews, internships, and even freelance clients often ask for a portfolio link.
10+
### Option A: The "Developer" Way (Recommended)
11+
Build it yourself. It shows you know HTML/CSS/React.
12+
* **Tech Stack:** HTML/CSS (Beginner) or React/Next.js (Advanced).
13+
* **Hosting:** GitHub Pages (Free) or Vercel (Free).
14+
* **Domain:** Buy a domain (e.g., `yourname.com`) for $10/year using Namecheap. It looks super professional.
1515

16-
---
17-
18-
## 🚀 Why you should make one **as soon as possible**
19-
20-
* **Compounding effect** — The earlier you build it, the more time you have to keep adding projects and achievements.
21-
* **Internships in first/second year** — Many opportunities ask for project links; having a personal website makes you stand out early.
22-
* **Practice web dev** — Even building your portfolio is itself a skill (HTML, CSS, React, or Next.js).
23-
* **Networking boost** — When you attend hackathons, workshops, or meetups, sharing a simple link is powerful.
16+
### Option B: The "No-Code" Way (Fast)
17+
If you are a backend dev and hate CSS.
18+
* **Bento.me:** A link-in-bio style portfolio. Very trendy right now.
19+
* **Peerlist:** A developer-focused professional network.
20+
* **Notion:** You can turn a Notion page into a website.
2421

2522
---
2623

27-
## 🔎 What to put in a portfolio website
24+
## 📝 What to Include?
2825

29-
* 👤 **About you** — short intro, photo, what you’re studying.
30-
* 💻 **Projects** — highlight 3–5 best projects (with GitHub links & live demos).
31-
* 📜 **Resume** — downloadable PDF.
32-
* 📝 **Blog/articles** (optional) — share what you learn.
33-
* 🌍 **Contact info** — email, LinkedIn, GitHub, maybe Twitter.
34-
* ⭐ **Achievements** — hackathons, scholarships, certifications.
26+
### 1. The Hero Section
27+
* **Who are you?** "Hi, I'm [Name]. I build scalable backends."
28+
* **Call to Action:** "Check out my work" or "Download Resume".
3529

36-
---
30+
### 2. The Basics
31+
* **About Me:** A short, fun bio. "I love coffee and debugging."
32+
* **Tech Stack:** Use icons (React logo, Python logo).
3733

38-
## ⚡ How it helps you
39-
40-
* **Placement & internships** — HRs and recruiters prefer candidates who show work, not just grades.
41-
* **Freelancing** — Clients can instantly see your past work.
42-
* **Scholarships & global opportunities** — Many application forms have a “Portfolio/Website link” field.
43-
* **Confidence boost** — Seeing your growth displayed motivates you.
44-
45-
---
34+
### 3. The Projects (Critical)
35+
Only list your **Top 3** projects.
36+
* **Thumbnail:** A screenshot of the app.
37+
* **Title & Description:** Short explainer.
38+
* **Links:** **Code** (GitHub) and **Live Demo** (Website Link).
39+
* *Note:* If you don't have a Live Demo, you lose 90% of visitors. Deploy your apps!
4640

47-
👉 In simple words:
48-
A **portfolio website = your personal career showroom**.
49-
The earlier you set it up, the more powerful it becomes over time.
41+
### 4. Blog (Optional but Powerful)
42+
* Write about what you learn. "How I fixed a CORS error today".
5043

5144
---
5245

53-
Would you like me to also **make a sample roadmap + free tools list** (like GitHub Pages, Netlify, Vercel, etc.) for building your first portfolio website quickly?
46+
## � Pro Tips
47+
* **Mobile Responsive:** Check your site on your phone. If it breaks, fix it. Recruiters use phones.
48+
* **Dark Mode:** Developers love dark mode.
49+
* **Don't over-engineer:** A simple site that loads fast is better than a 3D animated site that crashes the browser.

‎docs/job/resume.md‎

Lines changed: 37 additions & 40 deletions
Original file line numberDiff line numberDiff line change
@@ -1,59 +1,56 @@
1-
# 📄 What is a Resume & Why You Must Build One Early as a CSE Student
1+
# 📄 The Perfect Software Resume
2+
### "Your Ticket to the Interview"
23

3-
A **resume** is a **1–2 page document** that summarizes your **skills, education, projects, and achievements**. It is the first thing recruiters, professors, or organizers look at when you apply for an **internship, scholarship, hackathon, or placement**.
4+
Recruiters spend an average of **6 seconds** looking at a resume. If they don't see what they want, you are rejected.
45

56
---
67

7-
## ✅ Why you should make your resume **as soon as possible**
8-
9-
* **Lightning opportunities** — Sometimes you’ll see an internship/hackathon/scholarship with just 24–48 hours to apply. If you don’t already have a resume, you’ll miss out.
10-
* **First-year advantage** — You may think you don’t have much to put in, but even basic projects, coding practice, or school achievements count. Start now, improve later.
11-
* **Seniority pressure** — Seniors often say “Send me your resume fast, I’ll refer you.” Without one ready, you lose the chance.
12-
* **Professional habit** — Building a resume early makes you **track your progress** and forces you to build projects/skills to fill it.
8+
## 🚫 Common Mistakes (Fix These First!)
9+
1. **Two Columns:** ATS (Applicant Tracking Systems) often cannot read two-column layouts. **Use a Single Column layout.**
10+
2. **Photos/Icons:** Do not put your photo (unless you are a model). It wastes space and causes bias.
11+
3. **Skill Bars:** "Python: 80%". What does that mean? 80% of what? Remove these. Just list the skill.
12+
4. **Objective Statement:** "Passionate student looking for..." -> Delete this. We know you are looking for a job.
1313

1414
---
1515

16-
## 📌 What a CSE resume should have
17-
18-
1. **Contact Information** — Name, email, LinkedIn, GitHub, portfolio website.
19-
2. **Education** — College, branch (CSE), year, CGPA (if good).
20-
3. **Skills** — Languages (Python, Java, C++), tools (Git, Linux, SQL).
21-
4. **Projects** — Short, impactful descriptions with tech stack and results.
22-
5. **Experience** — Internships, freelance, open-source contributions (if any).
23-
6. **Achievements** — Hackathons, scholarships, coding contest ranks.
24-
7. **Positions of Responsibility** — Clubs, societies, organizing events.
16+
## ✅ The Ideal Structure (Order Matters)
2517

26-
---
18+
### 1. Header
19+
* **Name** (Big & Bold).
20+
* **Links:** LinkedIn, GitHub, Portfolio (Make them clickable!).
21+
* **Contact:** Email, Phone Number.
2722

28-
## 🎯 Best structure that works for CSE students
23+
### 2. Education
24+
* College Name, Degree (B.Tech CSE).
25+
* CGPA (Only include if > 7.5. Otherwise, leave it out).
26+
* Graduation Year.
2927

30-
* **One-page resume** — clear, easy to read.
31-
* **Bullet points** instead of paragraphs.
32-
* **Strong verbs** (Built, Developed, Optimized, Automated).
33-
* **Show impact** (e.g., *“Built a quiz app used by 200+ students”*).
34-
* **Tailor for roles** — different resumes for internships vs research vs placements.
35-
36-
---
28+
### 3. Skills (The Keyword Farm)
29+
* **Languages:** C++, Java, JavaScript, Python, SQL.
30+
* **Frameworks:** React.js, Node.js, Express, Flutter.
31+
* **Tools:** Git, Docker, Linux, MongoDB.
32+
* **Core:** DSA, OOPs, DBMS.
3733

38-
## 🚀 Pro Tips
34+
### 4. Projects (The Meat)
35+
* **Format:** Project Name | *Tech Stack Used* | [Link]
36+
* **Description:** Use bullet points.
37+
* *Bad:* "I made a weather app."
38+
* *Good:* "Built a Weather Dashboard using **React.js** and **OpenWeatherMap API** that displays real-time forecasts for 500+ cities with 99% uptime."
3939

40-
* Keep it **ATS-friendly** (simple fonts, no fancy designs, use PDF).
41-
* Update every 3–6 months.
42-
* Link **GitHub repos, portfolio website, and LinkedIn**.
43-
* Ask seniors or mentors for feedback — they know what recruiters want.
40+
### 5. Experience (If any)
41+
* Internships, Open Source Contributions, Volunteer work.
4442

4543
---
4644

47-
## 🎥 YouTube Video for You
48-
49-
👉 [How to Make a Perfect Resume for Computer Science Students (YouTube)](https://www.youtube.com/watch?v=O2QWj3Jtr4M)
50-
51-
*(Tip: There are many resume guide videos, but the above is beginner-friendly and focused on CSE.)*
45+
## 🪄 The "Action Verb" Magic
46+
Start every bullet point with a strong verb.
47+
* **Built**, **Deployed**, **Optimized**, **Reduced**, **Improved**, **Designed**.
48+
* *Example:* "**Reduced** api loading time by 40% using Redis caching."
5249

5350
---
5451

55-
⚡ **Bottom line:** A resume is your **career passport**. Don’t wait until final year — build it in first year, keep polishing, and be always ready when the right opportunity knocks.
56-
57-
---
52+
## 📥 Free Templates (ATS Friendly)
53+
* **Overleaf :** you can find good resume for cs in overlead it is also easy to edit later
54+
* **FlowCV:** A great free builder.
5855

59-
Do you want me to also **create a sample one-page resume template (ATS-friendly)** for a **first-year CSE student** with sections already filled (skills, projects, achievements)?
56+
> **Rule of Thumb:** If it looks boring, it's probably a good resume. Recruiters want data, not art.

0 commit comments

Comments
 (0)