Do you have any questions for me?
When an employer/recruiter asks you this question, you should answer, “YES OF COURSE I DO.” Then you casually bombard them with the questions listed below. Although, you should keep in mind that some questions can be answered just by doing your homework (researching the company). So don’t ask all the questions.
- Where will the company be in 2 years? (maybe “2 years” should be greater if company is older)
- Will the business model remain the same? Is the business model still in flux?
- How many employees will there be in X years? What many of them will be engineers?
- Does the company plan to scale up? How?
- Increased marketing efforts?
- Increased R&D?
- Growing talent?
- Creating partnerships?
- Business model pivot?
- What are typical work hours?
How often do people actually take vacations?
- What are some examples of your company’s culture in play?
- e.g., It’s one thing to say the company promotes diversity, but what are examples of that happening?
What aspects of your company help shape the cuture?
- Older/bigger companies: One of the stereotypical downsides of working at a more established company is that employees don’t feel like they have a big enough impact. How do you ensure employees can make substantive contributions rather than feel like a tiny cog in a big machine?
- How do you ensure that employees always get to try/learn new things?
- How many engineers does the company have?
- How many back-end, how many front-end, how many full-stack?
- How big are the engineering teams?
- Will team size change a lot (scaling up)?
- Do employees ever change teams/roles?
- Exactly whom would I be working with?
- What are their roles, backgrounds, etc?
- How does user feedback ultimately end up reaching the engineers?
- What kind of development cycle do they use?
- What is the structure of a typical sprint?
- How often do engineers deploy?
- Do they use Agile SCRUM, Kanban, etc?
- In an average week, how many meetings would I need to attend?
- How does the company ensure quick, painless onboarding?
- (does the company ensure new hires don’t get overwhelmed by huge, existing codebase?)
- (or is there no onboarding at all because the company is too tiny?)
- Does the company have strong opinions on coding aesthetics?
- Does the company have a style guide?
- Are there code reviews?
- Are they scheduled or ad hoc? (“ad hoc” may be BS for “rarely”)
- Is there time set aside for post-mortems, reflections, retrospectives, etc?
- What kind of testing is in place?
- (unit testing, integration testing, e2e testing, QA engineering)?
- which tools?