Enterprise Solutions Architect // Remote to Onsite // FL / TX / WA
Hello Team,
Please find the below requirement details
Position: Enterprise Solutions Architect
Location: Remote, after 6-months they may have to go onsite to Tampa, FL, Plano Texas, or Camas WA
Duration: 12 Months
Rate: $90/Hr. on C2C
This is not a Sr or Lead Developer position, but actual Architects.
Basic Qualifications:
.Net API development Microservices Messaging (any) Good experience architecting systems integrations
What are the top 3 MUST HAVE technologies or Required experience of the position?
1. After 6 months must be willing to sit onsite and be vaccinated
2. Messaging (any)
3. Good experience architecting systems integrations
NICE TO HAVES (OR WHAT GETS THE WIN)?
1. Financial systems experience
2. Microservices
3. Azure
The Day-to-Day:
Partner with the lead Portfolio Management Solution Architect and development team leads to set standards for technical excellence
Collaborate with the enterprise architecture group to evolve architectural standards and to represent the Portfolio Management Group system architecture
Create and maintain system integration, data flow, network zoning, and other diagrams for all Portfolio Management systems
Perform hands-on coding as needed, as well as code reviews, architecture critique, and technical design
Build rapid prototypes for architectural proofs of concept
Present architectural decisions to stakeholders and executives in a clear and articulate manner
Your Qualifications:
5+ year's technical leadership experience
BS/MS in Computer Science or related field or combination of education and experience
Demonstrated experience working with investment management systems and processes within a financial services firm
Expertise in software architecture design, distributed systems, Microservices architectures, and data distribution strategies
Hands on experience creating diagrams including system diagrams, data flow diagrams, and system architecture maps
Experience with multiple technical stacks and a wide breadth of ETL, message bus, and integration tools
An understanding of architectural tradeoffs
Comments
Post a Comment
Thanks