From e9991d2235dc48a590509ff71033d1b099a28219 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stanis=C5=82aw=20Pitucha?= Date: Mon, 9 Sep 2019 00:05:31 +1000 Subject: [PATCH] Initial questions --- README.md | 75 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 75 insertions(+) create mode 100644 README.md diff --git a/README.md b/README.md new file mode 100644 index 0000000..f7aae09 --- /dev/null +++ b/README.md @@ -0,0 +1,75 @@ +# Reverse interview + +This is a list of questions which may be interesting to a tech job applicant. +The points are not ordered and many may not apply to a given position, or work type. +It was started as my personal list of questions, which grew over time to include both things I'd like to see more of and red flags which I'd like to avoid. +I've also noticed how few questions were asked by people I interviewed and I think those were missed opportunities. + +If you asked something not listed here, send in a PR. + +## Expected usage + +- Check which questions are interesting for you specifically +- Check which answers you can find yourself online +- Otherwise ask + +Definitely don't try to ask everything from the list. + +# The Role + +- What's the on-call plan/schedule? (what's the pay) +- What are the tasks on a usual day? +- What's the junior/senior balance of the team? (and are there plans to change it) +- What does the onboarding look like? +- How much independent action vs working off a provided list is expected? +- What are the expected/core work hours? + +# Tech + +- What are the usual stacks used at the company? +- Do you use source control? +- Do you test code? +- Do you use bug tracking? +- Do you use CI/CD? +- Is your infrastructure setup under version control / available as code? +- What's the workflow from the planning to the finished task? +- Do you have backups / disaster recovery plan? +- Is there a standardised development environment? Is it enforced? +- How quickly can you setup a new local test environment for the product? (minutes / hours / days) +- How quickly can you respond to security issues in the code or dependencies? + +# The Team + +- How is the work organised? +- How does the intra/inter-team communication typically work? +- How are differences of opinions resolved? +- Who sets the priorities / schedule? +- What happens after pushback? ("this can't be done in the projected time") +- What kind of meetings happen every week? +- What's the product/service schedule? (n-weekly releases / continuous deployment / multiple release streams / ...) + +# The Company + +- Where does the funding come from and who decides the high level plan/direction? +- Is there a conference/travel budget and what are the rules to use it? +- What's the promotion process? How are requirements / expectations communicated? +- Is there a separate tech and management career path? +- How much annual / personal / sick / parental / unpaid leave is available? +- What's the status of / view on diverse hiring? +- Are there any company-wide resources for learning available, like ebooks subscriptions, or online courses? +- Is there a budget for getting certifications? +- What's the maturity stage? (early finding direction / feature work / maintenance / ...) +- Can I contribute to FOSS projects? Are there any approvals needed? + +# Remote Work + +- What's the ratio of remote to office workers? +- Does the company provide hardware and what's the refresh schedule? +- Are extra accessories/furniture possible to buy through the company? Is there a budget for them? +- How often are office visits expected? +- Are the office meeting rooms always prepared for video conferences? + +# Office Work + +- What's the office layout? (open plan / cubicles / offices) +- Is there a support / marketing / other call-heavy team close to my new team?