What you'll be working on if they hire you vs what they say you'll be working on if they hire you.

A project using raspberries use in factories was offered to work on when got hired but ended up writing administration software for curtain fabrics.

I found out meanwhile that the rpi project was in bad state, rewrote crucial part in free time and it ended up as my project to work on.

So, I did get at the end what I wanted after some effort

I was told to hire to work on gui. I did.

Then I worked on servers for industrial automation.

Now I am working both.

I don't complain. I get a paycheck. People are nice to me.

I was hired to create/manage CICD

In the end, I also have to do Java development (because nobody in the team can do it)

Now I also volunteer to do Groovy scripting because I am bored (the other dev who can do it is too busy with other assignments)

i was hired to do vb projects and maintain the sql database. in the end i was doing full stack web development again

Should’ve worked on Data-Pipeline design, ERP implementation and integration. I started out with paying back the technical debt some other fuckers gave the clients, but nowadays I’m actually doing what was promised, so yea

Not a big difference. Pretty much the same in most cases

However, how they interview the candidate and what kind of questions they ask the candidate are entirely unnecessary and unrealistic. Like asking someone to build a ticket booking website or sort an unbounded collection when the candidate won't be solving anything close in their projects once hired

Thanks all, this was originally a rant about my personal experience, particularly as I'm now starting to apply for jobs, but turned into a really interesting thread.

I was hired to be a creative corporate desk slave and now I'm a demotivated corporate desk slave

The creativity goes elsewhere now if I can help it

Once was an iOS developer for 4 years. Didn't write a single line of code for iOS.