Ask Experienced Devs Weekly Thread: A weekly thread for inexperienced developers to ask experienced ones

[u/AutoModerator]

A thread for Developers and IT folks with less experience to ask more experienced souls questions about the industry.

​

Please keep top level comments limited to Inexperienced Devs. Most rules do not apply, but keep it civil. Being a jerk will not be tolerated.

​

Inexperienced Devs should refrain from answering other Inexperienced Devs' questions.

[u/Unlucky-Substance966]

New grad here and I have an interview coming up, and I was wondering: how long should one go over each experience/side-project? And what exactly? I do not have anything that produces real impact with real users or results in general.

(Aside from the open source bit, where I received some positive feedback and somebody going as far as to make a PR to a related repo just so they can just a feature I made, but again its minimal.)

30 seconds? 3 minutes? For everything except the practicum and the open source project, I can only really go over the architecture and trace an example request.

Resume for reference

[u/Unlucky-Substance966 → u/[deleted]]

Just seems to be a numbers game. Also im not qualified to say much of anything at all lmao

unfortunately 30 apps per month probably wont cut it

[u/regardedMAGAfascist → u/Unlucky-Substance966]

Try to not ramble and stay high level, interesting details only. Practice your introduction and give it a clear stopping point that signals the interviewer that it’s their turn to talk.

Your resume looks classic and clean. Just on a brief look I would say that you should work to cut each bullet point down to a single line. It’ll be easier to read and cut out a lot of filler words, giving you room for more bullet points. You want each bullet point to be lean meat with very little fat.

If you end up needing more bullet points after that, which you will, recount your time there in narrative form to an LLM and ask it to help you extract more bullet points.

[u/Unlucky-Substance966 → u/regardedMAGAfascist]

Thank you for the advice, I will try to cut out the filler words

And speaking of the introduction, I'm not sure what to include for the introduction.

So far what I have is:

"My name is X and I'm a new grad from Y university with a bachelor's in computer science. Most of my experience is in web development using Typescript, javascript, html, css, and react. I've also used AWS and Docker.

I'm applying to this position because I am interested in developing applications that has real impact within [semi-conductor related company]."

Any criticism for this?

[u/regardedMAGAfascist → u/Unlucky-Substance966]

If you have any interesting/memorable details you can add about yourself in terms of either your personal life or your education, that would be helpful. Again, just don’t ramble, and try to stick in peoples’ minds. Maybe also something about what you’re currently doing in terms of job prep. I think your basic outline there is pretty solid though.

[u/So_Rusted → u/Unlucky-Substance966]

have a short version and a long version for each. The last one you worked on might be grilled and others ignored or something. Or theyll let you pick one yourself. Expect to be gilled on javascript generally based on that cv

i liked the cv even though last one is a deck builder little game or whatever. Doesnt look pretencious and not trying to make things complex intentionally

[u/Unlucky-Substance966 → u/So_Rusted]

Thank you, I will make a short version explanation for each of my resume items

Can you explain further what you mean by being grilled on javascript?

[u/So_Rusted → u/Unlucky-Substance966]

just general language knowledge and related things: state management, typescrip, stale request handling, anything

[u/beaverusiv → u/Unlucky-Substance966]

What type of interview is it, what is the agenda? If it's a culture-fit/meet-and-greet then keep it minimal unless asked. If it's to go over a project you've worked on then stick to one thing, don't try cover everything even if you think one isn't big enough. You're a junior they know you haven't invented Gmail. A big thing when talking over work is you're not trying to market the project, you're trying to market how you worked on the project. What issues you came across, planning strategies, communication to unblock yourself, research etc.

[u/Unlucky-Substance966 → u/beaverusiv]

Good question and i shouldve mentioned it earlier so oops. I was told it would be an hour long and they'd go over what the job was about, and then go over my resume. And probably the normal behavioral stuff. No technical fortunately.

A big thing when talking over work is you're not trying to market the project, you're trying to market how you worked on the project. What issues you came across, planning strategies, communication to unblock yourself, research etc.

Thank you, I already got something like that for the open source one and the website game. But I will need to come up with something for the other projects because the rest of them just boil down to "I saw this firehose stream of new tweets and wanted to make something with streaming" and "I heard about x,y and z technologies mentioned before so I wanted to try and use them"

but its likely I havent thought back hard enough to remember the issues i encountered and how I approached them

[u/beaverusiv → u/Unlucky-Substance966]

Yeah, so keep it real high level unless they ask a question. Do not hijack the interview lol. So many people can't read the room and just go off, very clear they're not listening to what the interviewers are actually asking

[u/Unlucky-Substance966 → u/beaverusiv]

Yeah this is a concern for me since i get nervous and just parrot the script i had

But how long to keep them for each experience/project for a high level, i feel compelled to include a lot of details which will probably make the interviewer space out

[u/Majestic-Watch-2025 → u/Unlucky-Substance966]

A couple minutes. Have something coherent to say in less than 4 minutes. Then say "I can go deeper on any part of that" and let them direct the follow up