15 Characteristics of a Agile Programmer

1. Impressive technical skills
 Describe your experience with different programming languages.

2. Willingness to learn
 What do you do to keep your programming skills current?

3. Debugging skills.
 How do you handle bugs in your code? (next, I would give them a trial run to debug code)

4. Work environment match
 Some programmers require complete silence to concentrate, while others thrive in chaos.

5. Problem-solving skills.
 How would you create (insert near impossible task for your organization)?

6. Passion for the work.
True programmers are self-proclaimed “computer geeks,” spending their time gaming, building servers, or creating apps for friends. 

7. Grace under fire.
 The ideal programming candidate will be able to handle even the most stressful situations calmly and, most importantly, be able to continue working.

Describe a time when you were under extreme pressure and your application wasn’t working. What did you do?

8. People skills.
 Explain how your favorite application works in a way a layman would understand.

9. Laziness.
 Tell us about a time when you saved time by automating a process.

10. A business perspective.
Have you ever made a suggestion that improved a business’s processes?

11. Ability to plan
Explain your approach to a new design. What do you do first?

12. Ability to handle failure.
Have you ever spent hours on a code, only to find it was the wrong approach? What did you do?

13. Teamwork mentality.
 Share a rewarding team experience.

14. Willingness to research.
Tell us about a time you had to learn about a particular business? How did you do your research?

15. Respect for deadlines.
Describe a time when you had to meet a tight deadline.

source- 15 Chracteristics of an Agile programmer

Comments

Post a Comment

Popular posts from this blog

Scrum Answer to Top 10 Software Project Risks

Source: (The Standish Group, 2011) Lack of top management commitment Scrum demands commitment from the top management through the assignation of a full-time cross-functional self organized team. The team is protected and can take their own decisions about the project with the support of the top management. Failure to gain user commitment In Scrum, the team constantly show working software to the users, which increase the commitment and feedback. Misunderstanding the requirements Scrum knows that is not possible to fully understand all the user requirements. In each iteration, the team work in the more important and clear requirements. As the software is developed, the team get better insights about the project goals and have more clarity about the following requirements. Lack of adequate user involvement Constantly working software makes the users more involve in the process. Lack of required knowledge/skills in the project personnel In Scrum, the teams are cros...
Read more