-
-
Save zerothabhishek/950120f844368653c6eacec6f731fd2a to your computer and use it in GitHub Desktop.
Revisions
-
vcarl revised this gist
Apr 24, 2018 . 1 changed file with 8 additions and 7 deletions.There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -1,26 +1,27 @@ Questions to ask potential employers * How long do you expect it would take me to deploy my first change? To become productive? To understand the codebase? * What kind of equipment will I be provided? Will the company pay/reimburse me if I want something specific? * What's the longest tenure of a developer at this company? * How long has the top quarter of the developers been here? * What fraction of the developers have been here less than 6 months? * How long does it take to do a complete deployment? * How large are PRs? For a "big" PR, how many lines of code? How long is it open? * About what fraction of their time are developers given (implicitly or explicitly) the freedom to explore? * Do you pay for conferences? * How do you define success and growth for your individual developers? * How often does my manager have 1:1s with their reports? * What kinds of topics are usually discussed in 1:1s? * How often do you have major outages? What constitutes a major outage for you? * Do you have a defined process for the aftermath of an outage? * What's the lifecycle of new development, from somebody's idea to deployment? * How do you balance shipping new features and maintaining the codebase? * How often do 2 devs work together for more than 15 minutes? 3 or more devs? * How do you like to track tasks? * Do you do agile/scrum? * How do you decide what to build? * What are your swimlanes called? * How do you know when something is done? * What project management software do you use? * How many repositories does an average engineer touch? * How often do you do lunch and learns, or other semi-formal knowledge sharing? -
Apr 23, 2018 . 1 changed file with 8 additions and 9 deletions.There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -1,24 +1,23 @@ Questions to ask potential employers * How long do you expect it would take me to deploy my first change? To become productive? To understand the codebase? * What's the longest tenure of a developer at this company? * How long has the top quarter of the developers been here? * What fraction of the developers have been here less than 6 months? * How long does it take to do a complete deployment? * How large are PRs? For a "big" PR, how many lines of code? How long is it open? * How often do you have major outages? What constitutes a major outage for you? * Do you have a defined process for the aftermath of an outage? * About what fraction of their time are developers given (implicitly or explicitly) the freedom to explore? * How do you define success and growth for your individual developers? * Do you pay for conferences? * How do you balance shipping new features and maintaining the codebase? * How many repositories does an average engineer touch? * What's the lifecycle of new development, from somebody's idea to deployment? * How often do 2 devs work together for more than 15 minutes? 3 or more devs? * How do you like to track tasks? * Do you do agile/scrum? * How do you decide what to build? * What are your swimlanes called? * How do you know when something is done? * What project management software do you use? -
Apr 22, 2018 .There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -0,0 +1,27 @@ Questions to ask potential employers * How long do you expect it would take me to deploy my first change? To become productive? To understand the codebase? * What's the longest tenure of an engineer at this company? * How long has the top quarter of the engineers been here? * What fraction of the engineers have been here less than 6 months? * How long does it take to do a complete deployment? * How large are PRs? For a "big" PR, how many lines of code? How long is it open? * How often do you have major outages? * Do you have a defined process for the aftermath of an outage? * About what fraction of their time are developers given (implicitly or explicitly) the freedom to explore? * Do you pay for conferences? * How do you manage technical debt? * How do you balance shipping new features and maintaining the codebase? * How many repositories does an average engineer touch? * What's the lifecycle of new development, from somebody's idea to deployment? * How often do 2 devs work together for more than 15 minutes? 3 or more devs? * How do you like to track tasks? * If they do agile: * Scrum? * How do you gather requirements? * What are your swimlanes called? * How do you know when something is done? * What project management software do you use? * How often do you do lunch and learns, or other semi-formal knowledge sharing? * How often does my manager have 1:1s with their reports? * What kinds of topics are usually discussed in 1:1s?