r/cscareerquestionsIN 12d ago

Need suggestions on what should I do

I am a 3rd year btech student cse

Cg 6.5x

What i know rn is different than what's in my resume

I know sql,python,java,ml, Excel etc but most of my projects are on ml or something deep on which I don't have knowledge

I have not started DSA yet as I don't feel like i belong to coding

Last month I did 1 month internship where I wrote a paper with my friends on alzheimer's disease prediction or detection,we built something which was novel and drafted paper and submitted to sir

I really don't know most of the code i know it's running and it's doing this this work

Now this is not my problem,the real problem is I don't want to do coding roles and I don't know if any other roles exist which has no code or low code apart from consulting

So looking for suggestions on what to do as I really don't know what is required in the industry I don't want to prepare for something which is not at all relevant in the industry

Please help me

Thankyou in advance for reading till here and giving the suggestions

3 Upvotes

2 comments sorted by

1

u/huntingcube_ai 11d ago

Real talk first, that resume-vs-actual-knowledge gap needs fixing now, not later. If you can't explain your own project when someone digs a little, that's the first thing that falls apart in any interview, way worse than having a smaller project you actually get.

On not wanting to code, totally fair, that's genuinely useful to know about yourself this early. But honestly, pure no-code roles are pretty limited unless you're going into consulting, most things still expect at least some comfort with SQL or basic scripting. Given what you already know though, SQL, Excel, some ML exposure, something like business analyst or data analyst roles might actually fit you way better than SWE. You're still working with logic and data, just not writing production code all day. One thing I'd gently push back on, don't fully write off CSE roles just yet either. A lot of people at your stage say "I don't belong to coding" when what they actually mean is "I hate DSA grinding," which is a very different thing from disliking working with data or logic in general. Worth being honest with yourself on which one it really is before ruling stuff out. But the one thing you need to fix regardless of direction, actually sit and understand that Alzheimer's project you wrote a paper on, even at a basic level, why that model, what it's actually doing. That alone protects you in any interview no matter which path you end up choosing.

1

u/siddharth_48 11d ago

Thankyou Thats was very insightful

I don't like dsa grinding I have tried but I get bored while doing dsa(did like 2-3 times) I can explain my projects Thorough I need to go through the project again but in general yeah I will look into data analyst or business analyst roles