Asklemmy

43947 readers

766 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!

Open-ended question
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.
Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
Not ad nauseam inducing: please make sure it is a question that would be new to most members
An actual topic of discussion

Looking for support?

Looking for a community?

Lemmyverse: community search
sub.rehab: maps old subreddits to fediverse options, marks official as such
[email protected]: a community for finding communities

~Icon~ ~by~ ~@Double_[email protected]~

founded 5 years ago

MODERATORS

[email protected]

3181

What is the biggest lesson that employment has taught you? (lemmy.ml)

submitted 1 year ago by [email protected] to c/[email protected]

593 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 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