1. Introductory
What role do you have in the software department and how might this change or stay consistent with using the Telemetry Dashboard?
What programming languages are you familiar with? (To get a better understanding of what languages people in the software dept know already)
Have you participated in a race before?
Do you have experience with working on responsive designs?
Do you have experience with working on telemetry dashboards?
What were your responsibilities for them and were you able to use them effectively?
What stacks & programming languages did it incorporate?
2. Data prioritization
Are you familiar with data visualization and the tools associated with it?
What data do you want to focus primarily on? (could do a card exercise similar to the one in the Hardware guide)
How much data do you usually view at once?
At what point is too much data overwhelming?
3. Process involved in performing tasks
What are your most used design patterns and in what contexts do you use them?
Describe the process you have for a programming task, from requirements to delivery (SDLC).
Does the team plan on using Agile software development when working on telemetry or do you have another ideation in mind?
What are your thoughts on software testing?
If a bug were to appear in the telemetry dashboard, how would you go about implementing your error handling?
Are there any technical obstacles that you must typically go through when navigating a task?
4. Stakeholder stuff
How do you explain technical challenges to stakeholders who do not have technical knowledge or background in software?
Ideally how much time do you want to spend when working/performing on a specific task?
How do you determine a project’s success?