Mrinal Raghav’s Post

The other day I saw this post from Zach Wilson asking when is this "Senior-Only Job Market" is going to end. I replied with my thoughts in his post but wanted to share with you as well. What is the "Senior-Only Job Market"? Its the fact that when companies recruit for some "entry-level" jobs now, they are asking for unattainable curriculas from applicants with no experience looking to enter the market. And like I replied on Zach´s post, the worst part is that I believe the seniors-only market has just started. AI has been disrupting jobs for some time now, and as we have seen, it has the potential to cover for several junior functions such as: - drafting summaries, - writing articles, emails - basic coding, basic data wrangling - and pretty much every task that doesn't require much specialization. Then, to contextualize and make the outputs work & useful companies will need mostly specialized/experienced talent. This means that I believe the most impacted jobs in the medium and long term by Artificial Intelligence disruptions will be the junior ones, setting up an entry barrier for new talents to enter the "formal" job market. What do you think?

How do you suggest we tackle this situation Zach Wilson ? There are rarely any junior positions and even if there are they will require 5+ years of experience. I know building projects would help but how will I compare with the experienced individuals? A request to recruiters, to please reconsider our experience when reaching out to us, because it only results in heartbreak if we don’t have the experience you expect and as international students, our time is ticking. #dataengineering

It doesn’t matter if you’re a Data Engineer. It doesn’t matter if you’re a Data Scientist. It doesn’t matter if you’re a Data Analyst. It doesn’t matter which title you own. You still have to … - Handle missing or inconsistent data. - Optimize SQL queries for better performance. - Communicate your findings to non-technical stakeholders. - Integrate data from multiple sources. - Ensure data security and compliance metrics are met Titles change but groundwork remains the same. Agree? Btw, want to join a community of 1000+ like-minded data folks? Comment your email and I’ll send you a link ⬇️

It doesn’t matter if you’re a Data Engineer. It doesn’t matter if you’re a Data Scientist. It doesn’t matter if you’re a Data Analyst. It doesn’t matter which title you own. You still have to … - Handle missing or inconsistent data. - Optimize SQL queries for better performance. - Communicate your findings to non-technical stakeholders. - Integrate data from multiple sources. - Ensure data security and compliance metrics are met Titles change but groundwork remains the same.

In this article, I am going to present the following: - Why is it so hard to get a data engineer job without an IT background? - Five guidelines to get a data engineer job

It doesn’t matter if you’re a Data Engineer. It doesn’t matter if you’re a Data Scientist. It doesn’t matter if you’re a Data Analyst. It doesn’t matter which title you own. You still have to … - Handle missing or inconsistent data. - Optimize SQL queries for better performance. - Communicate your findings to non-technical stakeholders. - Integrate data from multiple sources. - Ensure data security and compliance metrics are met Titles change but groundwork remains the same. Agree? #Dataengineering #Dataanalyst #Datascientist

It doesn’t matter if you’re a Data Engineer. It doesn’t matter if you’re a Data Scientist. It doesn’t matter if you’re a Data Analyst. It doesn’t matter which title you own. You still have to … - Handle missing or inconsistent data. - Optimize SQL queries for better performance. - Communicate your findings to non-technical stakeholders. - Integrate data from multiple sources. - Ensure data security and compliance metrics are met Titles change but groundwork remains the same. #DataScience #DataEngineering #DataAnalysis #DataManagement #DataIntegration #SQLOptimization #DataSecurity #TechCareers #DataProfessionals #DataDriven #DataInsights #Analytics #DataQuality

How to Know if a company is employing you to be a core data engineer/ analyst or looking to make you fulfill both roles Just pay careful attention to the job description. If it's all over the place and overlapping both roles, you have your answer

One of the pain-points I heard from data leaders last year was that it can be hard to justify hiring a data engineer. Hiring a data scientist or analyst is generally easier to sell to the business because their work is immediately tangible. Many data scientists and analysts are also great at building SQL and notebooks workflows that can take data from Data Lakes and process it into a usable format. So why even hire data engineers? This is a question so many companies have run into. The truth is, companies can get away without data engineers for a little bit. But here’s what often happens. 1)Tech-debt starts to build 2) Lots of pipelines and data workflows get set-up for one-off requests 3) No one ever thinks about data governance 4) Even small changes risk breaking multiple critical flows 5) No one wants to own any of the above This has happened time and time again. It eventually comes to a head once the CEO is tired of dealing with conflicting numbers, slow dashboards and the constant "we can't change that, or something might break" responses. If you're that CEO or a data leader who needs to have that conversation with the CEO, then let's talk!

Data Analysts and Data Engineers are data professionals with specific job roles. Watch this video to learn more about the differences between a data analyst and a data engineer. Don't forget to tag an aspiring data professional who should see this ✨✨ #tech #womenintech #cloud #data #dataprofessionals #devopsengineering #techroles #data #datum