Sumit Mukherjee

1.8K posts

Sumit Mukherjee banner
Sumit Mukherjee

Sumit Mukherjee

@sumit_codes_

I'll help you get better paying job opportunities

Присоединился Nisan 2026
591 Подписки696 Подписчики
Закреплённый твит
Sumit Mukherjee
Sumit Mukherjee@sumit_codes_·
Hey everyone! I'm Sumit. I'm a data engineer who writes content about data engineering and career growth. I help people get into data engineering and tech roles through my mentorship sessions. If you're into data engineering or tech industry, we'll get along. Nice to meet you!
English
9
0
33
3.7K
Sumit Mukherjee
Sumit Mukherjee@sumit_codes_·
The worst they can say is no. They will not rescind the offer because you asked. That's a myth told by employers who don't want to pay more. If they say no, you can still accept the original offer. You've lost nothing. You've gained the knowledge that you advocated for yourself.
English
0
0
2
31
Sumit Mukherjee
Sumit Mukherjee@sumit_codes_·
What to say when you counter. "Thank you for the offer. I'm very excited about the team and the work. Based on my research and the value I believe I can bring, I'd be more comfortable at ₹14 LPA. Is that something you can make work?" Polite. Not a demand. An invitation.
English
1
0
1
33
Sumit Mukherjee
Sumit Mukherjee@sumit_codes_·
Don't just negotiate salary. Negotiate the full package. Joining bonus. Relocation. Work-from-home stipend. Learning budget. Stock options. Sometimes salary is fixed but these other levers are flexible. A ₹50K joining bonus is still ₹50K. Take it.
English
1
0
1
30
Sumit Mukherjee
Sumit Mukherjee@sumit_codes_·
Research market rates. Glassdoor. AmbitionBox, etc. Ask people in your network. Know the range for your city, your experience level, your skill set. If the offer is below market, you have data, not just feelings.
English
1
0
0
23
Sumit Mukherjee
Sumit Mukherjee@sumit_codes_·
You got an offer. Congratulations. Now comes the part where most career switchers leave ₹2-3 lakhs on the table because they're afraid to negotiate. Let me teach you how to negotiate your first data engineering salary without burning the offer.
English
1
0
0
104
Sumit Mukherjee
Sumit Mukherjee@sumit_codes_·
When you get the offer, thank them. Express genuine excitement about the role. Then say: "I'd like to take a day to review the full package. When can I get back to you?" Never negotiate in the moment. Buy yourself 24 hours. Use those 24 hours to prepare.
English
1
0
0
24
Sumit Mukherjee
Sumit Mukherjee@sumit_codes_·
Before you get the offer, do not give a number first. When they ask your expected salary, say: "I'm focused on finding the right role. I'd love to hear what range you have budgeted for this position." Their anchor is almost always higher than what you would have said.
English
1
0
1
48
Sumit Mukherjee
Sumit Mukherjee@sumit_codes_·
The most important thing to understand: the first number they offer is never their best number. It's an anchor. They expect you to counter. If you accept the first number without negotiating, you just told them they could have paid you less.
English
1
0
0
56
Sumit Mukherjee
Sumit Mukherjee@sumit_codes_·
Day 1 of tagging @davidgoggins till he reposts this tweet
Sumit Mukherjee@sumit_codes_

I read both of David Goggins' books. Here's what stayed with me. Goggins didn't teach me to run ultras. He taught me that the voice in your head that says "you're not smart enough for data engineering" is the same voice that told him he'd never walk again. It's a liar. Both times He calls it the "governor" - the internal mechanism that pulls you back to safety before you hit your actual limit. I hit mine in month two of learning SQL. Joins broke my brain. I almost quit. The governor said: "You're from a non-tech background. This isn't for you." Goggins taught me to name that voice, then ignore it. The other thing: callousing the mind. You don't wake up tough. You earn it through repetition. One shitty day. One failed query. One rejection. Then another. Then another. Each one adds a layer. My first data engineering interview was a disaster. The second was bad. The third was less bad. The fourth got me an offer. I didn't get better at interviews. I got calloused to the discomfort of not knowing everything. The most underrated lesson from both books: accountability is self-inflicted. Nobody cares about your dreams. Not your friends, not your family, not the hiring manager. Goggins didn't wait for permission to fix his life. He did the work at 4 AM when nobody was watching. I built my first real pipeline at 5 AM. Nobody clapped. Nobody retweeted. That's the work. That's what moves the needle. Two books. One message that rewired me: the only way out is through. Stay hard.

English
0
0
1
92
Sumit Mukherjee
Sumit Mukherjee@sumit_codes_·
I read both of David Goggins' books. Here's what stayed with me. Goggins didn't teach me to run ultras. He taught me that the voice in your head that says "you're not smart enough for data engineering" is the same voice that told him he'd never walk again. It's a liar. Both times He calls it the "governor" - the internal mechanism that pulls you back to safety before you hit your actual limit. I hit mine in month two of learning SQL. Joins broke my brain. I almost quit. The governor said: "You're from a non-tech background. This isn't for you." Goggins taught me to name that voice, then ignore it. The other thing: callousing the mind. You don't wake up tough. You earn it through repetition. One shitty day. One failed query. One rejection. Then another. Then another. Each one adds a layer. My first data engineering interview was a disaster. The second was bad. The third was less bad. The fourth got me an offer. I didn't get better at interviews. I got calloused to the discomfort of not knowing everything. The most underrated lesson from both books: accountability is self-inflicted. Nobody cares about your dreams. Not your friends, not your family, not the hiring manager. Goggins didn't wait for permission to fix his life. He did the work at 4 AM when nobody was watching. I built my first real pipeline at 5 AM. Nobody clapped. Nobody retweeted. That's the work. That's what moves the needle. Two books. One message that rewired me: the only way out is through. Stay hard.
English
0
1
4
271
Pri
Pri@Alwayspriyesh·
June 6/30 🚀 Today was all about building. ✅ Spent the day working on a project and completed it in 2 days. 🚀 Launching it tomorrow. • Learned more about X growth strategies • Wrote content for X • Continued documenting my journey Growth: 📈 +76 followers 📉 -6 unfollows Lesson of the day: "Consistency compounds. Small actions repeated daily create big results." Thank you to everyone supporting the journey. More exciting things coming tomorrow. 👀 #BuildInPublic
Pri@Alwayspriyesh

June 5/30 🚀 Learning: • Anomaly Detection Algorithm • Developing & Evaluating Anomaly Detection • Choosing the Threshold (ε) • Computational Considerations • Quiz Passed ✅ Growth: •+80 followers 📈 and -9 unfollow 📉 Other: • Premiere Pro Tutorials 🎬 • Read a few pages 📖 Lesson of the day: "People crave appreciation more than criticism. Make others feel valued." Let's keep learning and growing together. 🚀 #BuildInPublic

English
3
0
16
396
Sumit Mukherjee
Sumit Mukherjee@sumit_codes_·
Stop measuring yourself against strangers on the internet. Start measuring yourself against who you were yesterday. That's the only scoreboard that counts.
English
0
0
2
108
Sumit Mukherjee
Sumit Mukherjee@sumit_codes_·
Nobody is going to build your pipeline for you. Nobody is going to write your SQL for you. Nobody is going to ship your project, debug your errors, or decide you're ready except you.
English
1
0
1
104
Sumit Mukherjee
Sumit Mukherjee@sumit_codes_·
There's someone on your timeline who just landed a data engineering role in 3 months. Someone else built a killer pipeline project over the weekend. Someone posted their 30 LPA offer letter and you stared at it for way too long. Close the app.
English
3
4
64
2.8K