39 points

Interview: write an optimized o log something reverse binary linked list quick sort to extract a cake recipe out of an object with an array list of football teams by hand and explain it like it’s the only code you’ve been writing all your life

Job: meetings that could have been e-mails

permalink
report
reply
0 points

Interview: write an optimized o log something reverse binary linked list quick sort to extract a cake recipe out of an object with an array list of football teams by hand and explain it like it’s the only code you’ve been writing all your life

No, because that’s bullshit.

permalink
report
parent
reply
21 points

There are worse mistakes than accepting senior engineer: there’s management.
I’ll give you my IWW card when you pry it from my cold, dead hands.

permalink
report
reply
13 points
*

Yeah, you either work extra hours or you work during the meetings or both or you get de-skilled pretty quickly unless you work open source, second job or personal projects in the non-work hours. Otherwise, you can treat it like BS job but your skills will become BS and you will have to get better at lying and or potentially go into management with that level of experience. RN I’m unemployed and I’d gladly take any position, even if I’m qualified for senior, and I don’t care if I have to work extra hours to keep up and this is coming from someone who has been actively organizing on the job at my last two tech jobs.

permalink
report
reply
1 point

If you’re a senior engineer, then you should have a team of juniors doing most of the coding. Your job is to architect, peer review, meet with stakeholders, etc… At least that has been my experience. Unless you are on one of those small teams with all senior engineers and then you have to do all of the above, and the coding too. I’ve had that experience as well.

permalink
report
parent
reply
1 point
*

If you’re a senior engineer, then you should have a team of juniors doing most of the coding. Your job is to architect, peer review, meet with stakeholders, etc… At least that has been my experience. Unless you are on one of those small teams with all senior engineers and then you have to do all of the above, and the coding too. I’ve had that experience as well.

small team with inexperienced new people that needed a lot of training and we also had “architect” positions and those guys I would never even see or talk to, they were in their own realm somewhere isolated from the actual work. what you are describing was more like the “principal” engineer and we had one of those and he was mostly only doing meetings and occasionally doing some work when the itch struck him sufficiently

permalink
report
parent
reply
13 points

I’ve been a senior engineer ever since I started my career.

The title means nothing.

permalink
report
reply
3 points

In my experience, getting one can be more about politics and fulfilling certain management checkboxes than about technical skill and experience.

permalink
report
parent
reply
3 points

i got it right out of college.

permalink
report
parent
reply
2 points
*
Deleted by creator
permalink
report
parent
reply
1 point

did senior pe engineering help you guess i was a senior software engineer posting in the programming humor community?

permalink
report
parent
reply
4 points

This is precisely why I don’t actively seek promotions. Not only are there very few paths for someone to move up with my skill set, but if I do, I won’t be doing what I enjoy doing anymore. I just want to find the medium where I can make enough to live off of and also just do my work most of the time.

permalink
report
reply

Programmer Humor

!programmerhumor@lemmy.ml

Create post

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

  • Posts must be relevant to programming, programmers, or computer science.
  • No NSFW content.
  • Jokes must be in good taste. No hate speech, bigotry, etc.

Community stats

  • 4

    Monthly active users

  • 755

    Posts

  • 2.2K

    Comments