Siddhant Jain

Looking for a full-stack developer role! My portfolio, resume, and project links are attached in the description below. I’d love your feedback on my resume! Please like and retweet for maximum reach. Let’s build something great. 📷 #BuildInPublic #FullStack #WebDev #Hiring"

@merishabh_singh But I guess it's not enough now to get hired anymore! github.com/CoolSidOfficial

The fastest way to upskill? Build projects.

@longwire sended!

We’re Hiring: Frontend Developer Intern (Remote) 💼 Role: Frontend Developer Intern 📍 Location: Remote, India 📩 How to apply: Send your portfolio/resume (with deployed project links) to hr@dodox.in (or DM me directly)

@Misbahtwts hehe

only developers who are unemployed can reply to this post

@itsfarshidabdi thx

One tip from someone who taught himself to code and pivoted from a completely different career — the projects on your portfolio matter more than anything on the resume. Ship something small that solves a real problem and talk about the decisions you made building it. That's what gets attention.

Looking for a full-stack developer role! My portfolio, resume, and project links are attached in the description below. I’d love your feedback on my resume! Please like and retweet for maximum reach. Let’s build something great. 📷 #BuildInPublic #FullStack #WebDev #Hiring"

@shregupta89 coolsid.tech x.com/officialcoolsi…

I work at a banglore based fintech startup and its currently hiring for Backend/AI intern roles. Any batch with relevant POW or experience is welcome. Tech stacks req: Python, postgres,familiar with langGraphs Comment your portfolios/resumes/POW below. Will reach out to you if suited for the role. Keep your dms open

@shotsinmind treat java nicely!

@officialcoolsid We are from same cllg bro, im from 2027 batch 🙌 lets hope for the best

@ThisIsBhandari DMs not opened

@officialcoolsid we have full time roles available. maybe we can talk in dm

@0xlelouch_ Built a scrappy Flask tool to track company-wise most-asked interview questions from a CSV… never shipped it Last time I went “too far,” I wrote a C++ script generating state-wise Indian phone numbers for cracking-related use and got banned on GitHub. 😅 gofile.io/d/xo8jLN

And if you’re targeting specific companies, add these: Amazon: 146 LRU Cache 692 Top K Frequent Words 994 Rotting Oranges 863 All Nodes Distance K in Binary Tree 1152 Analyze User Website Visit Pattern Google: 23 Merge k Sorted Lists 224 Basic Calculator 772 Basic Calculator III 129 Sum Root to Leaf Numbers 358 Rearrange String k Distance Apart Meta: 560 Subarray Sum Equals K 1762 Buildings With an Ocean View 670 Maximum Swap 987 Vertical Order Traversal of a Binary Tree 1249 Minimum Remove to Make Valid Parentheses Microsoft: 139 Word Break 56 Merge Intervals 236 Lowest Common Ancestor 240 Search a 2D Matrix II 460 LFU Cache Uber: 127 Word Ladder 973 K Closest Points 297 Serialize and Deserialize Binary Tree 253 Meeting Rooms II 341 Flatten Nested List Iterator Netflix: 981 Time Based Key-Value Store 636 Exclusive Time of Functions 721 Accounts Merge 295 Find Median from Data Stream 79 Word Search --- If you do: 10 patterns x 4-6 good problems each 20-25 company-focused questions You’ll already be more prepared than most candidates who just say “I’ve done 500+ LeetCode.” Solve by pattern. Revise by template. Practice by company. That’s how you can crack DSA rounds fast.

@aShubhamz @shydev69 @amaan8429 @adxtyahq @Abhinavstwt @AbhinavXJ @abhijitwt @karankendre @shrav_10 @Divyansh91565 😂😂🤣🤣🤣

@officialcoolsid @shydev69 @amaan8429 @adxtyahq @Abhinavstwt @AbhinavXJ @abhijitwt @karankendre @shrav_10 @Divyansh91565 Ayush and amaan me itna gap kyun diya h bakiyon se?

@shikhars_ coolsid.tech

Any early stage startups hiring a frontend engineer? Have a strong person to refer.

@0xlelouch_ Will create a leetcode list for these specific questions , and share it below later!!

Preparing for DSA interview, do these leetcode problems! 1. Sliding Window: 3, 76, 424, 904 2. Two Pointers: 11, 15, 167, 42 3. Binary Search: 33, 153, 875, 1011 4. Hashing + Prefix: 1, 49, 560, 128 5. Monotonic Stack: 739, 503, 84, 901 6. Heap (Top K): 215, 347, 973, 703 7. Intervals: 56, 435, 57, 252 8. BFS/DFS: 200, 994, 102, 133 9. Trees: 104, 236, 543, 124 10. DP basics: 70, 198, 322, 300 Just 2-3 per pattern, write the template from memory, then speedrun variants.

@robert_shaw coolguide.live

SaaS/Startup founders What are you building currently? Show your amazing product below, join 100+ founders here every week. #indiehackers #buildinpublic

@crescentforeal coolsid.tech For Frontend Role

Update: Backend Dev secured ✅ Designer onboard, but still looking for a stronger fit. Open roles: • 2 Devs (Frontend / Web3) • 1 Graphics Designer Follow me up to keep in touch DM's and Drop your portfolio below 👇

@0xlelouch_ Changes according to your tweet

Reviewed a resume today and here is the honest breakdown. The Good: - Clean one-page format. Easy to scan. - Good project depth for a student resume. - Shows actual shipping mindset, not just tutorial work. - Mentions production-ish things like OAuth, async jobs, Redis, Docker, rate limiting, presigned URLs, WebSockets. - Has numbers in a few places like 1,000+ daily users and 20+ deployments. This helps. - Freelance experience makes it more believable than random college projects. --- The Bad: - It is still too stack-heavy and not outcome-heavy enough. - Saying Node.js, Redis, Docker is fine. But recruiters care more about: 1. what problem you solved, 2. what scale it handled, 3. what improved after your work. 4. Some bullets are too long. A good bullet should hit fast: action + system + impact. Right now a few bullets read like mini paragraphs. “Built features using OpenAI API, LangChain, vector embeddings” in skills is weak. That line is vague and sounds like buzzword stuffing unless backed by a strong project bullet. Education is taking prime real estate. For someone with good projects and freelance work, experience/projects should dominate more. “Picked up React Native from scratch and shipped in 15 days” is impressive, but it can sound a little dramatic unless you explain result better. What happened after shipping? Users? retention? client result? --- The Ugly: - No clear positioning. - Is this person a backend engineer? full-stack dev? SaaS builder? AI engineer? - The resume shows many things, but no sharp identity. That confuses recruiters. - Too much “I built X” and not enough “X mattered because Y”. For example: not just “built multi-platform social media SaaS” but “reduced manual posting work for creators/businesses by automating cross-platform publishing”. - A few bullets sound like feature lists, not engineering achievements. - Feature lists do not get interviews. - Engineering impact does. Missing stronger proof of quality: performance improvements, latency reduction, cost savings, uptime, delivery speed, bug reduction, customer adoption, revenue impact. Without these, even strong work can look average. --- My verdict: This is a good resume for a student/fresher. Not bad at all. Actually above average. But it is not yet a killer resume. It has real work. It has proof of initiative. It has decent technical depth. Now it needs better packaging. Some resume lesson for devs: Projects get attention. Clarity gets interviews. Impact gets offers. A resume should not read like: “here are the technologies I touched” It should read like: “here is why hiring me makes your team stronger”

@0xlelouch_ thx , any update?

@officialcoolsid Sure

Reviewed a friend’s resume today. He is a young backend engineer, worked on product backends, trading workflows, infra, Solana stuff, and some pretty serious Rust projects too. On first look, the resume feels strong cause there is real work in it, not just random tutorial projects and fake impact lines. But after reading it properly, I was reminded of something many engineers do wrong: A resume can have good work and still be badly positioned. Good: - Real backend experience in production - Ownership over infra and backend systems - Good technical projects, especially the Rust HTTP/3 and ingestion work - Strong enough stack for backend roles like Rust, Go, TypeScript, PostgreSQL, Docker, AWS - Built things used by actual users, which already puts him ahead of many resumes Bad: - Some bullets feel too inflated for the years of experience - A few metrics are not strong enough to impress, like “1000 active users” sounds honest but not like a killer signal - Too many keywords are packed into single lines - Summary is generic and does not clearly say what kind of engineer he really is - Good work is there, but the story is not sharp Ugly: - “AI-assisted development” section should be deleted fully - Some bullets sound more like research abstract than resume bullet - It tells me tech used, but not enough about what problem was solved - Strongest points are buried under fancy wording - It tries a bit too hard to sound advanced instead of sounding credible --- My biggest takeaway after reviewing his resume: A lot of software engineers are not held back by lack of skill. They are held back by weak positioning. Your resume is not the place to sound intellectual. It is the place to sound clear, useful, and believable. Built what? For whom? At what scale? What improved? That is it. Not every bullet needs to sound like you invented distributed systems. A good resume makes recruiter think: “This person can come in and solve backend problems.” A bad one makes recruiter think: “This person knows many words.” Very small difference in writing. But massive difference in outcomes.

@nitesh_singh5 Interested

Role - Full-Stack Developer Intern Stipend - ₹50K - ₹100K per month Experience - 0-3 years - Building and maintaining web apps with Next.js - Problem-solving skills Let us know if you are Interested 👇

@AvinashSingh_20 CoolGuide is a personalized digital guide that recommends products or content step-by-step based on user preferences. coolguide.live

Startup founders building in public, don’t be shy- comment on what you’re building. Let’s network.