One thing you should never do at an interview

Never lie in CV

I asked one candidate about technology mentioned in his CV and he did not remember what it is. It is a shame. If it is accidental or intentional it does not matter. It is bad.

Sometimes IT guys make CVs nicer, they list a lot of technologies because HR people just compare buzz words and if you have not right words in CV you cannot pass to next round. That is partly true, but do you really want to work for a such company? Maybe it is reasonable to prefer company with a more technical approach.

I think it is better to be honest and do review of CV with respect of reality. If you have changed one annotation or corrected one xml in a Spring project that does not mean you are a Spring expert or somebody somewhere in application uses a Hibernate does not make also a Hibernate expert from you or you first time compiled a Linux kernel you are definitely not a Linux expert.

Please just think about it and never lie in your CV.

Comments

Senior or Junior

Usually companies call young employees Juniors and more experienced Seniors. Sometimes you need to just sit and wait and it will come. Sooner or later. From my point of view it is not enough. I met a lot of old employees they call themselves Seniors but they behave like Juniors. So I defined my point of view on Seniority: professional simple understand what I am doing and understand reason why I am doing it can coach others this is very basic; who can coach others is just fine but who can coach others to became a new coaches is super not genius but have deep knowledge on some specialized parts geniality is overestimated, we do not need "magical guru", to be expert is good enough; if you are "one to go" when there is problem, it is OK big picture overview it is not probably possible to understand a whole system in details but it is necessary to have at least overview know what I know and know what I do not know to see myself in correct light is very ...

Anti-Lean Quotes

Set of quotes which usually highlights Anti-Lean behavior Create waste instead of Eliminate waste ' Developer who is not working at least on 4 projects is not properly utilized ' - less is definitely more and only done-done work counts by end of the day, limited work in progress is helping to focus on right priorities ' In case of any network issues please create a ticket on the help desk system at our partner's web-page' - creating catch 22 situations by design is craziness, such a process does not make any sense 'Yes, this is what our customers really need but could we add also this small feature, just in the case?' - extra feature creates an extra complexity, it is better to stay focused on real value and make it great for the users ' I know that you are working on the top priority but I am sure that you can do also this small task till noon' - probably there will be nothing really done by noon, task switching is more expensiv...

Agile is not a religion

It is quite annoying to me when argument during discussion is like this: it must be XY because the book says it. It is kind of: Bible is saying XY so we have to follow = end of discussion. I am not very happy in such a case because we probably do not understand principles and just trying to blindly imitate something without deep knowledge of the matter. I prefer to admit it or show personal standpoint.

What to expect from devops

Build smart automation automate everything and everywhere implement clever monitoring in case of a failure automatically fall back into the previous working state Enable continues development give all developers easy and simple way how to do continues development without compromises build support for step-by-step deployment and A/B testing deliver production-like environment runnable on developer's workstation Rule the cloud deeply understand cloud technology code scalable infrastructure for actual and future needs enforce optimal security model Be step ahead always think one step in future about necessary improvements constantly identify bottlenecks and limits of current production system with possible solutions apply agile and lean principles

Agile coaching hints

boring stand-ups typical reason: every team member is solving very different issue, no intersections or direct collaboration; basically "I do not care" about 1 status sentence of my colleagues because there is no connection to my current work + strong individualism possible solution: moving towards to the feature team, e.g. instead of doing 1 feature by 1 developer 6 weeks, try to split work and do it in parallel by 3+ developers with feature lead in 2 weeks or even faster if possible (could be challenging at the beginning but helps to build no siloed knowledge) + build the team too long stand-ups typical reason: too much details + bike-shading and direct follow ups on stand-up with whole team + manager's hijacking possible solution: park every discussion longer than 1 minute after the stand-up and follow up only with committed people (pigs & chickens); 'kill' any bike-shading; have manager's talk after the stand-up non realistic estimations ...

Lubo Drobny

Search This Blog