Previous Job
Solution Architect
Ref No.: 18-01121
Location: Topeka, Kansas
Start Date: 07/12/2018
Looking for minimum 12+ yrs of profile. Candidate should be hands on Java and cloud Services

The position of Enterprise Solution Architect/Solution Architect must be able to:
  • Translate models such as Business Process Models, Process Mapping Models and Task Mapping models among others, from Business Architecture into actionable Solution Architectures that can be further elaborated into detailed specifications such as OpenAPI (Swagger), Technical Architecture Design Documents, Feature Stories and User Stories, Non-Functional Requirements (NFRs), Test/Acceptance Criteria, etc. as needed.
  • Leverage ARIS to express the Solution Architecture from Conceptual, Logical, and Physical viewpoints.
  • Identify existing external behaviors of the Business, Application, and Technology/Infrastructure layers and describe in Archimate viewpoint models how these behaviors will interact structurally in a Target State to realize the designated Business Processes across all layers to be implemented within a Micro Services Solution Architecture.
  • Elicit detailed business rules from a code-decomposition process that will inform system behavior and performance of the desired Target State
  • Effectively communicate with Business Leadership, Product Owners, Product Managers, Architecture Teams, and Feature Team Developers to drive out a Roadmap of deliverables to transition from the Current State to the desired Target State within a Scaled Agile Framework process.
  • Ensure the Feature Team developers are equipped to perform full DevOps capabilities within a Continuous Deployment environment, including: Agile Code Reviews, Code Coverage and Quality metrics, Automated Unit and Functional Testing, Automated User Acceptance and Approval Processes, etc.
  • Contribute quality, secure, performant, and tested code that may address complex system aspects or other areas as needed to meet the Sprint objectives.
  • Describe common patterns at many levels within the implementation space and identify when to apply these patterns:
    • Software Refactoring Patterns
      • 'Extract Method'
      • 'Inline Method'
      • 'Replace Constructor with Factory Method'
      • 'Replace Conditional with Polymorphism'
      • 'Tease Apart Inheritance'
    • Software Design Patterns
      • Prototype
      • Singleton
      • Factory Method
      • Strategy
      • Iterator
      • Proxy
      • Decorator
      • Fac¸ade
    • Enterprise Application Architecture
      • Model View Controller
      • Optimistic Offline Lock
      • Separated Interface
      • Registry
      • Repository
    • Enterprise Integration Patterns
      • Event Message
      • Dynamic Router
      • Command Message
      • Service Activator
    • Micro Service Patterns
      • Backend for Frontend
      • Circuit Breaker
      • Anti-corruption Layer
      • CQRS
      • Event Sourcing
      • External Configuration Store
  • Describe principles of the 12-factor App and how to achieve them
Furthermore the following technologies must be understood and leveraged as part of the desired Target State Micro Service Solution Architecture:
  • Apache Kafka
  • Spring Framework
  • Spring Boot
  • Gradle
  • Jenkins
  • GitHub
  • Open Shift
  • Docker
  • Kubernetes
  • ReactJS and/or AngularJS
  • Cassandra
  • Distributed Cache/Data Grid
  • DB2 JSON / MongoDB
  • DB2 SQL
  • Redis