Cleaning up

README.md

@@ -21,7 +21,7 @@ Carefully curated content to help you ace your next technical interview, with a
 - [Interview formats](non-technical/interview-formats.md) of the top tech companies
 - [Behavioral questions](non-technical/behavioral.md) categorized by companies
 - [Good questions to ask your interviewers](non-technical/questions-to-ask.md) at the end of the interviews
-- [Helpful resume tips](non-technical/resume.md) to get your resume noticed and the Dos and Don'ts
+- [Helpful resume tips](non-technical/resume.md) to get your resume noticed and the Do's and Don'ts
 
 This handbook is pretty new and help from you in contributing content would be very much appreciated!
 
@@ -53,7 +53,7 @@ Also, existing resources focus mainly on algorithm questions, and lack in covera
   - [Psychological Tricks](non-technical/psychological-tricks.md)
   - [Questions to Ask](non-technical/questions-to-ask.md)
   - [Negotiation Tips](non-technical/negotiation.md)
-- **[Utilities](utilities)** - Snippets of algorithms/code that will help in coding questions.
+- **[Utilities](utilities)** - Snippets of algorithms/code that will help in coding questions
 
 ## Contributing
 

non-technical/questions-to-ask.md

@@ -19,14 +19,6 @@ Here are some good questions to ask at the end of the interview, extracted from
 - What was something you wish someone would have told you before you joined?
 - What was your best moment so far at the company?
 
-### Product
-
-- Tell me about main products of your company.
-- What is the current version of product? (If it's v1.0 or similar - there could be a lot of chaos to work with)
-- What products are main competitors for yours?
-- What makes your product competitive?
-- When are you planning to provide the next release? (If in several months, it would mean a lot of requirements specified in job description are not so highly actual, not needed right now)
-
 ### Culture
 
 - **What is the most frustrating part about working here?**
@@ -45,7 +37,6 @@ These questions are suitable for any technical role.
 - **What has been the worst technical blunder that has happened in the recent past? How did you guys deal with it? What changes were implemented afterwards to make sure it didn't happen again?**
 - **What is the most costly technical decision made early on that the company is living with now?**
 - **What is the most fulfilling/exciting/technically complex project that you've worked on here so far?**
-- **There's "C++" (or Python, Swift or any other tech) in job description. How will you estimate my proficiency in this tech in 3 month? What exactly will I have to do concerning it - write 500 lines of code, create some classes, framework, library?**
 - How do you know what to work on each day?
 - How would you describe your engineering culture?
 - How has your role changed since joining the company?
@@ -56,6 +47,15 @@ These questions are suitable for any technical role.
 - What does the company do to nurture and train its employees?
 - How often have you moved teams? What made you join the team you're on right now? If you wanted to move teams, what would need to happen?
 - If you hire person, what do you have for him to study product you're working on and processes in general? Do you have specifications, requirements, documentation?
+- There's "C++" (or Python, Swift or any other tech) in the job description. How will you estimate my proficiency in this tech in 3 months?
+
+### Product
+
+- Tell me about the main products of your company.
+- What is the current version of product? (If it is v1.0 or similar - there could be a lot of chaos to work with)
+- What products are your main competitors?
+- What makes your product competitive?
+- When are you planning to provide the next release? (If in several months, it would mean a lot of requirements specified in job description are not needed right now)
 
 ### Management