Are Right A Lot

Question 1

Tell me about a time when you had to work with incomplete data or information (or can you think of a time when you had to make a decision but you didn’t have enough data to be sure you were making the right decision? What did you do and how did it work out?)

Answer 1

Exhibit story since here there was not log
no evidence
its all guts.

Question 2

Can you think of a time you made a bad professional decision? What was the impact of the decision? What did you learn?

Answer 2

Situation:
I was working for a banking company. It is a multibillion dollar company headquartered in USa.
I recently joined and am working as a software developer. I had one interview setup for me for a few days to join the Bank of america merger module.

Task:
To give and pass interview and joint the team
Actions
I prepared for the interview however I failed on all JavaScript related questions.
I lost the opportunity to join a good team. Therefore I started learning JS more deeply
I started training couple of groups in JS in my company as well
Result
I was leading next project completely
Become member of induction and training department
Got an opportunity to visit a client and work from his location.
I was leading next project completely
Become member of induction and training department
Got an opportunity to visit a client and work from his location.
Now in my current role I have been leading the entire front end engineering team.

Question 3

When you had to make a difficult decision with inputs from a lot of people

Answer 3

Situation
I was responsible for the development team. I was interacting with the preview dev team on a daily basis and used to see their preview used to load in 6-7 minutes of time. Item Authors used to spend a day authoring items. Product owners used to wait to deliver new features in preview. Also whenever the driver team used to change, the preview used to break as well.
Over all there are 4 different entities involved.
Task
I decided to help businesses to get preview issues resolved and give them snappy previews.
Actions
Spoke with all 4 different entities and talked with end users in preview about exactly what they want.
Studied current architecture and able to carve out the part of the source code that can be used for preview separately and called it preview system app
Demo the working prototype to my VP of software development and he noticed the snappy the solution was
I presented to Product owners and business directors.
Results
The preview was working 15 sec for in memory data and 30 with db connection
Authors used to edit their items very quickly rather than waiting for the whole day to author a single item.
Preview lifecycle becomes independent of driver.