What I want in my job?

By -

Maybe, I am different, but modern style of IT recruiting is not what I want. Sometimes I think I am not a programmer, but a baby who looking fun.

What is on job offers?

I read a lot of offers. The requirements are more or less the same. The experience in years, English level, know programming language, good communication skill and team player (this is measurable...) and git, Jenkins, sonar or other tools. I often have a problem with these requirements, because when I know programming language or when I know tool? I think I can say I know a tool after watch 1,5 h tutorial, so I can meet a requirement of the job, after one week prepare. Is it correct? Sometimes better is learning new employee that tool. This consumes only the first week of work.

Job description is similar on all offers. Thinking, doing and contact with people. I think this all. Sometimes I think an employer looking people who do everything.

Benefits are cash, Multisport, private health care, playstation, foosball, a young dynamic team, a lot of fun events.

I think the template of offers is abused.

What I want?

I start from benefit. I would like having a chance to work with experts. This is the best benefit for me. I prefer to talk with experts 15 minutes, then play on playstation one hour. The young, dynamic team is often disadvantageous. Why? Young people don't have experience, they want a lot of things and this is bad for a project. I would like to have a team with people who have a different experience. The fun events are good, when I can go with family. The job is only job and after it I have a time for family, so this is not a benefit if the my requirement is not passed. The next benefit, which I like, is taking care about employee improvement. This is the thing which let me think that the employer will want me in the future and invest in me. The last of benefits I want a good tools (like IntellJ) for working and good laptop or computer, why? Because these things improve my speed of working, so I can do a lot of things faster.

I would like to know what I really will do on the new job. If you need a person, who will click one button every day, add this to your offer. I know that offer will be unattractive, but when I will get that job and it is worse than I think, I will leave it. You waste my time and your time. I think this is the worst way. Of course I get a lot of information during recruiting, but I still waste my time, when I get this information too late.

For requirements I don't have advice. I think this is a very unusable piece of offer. Why? Because description of job should give me an information about what I will do and after it, I can assess whether I will do it.

Summary

I know, I don't change the world, but I hope that one person changes something in their job offers and it will be more usable.

Comments

Post a Comment

Popular posts from this blog

Why TDD is bad practice?

By -
Image
Did you listen that TDD is bad? What do you think about it? I have my opinion about it! TDD is bad because... We don't have time to write tests first - I think this is a good point. I sometimes don't have time for that. Why? Because I need to do quickly fix on our code and deploy it. In this case I don't have time to create test after wrote production code too. The even worse case is when we have tested this part of our code and test after change doesn't work. I don't like this, because I must read tests and thinking about repair tests for new logic. I really don't like this. I would like to create new test and remove old every time when I have that situation. What's wrong with the test first on this case? Nothing, because if you have time to write tests after create code, you have time to create test before it. Don't you think so? We know how will implement it, but we don't know how testing it - I think a lot of developers have this problem,
Read more >>

My mistakes in working with legacy code

By -
Image
Hi everyone. A little bit time before, I have to work with legacy code. I need to extract the two from a lot of functionality. Of course the other functionality can work too. I need only change the way how it works and replace a kind of connection to database, servers and other applications. I made a mistake and I want to share my conclusion for it. How will I do it today? I will get a knowledge. I will get the use cases. I will validate the knowledge with the code and the use cases. I will change only fragment of code, where I must change. The end. Why? Get a knowledge I started from getting a knowledge from my colleague. I ask a lot of questions, get information about core functionality and what they want. If you worked with legacy project you know that knowledge is very poor. My first mistake was I didn't verify that knowledge in the code. I started working with code and three days later I got the blocker. I couldn't do it like I wanted, so next time I will try t
Read more >>

How correctly imitate dependencies?

By -
Image
This is continuous of my previous post about why we should imitate our dependencies. I did it not long ago. I though about how do it properly and when I can say that it is correct. Start from test and real dependencies I am starting from the tests. I wrote the simple tests which, I though, are correct. That was my learned about dependencies. I had the good situation that I had some prepared tests before. During the writing test I got a knowledge. A lot of time, I verified what the system return. After it, I got the full automated tests for my dependency. Now, I am sure that dependency works like I think. Like my test use it. I think this is a very good advantage. Extract the interface for communicating The implementation to communicate is implemented and tested. Our test, if you implement it like functionality test, not code test, should show us, how we want to use our dependency. We know what parameters we use, what methods. We know what we want. That is a place where we must extr
Read more >>