Job Description
Java Solutions Architect
Dallas, TX (Hybrid Onsite from day one)
Phone + Video
J:D:
Desired Skills and Experience
8-10+ years SW development
2-4 years of hands-on application architecture experience
4+ years of Java development experience
2+ years Microservice (need to have built 10+ from scratch)
eCommerce experience (building eCommerce systems)
Kafka or Azure Event Hub
Apache Camel
Experience with: Azure Logic app, Azure Function, Azure Data Factory (if don't have Azure expertise, need comparable AWS)
Expertise integrating with other systems (API development and integration)
Familiar with variety of Design Patterns
DB: Couchbase or NoSQL
Plusses
Swift UI
Experience with "Clear Architecture Pattern"
iOS mobile development experience (Swift or Xamarin)
Day-to-Day *
A fortune 100 client in Dallas, TX is seeing a Solution Architect to join their organization. This position would be within an eCommerce team and would work across 4 different technology directors to integrate various solutions into their development environment. As the Solution Architect, you will need to learn the team and understand their focus for immediate and long term objectives. Upon doing this, you will then provide solutions for their development needs. An ideal person will be doing 50% solution architecture, 25% code reviews, 25% proof of concepts (this can change/evolve day by day). You should act as an individual contributor to create a solution, and then work with developers and team leaders to implement.
Here are some questions they need to be able to answer
MORE QUESTIONS:
- Can you describe your experience with integration patterns like publish/subscribe, message routing, and transformation? Can you provide an example of a scenario where you have used these patterns in an enterprise architecture? - event based architecture / CQRS / Play AKKA (candidate should start talking about any of these 3 typed of integration patterns without you having to prompt them)
- How do you design and implement fault-tolerant Microservices-based architecture? Can you provide an example of a design pattern you have used for this purpose?
- What are your thoughts on containerization technologies like Docker and Kubernetes? Have you worked with them before, and if so, what kind of challenges did you face in integrating them into an enterprise architecture?
- How do you ensure high availability and disaster recovery in an enterprise architecture? Can you discuss the techniques and tools you have used for this purpose?
- What are your favorite design patterns for developing Microservices-based architectures? Can you explain how you have applied them in a real-world scenario?
- What is your experience with developing and maintaining API documentation? Can you describe how you have approached API documentation in a previous project? -
- How do you handle versioning of APIs in an enterprise architecture? Can you explain the techniques you have used to manage changes to API contracts across different versions? -
- Can you discuss your experience with cloud computing platforms like AWS, Azure, or Google Cloud Platform? Have you used them in an enterprise architecture, and if so, what are some of the challenges you have faced?
- Can you describe your experience with integration patterns like publish/subscribe, message routing, and transformation? Can you provide an example of a scenario where you have used these patterns in an enterprise architecture? - event based architecture / CQRS / Play AKKA
- How do you handle integration challenges like data synchronization and consistency across different systems? Can you explain the approach you have taken in the past to ensure data integrity in an integrated system? - data architecture
- How do you handle integration with legacy systems that do not expose APIs or web services? Can you describe the techniques you have used to integrate these systems into an enterprise architecture? - Legacy integration
- How do you ensure that your integration architecture is scalable and can handle increased traffic and data volumes? Can you explain the strategies you have used to achieve this scalability in a previous project? - Performance
- Hystrix - implements the Circuit Breaker pattern to prevent cascading failures and ensure the availability and stability of the system.
- Zuul - implements the Gateway pattern to provide a centralized entry point for requests into a microservices-based system.