TechWithSaumya

Hey everyone! ❤️ I’m starting a beautiful new chapter of my life—I’m married! 💍✨ While this journey was personal, your love and support have always meant a lot to me. Excited to continue creating and growing with you all! 🎥💖

#NewBeginnings #JustMarried

2 months ago | [YT] | 155

TechWithSaumya

Feeling Like a "Loser" at ₹50,000 a Month? Let’s Talk Reality

One of my Instagram followers reached out recently.

They felt like a loser for earning ₹50,000 a month.

I was surprised.

How could someone feel this way so early in their career?

Social media has glamorized huge salaries.

It’s creating unrealistic expectations for many.

Yes, it’s important to aim high and grow.

But constantly comparing yourself can harm your mental health.

Even with ₹40,000, you can live comfortably in a Tier-1 city.

Savings might be limited, but it’s manageable.

In software engineering, salaries often grow significantly over time.

So, focus on your personal growth instead of comparisons.

𝐂𝐨𝐧𝐬𝐢𝐝𝐞𝐫 𝐜𝐨𝐧𝐧𝐞𝐜𝐭𝐢𝐧𝐠 𝐡𝐞𝐫𝐞 𝐟𝐨𝐫 𝐭𝐞𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭: lnkd.in/gdkjU7TT

2 months ago | [YT] | 87

TechWithSaumya

The hard truth about high salaries in India:

Switching jobs is often the only way.

It can be risky, but the payoff can be massive.

If you're not being paid what you deserve, you have two choices: accept being underpaid or step up and seek the pay you deserve.

Most companies don't acknowledge or reward high performers.

But you deserve better.

You have a choice.

Stay somewhere where you're undervalued, or take the risk and find somewhere that recognises your worth.

"Overthinking" won't help.

But changing your situation will.

So take the leap. Seek a better salary, better opportunities, and a better life.

2 months ago | [YT] | 105

TechWithSaumya

𝗡𝗼 𝗼𝗻𝗲 𝘁𝗮𝗹𝗸𝘀 𝗮𝗯𝗼𝘂𝘁 𝘁𝗵𝗲 𝗵𝗮𝗿𝗱𝗲𝘀𝘁 𝗽𝗮𝗿𝘁 𝗼𝗳 𝘀𝘄𝗶𝘁𝗰𝗵𝗶𝗻𝗴 𝗷𝗼𝗯𝘀…

It’s not the interviews. It’s the waiting, the rejections, and the self-doubt.

I remember when I started looking for a better opportunity—fixing my resume, applying everywhere, preparing for interviews.

But what no one prepared me for was how mentally exhausting the process would be.

Week 1: Sent out multiple applications. No response. My LinkedIn is filled with “Excited to share…” posts. I tell myself, “It’s just the start.”

Week 3: A recruiter from a dream company reaches out! The interview goes well… but days pass, and I hear nothing. Anxiety kicks in.

Week 5: Another rejection. I refresh my inbox, hoping for a different email. But it never comes.

That’s the part no one tells you.

𝘑𝘰𝘣 𝘩𝘶𝘯𝘵𝘪𝘯𝘨 𝘵𝘦𝘴𝘵𝘴 𝘺𝘰𝘶𝘳 𝘱𝘢𝘵𝘪𝘦𝘯𝘤𝘦. 𝘠𝘰𝘶 𝘯𝘦𝘦𝘥 𝘵𝘰 𝘬𝘦𝘦𝘱 𝘨𝘰𝘪𝘯𝘨 𝘦𝘷𝘦𝘯 𝘸𝘩𝘦𝘯 𝘪𝘵 𝘧𝘦𝘦𝘭𝘴 𝘭𝘪𝘬𝘦 𝘯𝘰𝘵𝘩𝘪𝘯𝘨 𝘪𝘴 𝘸𝘰𝘳𝘬𝘪𝘯𝘨.

𝐂𝐨𝐧𝐬𝐢𝐝𝐞𝐫 𝐜𝐨𝐧𝐧𝐞𝐜𝐭𝐢𝐧𝐠 𝐡𝐞𝐫𝐞 𝐟𝐨𝐫 𝐭𝐞𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭: lnkd.in/gdkjU7TT

2 months ago | [YT] | 73

TechWithSaumya

❌ Stop rushing to learn everything
❌ Stop random DSA practice
❌ Stop tutorial hopping
❌ Stop copying others' paths
❌ Stop comparing timelines

Here's what actually works for tech interviews:

🎯 The Strategic 6-Month Roadmap:

Phase 1 (Weeks 1-4):
- Master fundamentals first
- Focus on arrays & strings
- Build problem-solving mindset

Phase 2 (Weeks 5-8):
- Core DSA concepts
- Trees & basic graphs
- Pattern recognition

Phase 3 (Weeks 9-12):
- Advanced algorithms
- Graph problems
- Dynamic programming basics

Phase 4 (Weeks 13-16):
- Complex problem patterns
- System design introduction
- Mock interviews start

Phase 5 (Weeks 17-24):
- Specialization phase
- Project building
- Interview preparation

💡 Key Success Factors:
- Consistency over intensity
- Quality practice > quantity
- Understanding > memorization
- Building > consuming

Remember: Everyone's journey is different. Trust the process.

4 months ago | [YT] | 115

TechWithSaumya

❌ Don’t join TCS
❌ Don’t join Wipro
❌ Don’t join Infosys
❌ Don’t join Accenture
❌ Don’t join Cognizant

You’ve probably heard this before, but here’s the truth: your career is in your hands.

These companies may not pay the most, but they offer:
✔️ Strong project management skills
✔️ Collaboration and teamwork experience
✔️ Effective communication and adaptability

Many professionals have started here, upskilled, and moved on to bigger opportunities.

Having an offer is better than no offer. Don’t let it slip away.

It’s not where you start—it’s how you grow. 🌟

𝐂𝐨𝐧𝐬𝐢𝐝𝐞𝐫 𝐜𝐨𝐧𝐧𝐞𝐜𝐭𝐢𝐧𝐠 𝐡𝐞𝐫𝐞 𝐟𝐨𝐫 𝐭𝐞𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭: lnkd.in/gdkjU7TT

4 months ago | [YT] | 69

TechWithSaumya

Happy New Year 🥳♥️

May every goal you set this year come with the determination to achieve it 🙌

4 months ago | [YT] | 81

TechWithSaumya

❌ Don’t join TCS
❌ Don’t join Wipro
❌ Don’t join Infosys
❌ Don’t join Accenture
❌ Don’t join Cognizant

You’ve probably heard this before, but here’s the truth: your career is in your hands.

These companies may not pay the most, but they offer:
✔️ Strong project management skills
✔️ Collaboration and teamwork experience
✔️ Effective communication and adaptability

Many professionals have started here, upskilled, and moved on to bigger opportunities.

Having an offer is better than no offer. Don’t let it slip away.

It’s not where you start—it’s how you grow. 🌟

5 months ago | [YT] | 131

TechWithSaumya

💔 What’s the biggest lesson failure has taught you?

For me, failures have been my greatest teacher. Each rejection, missed opportunity, or wrong turn brought clarity and strength I didn’t know I had.

Here’s what I’ve learned from my journey:

1️⃣ Rejection is Redirection
Every “NO” I heard wasn’t the end—it was a nudge toward something better. Those rejections opened doors I didn’t even know existed.

2️⃣ Growth Requires Discomfort
I failed interviews because I didn’t adapt to the latest tech trends. It taught me that comfort zones are career traps. Keep learning, keep growing.

3️⃣ Consistency Wins the Race
Talent helps, but showing up every day and doing the work is what takes you to the finish line.

4️⃣ Diversify Your Skills
Relying on one skill or job can be risky. Exploring side projects and upskilling has been my safety net.

Failures don’t define us—they refine us. Every setback is a step forward if you’re willing to learn.

Your Turn:
What has failure taught you? Drop your lessons in the comments 👇

6 months ago | [YT] | 26

TechWithSaumya

Is the time complexity of this code snippet always O(n)?

At first glance, it looks like this code should have a time complexity of O(n), where n is the size of the list. But there's a catch! The actual complexity depends on the type of List used.

💡 Case 1: ArrayList
- Time Complexity: O(n)

In an ArrayList, the get(i) operation is O(1) because ArrayLists store elements in a contiguous memory block. So, accessing any element by index is quick.

Thus, looping through n elements where each access takes O(1) results in an overall time complexity of O(n).

💡 Case 2: LinkedList
- Time Complexity: O(n²)

In a LinkedList, things are a bit slower. The get(i) method is O(i) because LinkedLists are not stored contiguously. The list has to traverse from the start to reach the i-th element, and this traversal takes O(i) time.

As a result, the first iteration takes O(1), the second O(2), and so on, until the last iteration takes O(n). Summing these up gives us a total complexity of O(n²).

📝 Conclusion:
ArrayList: O(n)
LinkedList: O(n²)

𝐂𝐨𝐧𝐬𝐢𝐝𝐞𝐫 𝐜𝐨𝐧𝐧𝐞𝐜𝐭𝐢𝐧𝐠 𝐡𝐞𝐫𝐞 𝐟𝐨𝐫 𝐭𝐞𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭: lnkd.in/gdkjU7TT

So, the time complexity isn’t always O(n); it depends on which List implementation you're using! 🚀

7 months ago | [YT] | 41