What I’d like to know about my next employer
9/2/11, 17:44
(No Ratings Yet)
Loading ...
(No Ratings Yet) Loading ...Here are some questions that interest me when choosing a company to work for. I won’t necessarily get the answer to all these questions, but there’s no harm in trying…
Company
- Tell me a bit about the history of your company.
- How old is it, how has it evolved, what are its goals/vision?
- Is it a startup?
- Do you have sales yet? How many?
People
- What people will I be working with?
- Do you have blogs I can look at?
- How many people are we talking about?
- What is your growth/hiring plans for the next year?
- How does the org chart look like?
- Who will I be reporting to, and who is he/she managing?
- What kind of people are you looking for?
Projects
- What projects or roles am I interviewed for?
- What is the job description/title?
- How dynamic is the project?
- Can you provide an example of a component I would own?
Tools, Technologies and Methodologies
- What tools do you use?
- Do devs have budget for decent IDEs & hardware? Two screens, laptops with SSDs?
- What are you using for build management & continuous integration?
- What programming languages are used?
- What open source / 3rd party libraries are you using? Extra Credit (thanks Ken): do you contribute to any OSS libraries?
- Do you have specific development methodologies you use?
- How does your release cycle look like?
That covers most of it. What are your questions?
Ken Egozi:
” What open source / 3rd party libraries are you using? ”
9/2/11, 18:35I’d add:
What OSS libraries do you *contribute* to?
ripper234:
@Ken – +1, thanks. Updated.
9/2/11, 18:58Arik Yavilevich:
How is the cycle managed?
10/2/11, 13:48How is cycle content determined, when and how dynamic it is?
Who prepares the functional specs?