The journey from a seasoned developer to become an architect often gets challenging. We help you on this journey to provide a simple yet effective path to achieve your goals.
Each developer would aspire to become an architect in due course & find the path to be very challenging at times. Some people get guidance from their mentors & few learn it through training/certification, reading, social media, blogs etc.
We define AJP (Architect Journey Path) for a developer so that you don’t get lost in the process & achieve your goal to be a successful architect.
|Role||Responsibilities & Skill-set|
|Developer||Coding, Rule Compliance, Unit Testing, Integration Testing, Refactoring, Design Patterns Implementation, Performance Optimizations, Security Fixes|
|Technical Lead||Development Skill-set Plus Design Patterns, Anti-patterns, Refactoring, Reviews, Performance & Security Testing/Fixes, Design/Architecture Components|
|Technical Architect||Technical Lead Skill-set Plus Architectural Patterns, Design/Architecture Creation, Specific Technology Artifacts such as data, security, information, UML, Broader Technology Knowledge (Build & Release, DevOps, Deployment Topologies, Cloud Technologies)|
|Solution Architect||Solution Mapping to Specific Technology, Impact Analysis, ROI of Technology Decisions, Broader Solution Knowledge (COTS vs. OpenSource, Solution Comparison & Recommendation)|
|Enterprise Architect||All the above plus Enterprise framework knowledge (e.g. TOGAF), Architectural Patterns, Architecture Evaluation Skills, Roadmap Planning, Technology Vision, Future State Architecture, Gap Analysis, Stakeholder Management (Business & Key Technical)|