Yash Saraswat

𝗧𝗵𝗶𝘀 𝗶𝘀 𝗵𝗼𝘄 𝗺𝘆 𝗿𝗲𝘀𝘂𝗺𝗲 𝗴𝗼𝘁 𝘀𝗲𝗹𝗲𝗰𝘁𝗲𝗱 𝗮𝘁 𝗨𝗯𝗲𝗿 𝗳𝗼𝗿 𝗦𝗗𝗘-𝟭 From a string of rejections to seeing “Congratulations! Your profile has been shortlisted for the SDE-1 role at Uber” — this is the story behind that email. When I started my journey, 𝗜 𝗱𝗶𝗱𝗻’𝘁 𝗵𝗮𝘃𝗲 𝗮 𝗽𝗲𝗿𝗳𝗲𝗰𝘁 𝗿𝗲𝘀𝘂𝗺𝗲. I didn’t have big brand names on my profile. What I did have was the willingness to build, learn, and improve every single day. Here’s what I changed over time that made all the difference: 1️⃣ 𝗕𝘂𝗶𝗹𝘁 𝘄𝗶𝘁𝗵 𝗶𝗺𝗽𝗮𝗰𝘁 𝗶𝗻 𝗺𝗶𝗻𝗱 – Not just random projects, but ones that solved real problems. 2️⃣ 𝗦𝘁𝗮𝘆𝗲𝗱 𝗰𝗼𝗻𝘀𝗶𝘀𝘁𝗲𝗻𝘁 𝘄𝗶𝘁𝗵 𝗗𝗦𝗔 – Not marathon study sessions, but steady, focused problem-solving that strengthened my foundation. 3️⃣ 𝗧𝗿𝗲𝗮𝘁𝗲𝗱 𝗺𝘆 𝗿𝗲𝘀𝘂𝗺𝗲 𝗹𝗶𝗸𝗲 𝗮 𝗽𝗿𝗼𝗱𝘂𝗰𝘁 – Iterated, tested, tailored for each role, and kept it ATS-friendly. 4️⃣ 𝗚𝗮𝗶𝗻𝗲𝗱 𝗵𝗮𝗻𝗱𝘀-𝗼𝗻 𝗲𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲 – Through internships where I delivered production-ready solutions and learned how real engineering teams work. 💡 What a good resume should have: ✔ 𝗧𝗮𝗶𝗹𝗼𝗿𝗶𝗻𝗴 – Match it to the job description instead of sending a generic version. ✔ 𝗜𝗺𝗽𝗮𝗰𝘁 𝘀𝘁𝗮𝘁𝗲𝗺𝗲𝗻𝘁𝘀 – Show what you did and what it achieved. ✔ 𝗤𝘂𝗮𝗻𝘁𝗶𝗳𝗶𝗮𝗯𝗹𝗲 𝗿𝗲𝘀𝘂𝗹𝘁𝘀 – Numbers speak louder than words (e.g., “Improved load time by 40%”). But here is a catch add those metrics only which you can justify in the interview. ✔ 𝗥𝗲𝗹𝗲𝘃𝗮𝗻𝘁 𝗸𝗲𝘆𝘄𝗼𝗿𝗱𝘀 – Help it pass ATS filters. ✔ 𝗖𝗹𝗮𝗿𝗶𝘁𝘆 & 𝗿𝗲𝗮𝗱𝗮𝗯𝗶𝗹𝗶𝘁𝘆 – Clean formatting, easy to scan in seconds. ✔ 𝗡𝗼 𝗳𝗹𝘂𝗳𝗳 – Every word should earn its place. At this stage, I don’t yet know if I have cleared the HackerRank assessment — but getting my resume shortlisted by Uber itself is a milestone I’m proud of. 🚀 This isn’t the finish line, but it’s proof that skills, impact, and a well-told story can open doors to incredible opportunities. If you’re working on your resume right now — don’t just list your skills. Make it a story worth reading which should show about your skills📄✨ #Uber #SDE1 #CareerJourney #MERNStack #NextJS #ResumeTips #SoftwareEngineering #DSA

I’m happy to share that I’m starting a new position as Associate Software Engineer at ADROSONIC!

🚀 𝗛𝗼𝘄 𝗜 𝗠𝗮𝗱𝗲 𝗠𝘆 𝗥𝗲𝘀𝘂𝗺𝗲 𝗔𝗧𝗦-𝗙𝗿𝗶𝗲𝗻𝗱𝗹𝘆 (𝗮𝗻𝗱 𝗦𝘁𝗮𝗻𝗱 𝗢𝘂𝘁 𝗙𝗿𝗼𝗺 𝘁𝗵𝗲 𝗖𝗿𝗼𝘄𝗱) Yesterday I got so many messages asking about my resume, ATS score, templates I use for my resume. So I am gonna answer most of the questions in this post if you guys are having more questions then you can ask it in my comment section or connect with me. In today’s hiring process, your resume is often first read by a machine (ATS – Applicant Tracking System) before a recruiter even sees it. That means your resume should not only be well-designed for humans but also optimized for ATS parsing. Here’s what worked for me: ✅ 𝗛𝗼𝘄 𝘁𝗼 𝗠𝗮𝗸𝗲 𝗬𝗼𝘂𝗿 𝗥𝗲𝘀𝘂𝗺𝗲 𝗔𝗧𝗦-𝗙𝗿𝗶𝗲𝗻𝗱𝗹𝘆 1. Use a simple, clean template (no fancy graphics or two-column designs that confuse ATS). 2. Stick to standard fonts like Arial, Calibri, or Times New Roman. 3.Use clear section headings: Education, Experience, Projects, Skills, Achievements. 📄 𝗧𝗵𝗲 𝗧𝗲𝗺𝗽𝗹𝗮𝘁𝗲 𝗜 𝗖𝗵𝗼𝘀𝗲 I went with a single-column ATS-approved template from Overleaf (LaTex) and the template is something like Jake's anonymous you can check it out on their website. 👉 This gave me a balance of professional design + ATS readability. 💡 𝗣𝗿𝗼𝗷𝗲𝗰𝘁𝘀 𝘁𝗼 𝗔𝗱𝗱 𝘁𝗼 𝗬𝗼𝘂𝗿 𝗥𝗲𝘀𝘂𝗺𝗲 Your resume should show not just what you’ve studied, but what you’ve built. I included: 1. Projects that align with the role (e.g., for Software Engineer – MERN stack apps, system design, real-time features). 2. Impact-driven descriptions (not just “built a website,” but “developed a real-time collaboration tool with 30+ users using Liveblocks and golang concurrency support”). 3. Internships / Open Source Contributions that highlight collaboration and industry practices. 🔍 𝗧𝗼𝗼𝗹𝘀 𝗜 𝗨𝘀𝗲𝗱 𝘁𝗼 𝗖𝗵𝗲𝗰𝗸 𝗠𝘆 𝗔𝗧𝗦 𝗦𝗰𝗼𝗿𝗲 Before sending my resume, I ran it through: Jobscan.co – Matches resume with job description. Resumeworded.com – Gives ATS & recruiter-friendly score. SkillSyncer.com – Analyzes missing keywords. 🌟 𝗛𝗼𝘄 𝗠𝘆 𝗥𝗲𝘀𝘂𝗺𝗲 𝗦𝘁𝗼𝗼𝗱 𝗢𝘂𝘁 I kept it one-page, impact-driven, and keyword-optimized. Focused on skills + projects + achievements instead of just listing coursework. Highlighted metrics & outcomes wherever possible (e.g., “reduced API latency by 40%” instead of “worked on APIs”). But most of the time ignore it just because I can't justify it right now so just try to add those metrics which you can justify in your interview. And last but not the least it's your resume treat it as your very first product and sell it to the recruiters with the same mind set. So now I think I have answered all the question that might have occured in your mind. See you guys in next post till then good bye. and also I haven't checked the score of my resume for some months so pls don't comment If it will be getting a little low score