This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
docs:job_interview_-_candidate_questions:job_interview_-_candidate_questions [2016/06/25 08:55] – note on kung-fu level of the team basz | docs:job_interview_-_candidate_questions:job_interview_-_candidate_questions [2021/03/25 08:31] – some notes emhasising team - who will you work with? basz | ||
---|---|---|---|
Line 7: | Line 7: | ||
- when need to go on-site? | - when need to go on-site? | ||
- how long before getting the feedback? | - how long before getting the feedback? | ||
+ | - how detailed the feedback will be? //crucial in case you fail.// | ||
- **working conditions**: | - **working conditions**: | ||
- where is the office located? //think about getting there and back on a daily basis.// | - where is the office located? //think about getting there and back on a daily basis.// | ||
Line 12: | Line 13: | ||
- open space or separate rooms? //i find open spaces noisy, which makes it impossible to focus on work -- this in turn kills innovation.// | - open space or separate rooms? //i find open spaces noisy, which makes it impossible to focus on work -- this in turn kills innovation.// | ||
- what's the dressing policy? //not everyone' | - what's the dressing policy? //not everyone' | ||
- | - is there obligatory (long) lunch break? //it's annoying when employer tells you when and how long you will be eating lunch. especially when you usually | + | - is there obligatory (long) lunch break? //it's annoying when employer tells you when and how long you will be eating lunch. especially when you often don' |
- ask recruiter "why do YOU like your job?". //nice way of observing if your (potential) future coworker really enjoying work, or "just works here" | - ask recruiter "why do YOU like your job?". //nice way of observing if your (potential) future coworker really enjoying work, or "just works here" | ||
- | - can get support to do any off-time projects? //say: extra money for a hardware, | + | - can get support to do any off-time projects? //say: extra money for a hardware, a spare computation power at night, green light for open-source contribution, |
- have time for writing/ | - have time for writing/ | ||
- have time for preparing conference talks? //some employers support presenting skills of they employees during conferences. this means +1 for your surname and +1 for company' | - have time for preparing conference talks? //some employers support presenting skills of they employees during conferences. this means +1 for your surname and +1 for company' | ||
- who will you work with? seniors/ | - who will you work with? seniors/ | ||
+ | - would you like to work with recruiters you just talked with? //it is of a critical importance to work with with great ppl, that don't get in the way of innovation.// | ||
- **employment**: | - **employment**: | ||
- how much? :) | - how much? :) | ||
Line 24: | Line 26: | ||
- [[wp>tax break]]? | - [[wp>tax break]]? | ||
- is work time flexible? | - is work time flexible? | ||
- | - does work include supports, weekends, night shifts, etc... //your time is grates | + | - does work include supports, weekends, night shifts, etc... //your time is the greatest |
- is work from home possible? how often? | - is work from home possible? how often? | ||
- is part time employment possible? //money are not the top priority -- in a long run, it's all about the time.// | - is part time employment possible? //money are not the top priority -- in a long run, it's all about the time.// | ||
- | - can hire as an external contractor? //this usually avoids few social | + | - can hire as an external contractor? //B2B can be beneficial for taxes and when buying HW.// |
- **trainings**: | - **trainings**: | ||
- does employer ensure trainings? | - does employer ensure trainings? | ||
Line 37: | Line 39: | ||
- development? | - development? | ||
- software architecture? | - software architecture? | ||
- | - CM? //who does configuration management. can it be influenced, if you see field for improvement?// | + | - (S)CM? DevOps? //who does configuration management? can it be influenced, if you see field for improvement?// |
- | - build management? //the same as for CM.// | + | - build management? //the same as for SCM/DevOps.// |
- **project organization**: | - **project organization**: | ||
- | - how to introduce a change/ | + | |
+ | | ||
- how much time is dedicated to finding new solutions and redesigning old ones? //many companies do not actually expect any change to come to their project. if so -- R U N !// | - how much time is dedicated to finding new solutions and redesigning old ones? //many companies do not actually expect any change to come to their project. if so -- R U N !// | ||
- what methodology do you use: SCRUM, RUP, SDLC+, none? //are you sure you want to take part in project which main task is to produce documentation and/or meeting minutes?// | - what methodology do you use: SCRUM, RUP, SDLC+, none? //are you sure you want to take part in project which main task is to produce documentation and/or meeting minutes?// | ||
- | - how do you document project? //there are reasonable limits both ways -- no documentation usually means no architecture and spaghetti code; tones of documentation usually means " | + | - how do you document project? //there are reasonable limits both ways -- no documentation usually means no architecture and spaghetti code; tones of documentation usually means " |
- | - is project local or multi-site? // | + | - is project local or multi-site? // |
- who makes project decisions (which company site/ | - who makes project decisions (which company site/ | ||
- what is the policy is bug is found is open-source library? //it's good to share -- otherwise you'll need to maintain your " | - what is the policy is bug is found is open-source library? //it's good to share -- otherwise you'll need to maintain your " | ||
- | - does company maintain any open-source projects or participate in any? //again - openness for sharing// | + | - does company maintain any open-source projects or participate in any? //again - openness for sharing.// |
- **technologies**: | - **technologies**: | ||
- | - C++14? | + | - C++? (make sure decent standard version is used!) |
- Linux? | - Linux? | ||
- gcc? clang? what versions? | - gcc? clang? what versions? | ||
Line 67: | Line 70: | ||
- what's the code-base size (in [[wp> | - what's the code-base size (in [[wp> | ||
- is continuous integration used? what tools are used to implement it? //CI is standard nowadays. but note, that having build server does NOT equals to having CI.// | - is continuous integration used? what tools are used to implement it? //CI is standard nowadays. but note, that having build server does NOT equals to having CI.// | ||
- | - is continuous delivery used? what tools are used to implement it? //CD is a step towards from CI, needed to minimize human factors. having real CD usually | + | - is continuous delivery used? what tools are used to implement it? //CD is a step towards from CI, needed to minimize human factors. having real CD usually |
- have automated tests? //no automated testing usually means tightly coupled architecture with tons of errors lurking in a code... usually legacy code.// | - have automated tests? //no automated testing usually means tightly coupled architecture with tons of errors lurking in a code... usually legacy code.// | ||
- how many tests are there? | - how many tests are there? | ||
- how many [[wp> | - how many [[wp> | ||
- | - what is code coverage? //though the % does not guarantee anything, | + | - what is code coverage? //though the % does not guarantee anything, |
- what types of tests are implemented (UT, MT, IT, ST)? which are automated, which manual? | - what types of tests are implemented (UT, MT, IT, ST)? which are automated, which manual? | ||
- is there project documentation? | - is there project documentation? | ||
Line 78: | Line 81: | ||
- how this documentation is done? //usually its a good idea to keep it in VCS-friendly format, like LaTeX or asciidoc in the same repo as the code, so that it can be easily updated to track changes in the code.// | - how this documentation is done? //usually its a good idea to keep it in VCS-friendly format, like LaTeX or asciidoc in the same repo as the code, so that it can be easily updated to track changes in the code.// | ||
- | last but not least, there is one important observation you should make. think about the questions/ | + | last but not least, there is one important observation you should make. think about the questions/ |