Turn to recruitment and you will know what to do.
From: http://www.dbanotes.net/jobs/looking_4_a_dot_net_architect.html
Responsibilities:
- 1. mainly responsible for the design of the company's product components
- 2. Responsible for technical analysis and architecture of Product Development Technology Research and Implementation
- 3. defines service-based interfaces, solutions, and implementation plans.
- 4. Lead and drive the technical learning of the entire development team and provide guidance to coding personnel
- 5. Global control and implementation of the established Solution
- 6. Follow the teamCodeQuality and standardization
Requirements:
- 1. Familiar with object-oriented programming ideas
- 2. 7-10 years working experience in the software industry (not required)
- 3. Bachelor degree or above in Computer Science
- 4. Good communication and team collaboration skills, meticulous work, ability to withstand work pressure, and a sense of responsibility
- 5. Have the architecture and design capabilities of the SOA system, and have practical work experience.
- 6. At least 3 years of experience in large-scale ERP project development and production in Architecture (not required)
- 7. Understand Microsoft's main enterprise application technologies and servers: Biztalk, message Queen (Message Queue), Windows UDDI server, and other related technologies.
- 8. very proficient in web services, especially familiar with related technologies such as WCF and WWF.
- 9. Focus on the background development architecture, rather than the page operation capabilities
- 10. have considerable experience in implementing the design model of software design solutions
- 11. Familiar with common design modes
- 12. have hands-on experience in Optimizing and evaluating system performance
- 13. Experience in MVC design
- 14. More than 3 years of practical experience in multi-layer application system development
- 15. Understand IOC, AOP, and other technologies
- 16. Experience in SSO single-point authentication or pass development
- 17. Have multi-system integration project implementation experience.
There are still a lot of descriptions. It is actually. net architects do not have to force all the conditions to be met (the two "non-mandatory" labels are added by me ), do not bother to describe whether there are too many points.
