this post was submitted on 21 Aug 2023
3148 points (98.3% liked)

Asklemmy

43856 readers
1690 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy ๐Ÿ”

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] Kecessa@sh.itjust.works 8 points 1 year ago (1 children)

How long do you work for the same employer though? What field are you in?

I've worked for the same employer for 12 years and never got a promotion because there was only one way up and a pool of over 1000 employees to pick from, then switched to another job and got a promotion under a year...

[โ€“] ipkpjersi@lemmy.ml 3 points 1 year ago* (last edited 1 year ago) (2 children)

Around 3 years per employer, so it's a bit on the shorter end, but not too far from the average for my field.

I'm a programmer. Not a ton of competition per team, especially when I usually work on smaller teams.

[โ€“] Kecessa@sh.itjust.works 3 points 1 year ago* (last edited 1 year ago) (1 children)

Oh yeah if you're "just" a programmer (in the sense that you don't have other formations) you might have to do management courses on the side, that's what my friend had to do to land a permanent promotion...

[โ€“] ipkpjersi@lemmy.ml 3 points 1 year ago

It's true management would likely get me promoted faster but honestly I always wanna stick with the programming side of things. As I get more experienced I will keep getting larger salary bumps, but it's almost definitely not gonna be from promotions but rather from switching jobs lol

[โ€“] electrogamerman@lemmy.world 2 points 1 year ago (2 children)

May I ask, what is the most important thing to show in a programmer CV?

Im a junior programmer. I would say im good at the job. I can easily create new software and also find problems in other codes and fix them. However I have no idea what I would say in an interview. Its not like I learn code by memory.

[โ€“] ipkpjersi@lemmy.ml 4 points 1 year ago

Unfortunately in your case, the most important thing is experience. You just need the years for employers to want to hire you, and with this year in particular, the competition for jobs is insane because of all the layoffs. Make some cool personal projects, that sort of thing can help.

[โ€“] raze2012@kbin.social 1 points 1 year ago

in rough order of important:

  • experience
  • personal projects or project you contribute to (e.g. a decent sized code base in Github). if you're early on, this can be school projects.
  • ability to answer programming concepts in an interview settings
  • school/grade prestige.

I have no idea what I would say in an interview.

if you have no previous job, then yea. It's rough. The first job is always rough, and even in software that's no exception. You will want to talk about decisions and features you worked on in personal projects for that stuff. And of course, really nail down your fundamentals; they really drill you with those interview questions as a junior.

If you have a job, then talk about that. Maybe there's some NDA, but you can talk about some problem in general terms and what you needed to do to solve it. You're not expected to do anything crazy as a junior, so your answer relies more on you knowing how to work in a team than novel architectual decisions.


Personal example: my first job was at a small game studio and my non-BS answer would be that I simply did bug fixes for a game. Nothing fancy, probably something an intern can do.

But interview spin: doing those bug fixes

  • helped me learn about Unity's UI system, I can talk about specific details if the interviewer cares (and don't feel too bad if they don't. Even a super experienced engineer won't be able to talk about every sub-topic of an industry)
  • I talk about where I encountered decisions and when I talked to my lead about what to do. e.g. One bug ended up coming from code that another studio owned. While it was a one line fix, I reported it to a lead who would then create an issue to pass on to that studio. Frustrating, but it shows you understand the business politics of the job, something school can't teach.
  • I never did it at that first job, but there were moments where deadlines get moved forward, and you think of a compromise for a feature due to the lack of time . That shows your ability to identify the Minimum Viable Product and to understand the problem, both the bad and good ways to solve something (sadly. in games you may have to hack solutions quite often)

Best of luck