Ask Lemmy

Focus on university course over "private certication" which are often full of bullshit and paid by companies anyway. The foundation you learn is what stays valid no matter what's the technique you use.

To give a word on agile, it's about having shorter development cycles and more intermediate release which are used by actual users. It works well in prototyping phase (when you have proper tools) and in software. However, many PM end-up making agile heavier more complicated/heavy than regular cycle with daily stand-up meeting and boards full of post-it. I would advise going in these type of projects without some technical background.

Also note that while project management looks cool (and is a way to grow your carrer quickly) it's a field where you deal with a lot of bullshit out of your control. A person is sick for the week ? How do your re-organize the project ? A truck delivering a critical part has an accident ? How do you deal with it The certification lab asks finds that your cable at the European fire safety norm but not the US ones (or the other way around ? ) adding two month delay to change everything ? How do you announce the customer that the final delivery is postponed due to some paperwork ? You often end-up sitting between the engineer knowing what needs to be done, the upper management cutting down the budget and the customer wanting more. So not a job for everyone

No one has replied so I will give it a go, but take it with a grain of salt as I'm no expert.

The first thing that stands out to me is that you're in India. India exports a lot of remote work to other countries, but I am not clear on how to get into this if that's what you are interested in. There is a good chance that what works in my country is not what works for yours.

However, I think there are a few key things that probably apply.

First, qualifications are what you use to get a job. The skills you need to do the job you will learn on the job. No qualification can replace experience, so I would suggest you try to get into a (relevant) job as soon as you can. Look at entry level jobs for people with your degree, and look at what they are asking for in the job description. Remember they will ask for everything they want but in most cases their perfect person doesn't exist so you only need to meet 50-70% of what they are asking for. If you have 50% I'd apply. Entry level jobs are tough competition so be prepared to apply for a lot of jobs to get an interview, and make sure you prepare for the interview (think about what questions they will ask, and come prepared with answers - ones that can be easily tweaked to fit different questions because they aren't going to ask exactly what you prepare). It can also help to do a practice interview with a friend, have them ask the questions and you give answers as if you are in a real interview.

Education isn't a step that happens before you get a job, it's something you will continue through your career, so don't think you need to get the certifications first and then get a job. Get a job as soon as you have the CV that lets you get one, then continue on the smaller certifications based on what you feel you are missing. The job ads will also help you decide on further qualifications. If you're having trouble getting interviews, look at what is commonly listed as a wanted certification in different job ads, and start working towards one of them. Keep applying for jobs, put "Currently working towards X certification" in your CV if it's relevant to the job.

If you are getting interviews but aren't getting the job, then the issue is not your qualifications. Interviewing is a skill, the more you do it the better you will get. I also like to recommend people apply for jobs with multiple roles going, if you can. That way you don't have to be the best candidate, just second or third best.

Networking is also underrated. Make friends with people in your classes, keep in contact after you graduate. Learn what jobs they get, and ask for advice on getting in. Ask if their workplace has any jobs going.

I'm hoping this advice is generic enough but you will have a better idea of how things work in India, and if you don't, make friends with those wanting to work in the same areas you're interested in and ask their advice.

Agile is a critical one. I'm a data analyst and a data engineer (I do a bit of both) but most of my work is in the Microsoft stack. There are loads of certificates to get from Microsoft, like the AZ-900, DP-900, DP-600 if you're interested in Fabric.

But for the Agile thing, consider traditional project development as a straight line. There is a start and an end. Agile projects look like an input line into loads of loops. These loops are called 'sprints'. In a sprint, every developer takes ownership of work items and by the end of the sprint, they are finished. If not, they need to be refined or they are taken into the next sprint. There's will be someone who guards the process, there is someone who knows what they want but there isn't really a project leader.

If you're interested in doing agile projects at large companies, you'll likely go from developing to implementing straight into maintaining the environment. Look into DevOps. It's the future of project development, especially in IT.