Behavioural.docx

14 Amazon Leadership Principals
1. Customer Obsession
a. Focus on customer requirement
b. Rather than lot of features provide features that can fulfil basic need with good latency
c. Later more features can be added on top of it
2. Ownership
a. We should think for complete project delivery rather than considering just own module in
the project
b. When any issue came, whether its my feature or not, I should start debugging it & try to fix
it.
3. Invent & Simplify
a. When we get a get any complex problem then also start with simple approach.
b. Don’t make initial approaches too complex
c. Rather than writing full code from scratch, weshould use already available api and libraries.
4. Leader Are Right a Lot
a. At every level some decisions should be taken, its not only a duty of a single person.
b. Even a new engineer can take decision for optimization and prioritize this task as our first
goal is to fulfil customer requirement.
5. Learn and be curious
a. Most of the time, Once the Product become stable then engineer afraid of changing code
for improvising because they think it may break code or some error can occur.
b. Always curious to Learn New technology and apply it, never become comfortable with
existing technology.
c. Think always for improvising.
6. Hire and Develop the Best
a. Senior engineers or leader should identify candidate with long term growth potential.
b. They should also look for exceptional talent in team and provide them opportunity to grow.
c. They shouldn’t hold back people but use their influence to provide them opportunity.
7. Insist on the higher standards
a. Standard of code/design should be very high for developer.
b. Should clear all testing
8. Think Big
a. Always think a scalable system which will be used by more users
b. System should be scalable and distributed
9. Bias for action
a. Speed matters than go deep so don’t think the perfect design in first go.
b. Always develop thing and then launch and keep revisiting it. [Incremental development]
10.Frugality
a. Use resources when it’s really required.
b. Try to consider less budget.

11.Earn Trust
a. As a leader we should accept responsibility for both Good as well as Bad.
b. Treat others and their ideas with respect
c. Admitting failures, listening and communicating to help employees
12.Dive Deep
a. While working on one project, a ticket has come which has high priority
b. As a developer, first mitigate the issue or unblock the customer rather than go deep.
c. Once it is done then later go on deep dive to find root cause why it has come.
13.Have Backbone, disagree & commit
a. Evenif everyone disagrees withyou, you should give your approach through complete data
points.
14.Deliver result
a. We need to deliver your features on time with quality
b. Also, we need to know how to prioritize our tasks
c. Although we are working on multiple projects then also.
Resolve Conflict with TeamMember [ During Final Year Project]
I had a conflict with my friend who was a part of my team in my college projects. We had a conflict
regarding the design of the system. He was keen on using NoSQL DB as a backend service for our project
as this helps us to explore schema-less Databases more as currently most of the industry is using NoSQL
DB to support billions of customers.
I was more interested in using MYSQL DB because that is primarily covered in our colleague's curriculum
and all our team members are well aware of RDMS. Considering the time, we have and the number of
people in the project it's more appropriate to use that technology which everyone is aware of it So the
project can be submitted within time.
We had a separate discussion withall our team members, His point vas totake the challenge and learning
new technology which will surprise the instructor as well as teachers. His point was valid but we should
also consider the project timeline and resources we have. Also, we need to work on this project along
with our regular classes and curriculum. There are maximum chances are there we will slip the project
submission deadlines because learning and implementing completely new technology takes time for all
of our team members. Ultimately, after understanding all pros and cons we came to the same page of
using MySQL DB for our project.
Tell me a about a time you had to meet a tight deadline ?
In my recent internship, I delivered my primary project ahead of schedule and was given a secondary
project to deliver by the end of my internship. Since my secondary project was required prior knowledge
of angular/mongoDB etc. It took me some time to come up to speed. The original time estimate was
given based on someone already working within the department.
I know that I was not going to be able to complete the project by the end of my internship. I talk
with my mentor and he allowed me to continue to work on the project part time even after the official
end of internship. She told me that they typically would not do it but she understood the circumstances
and criticality of work.
I was working day-night for 1 week as it was hard deadline and submitted the project. I got the highest
rating for my work in internship.

Tell me about a time you failed
 Failure required
 Learning from failure to become better at job and avoid similar mistakes
 Don’t blame anyone in fact take your own responsibility
#Case-1
[ SITUATION ]
I was working as a developer, so due to my good performance in development, I have been given a
chance to lead the next release. It was an incremental release for a product in the prototype phase.
Due to more excitement, and I didn't consider my role seriously I started working even harder as a
developer. And take more features in the first release. This proves to be a critical mistake. The release
was not that great, we were fixing bugs at the last min before release. The release has multiples issue.
[ Action Taken ]
Situation we reverted back the product to the previous version
[ LEARNING ]
My main learning from this incident is that I should have understood my responsibility as leading a
product and think of a long term that makes the product more stable and reliable one rather than
providing more and more feature which also makes team put extrahours and also, the product will not
be stable for long term. Although I learn it a hard way but this lesson helped me ahead in my carrier
and from last year, I was handling all releases in my last company
#Case-2 [ Taking lot of responsibility /over-promising ]
[SITUATIONS]
You were working on a project with a strict deadline meanwhile your lead/some senior person (who
was not aware of your current tasks) ask you to fix some high-priority task. Rather than communicating
with your team members or sprint master that you overload with your current task, you have taken
additional tasks. You push extra, spend extra time to work on a parallel task which results in the failure
of quality deliverables in your current project.
[LEARNING]
My main learning from this incident is that it's always good to speak up if you are overloaded withmore
tasks in your team meetings. Ultimately it impacts the deliverables.
-------------------------------------------------------------------------------------------------------------------------------------
During my internship program, I was overly eager to learn project work so much that I agreed to take
on unrealistic deadlines with my co-workers for the first task. As a result of that, I was late completing
tasks for two subsequent weeks. My co-workers were not happy with me.
After that experience, I devised a tracking system to make sure I knew how long each task would
actually take, and make sure never to fall behind again. Before providing any timeline, 1 day I took to
analyse the task complexity by discussing it with team experts. After thorough discussion and analysis,
I commit the proper estimation for the tasks.

What skills wouldyou like to improve ?
1. Networking Skills – Networking and contact always helps in career growing. I always feel
uncomfortable approaching people I don’t know. I need to improve connections.
2. Technical Skills
3. Presentation Skills – I would like to improve my presentation skills when I present to a large
audience. I find often I speak too fast at presentation. I like to improve voice control and delivery
during my presentation.
Biggest technical mistake you have made ?
I am my friends were working on a college project to present at the semester end exam. We have
used Visual studio, Oracle and Some scripting code.
While presenting our project to the instructor, he asked us , your project is good but now a days
almost most of the application are web based so we can execute a same application of different
clients. Is our project able to handle the networking thing or it will work only on single standalone
system. I was aware of the concept of socket programming but missed to implement in the project.
We got gpd marks but it wasn’t considered in top-3 project.
Later we have discussed with instructor to get more information about socket programming and
their implementation. I came to know about implementing it on different layers that we studied in
TCP/IP and OSI.
Tell me about a situationwhere you had solveda difficult problem ?
I was doing a project …….. Changing lots of code before presentation as new patch was released as
some existing functionalities were modified.
Why is your GPA not higher ?
I struggled with adjusting to college life and didn’t manage my time during initial years. However
gradually I have learned to be more efficient, understand my responsibilities and prioritizing the
tasks. So, after that continuously I have improved it in each semester and got good grades.
If you are behind the schedule on a project, what will youdo ?
1. Communicate with client/manager
2. Update schedule properly
3. Try to identify critical items first in the release
4. Borrow additional member from other team
5. Update process internally.
6. Perform root cause analysis
7. REASON
 Less Resource o Poor Planning
 Project requirement changes consciously

Behavioural.docx

Related slideshows

More Related Content

Behavioural.docx