I have a lot of experience from different enterprise IT projects. I have been working as both developer and architect. The architect role includes review, proof-of-concept, evaluating technologies, expanding frameworks, mentoring less experienced colleagues, making architectural and design decisions, attending performance issues, the customer dialog, etc.Twice, I have been among the very first to join a tech company, that later grew to 50+ employees (developers). The second time I believe I was one of the most important tech persons paving the way to success.I have lots of experience with agile processes. I do not believe in heavy/strict/static processes, but in the ability of intelligent people, through retrospectives, to continuously work out "the best way in the current context" based on inspiration from others (e.g. Scrum, Kanban or whatever is hot)I have a lot of experience with and interest in performance testing and tuning - endurance, response-time, throughput/capacity, scalability etc.I believe that there is a high factor (up to infinity) in the "ability to create business value" between the great and the below-average developer. Hire based on skills, not experience nor seniority. The great developer will master a new technology or method within weeks. The not-so-great will never master, even after decades.