Asked me if I knew any NoSQL I said not really. Then asked me how do I design a database model if Fields of each Record in table A's is not set before implementation and could be subject to change in the future.
Case 1. There are known N fields but each record might have value for any of N fields. Solution: Declare N fields and set them all to Nullable. Case 2. There are N fields for now and the requirements are subject to change at any time. Solution: This is unclear and undefined requirements. This is not recommended to be implemented. If really has to be done, redesign and get previous useful data through ETL.
I said I'd begin by breaking down the feature into sections, writing my own testplan and noting any questions I had regarding design questions and ask the appropriate person for clarification, and document this information for the team.
Pretty much they had no idea what they are doing in terms of managing quality. They weren’t even sure what was on job description and whom they are actually looking for. They talked everything about Standards required in organization and my academic and professional background.
It was more like they really don’t know what they are supposed to be asking. They were taking suggestions (as if) to how to improve their company. Inviting applicants to get advises. (Very cheap practice and illegal)