Principle Architect

Job title: Principal Architect Duration: Contract to hire. Location: Hybrid in Dallas TX is preferred. -> Open to remote but will need to travel once a month.

Feedback from Manager

Technical Proficiency Expectations:
Solid Software Engineering Background: Emphasis on core system design concepts and practical experience is crucial.
Up-to-Date Knowledge: Candidates should provide recent examples of architecting solutions to complex business problems. Avoids references from decades ago.
Hands-On Experience: Preference for candidates with recent, hands-on experience in software engineering, even in architect roles. Should not be overly focused on high-level business talk without demonstrating a grasp of technical details.
Revised Candidate Profile: Focus on candidates with 3-7 years of architecture experience and recent software engineering experience.
Overview: Less about knowing the latest technologies and more about the experience in transforming systems. Architecting IT systems, advisor, mentor, negotiator, troubleshooter, and providing a forward-thinking view.
Primary Focus:
Client is seeking a Principal Architect to support ongoing transformation efforts and team growth.

Technical Expertise:
Familiar with UI frameworks (React, Angular; Angular preferred).
Well-versed in managed services for storage and compute (Google Cloud Platform preferred but other hyperscalers considered).
Strong capabilities in cloud computing and AI.
Essential:
Knowledge of cloud computing, message queues (Kafka, RabbitMQ), SQL/NoSQL databases, web/application servers, and BPM technologies.
Experience with both legacy and modern systems (monolith to microservices).

Leadership and Influence:
"Mile wide, inch deep" in experience, with the ability to quickly adapt and contribute to various projects.
Generalist Approach:
Involvement in POCs, architectural roadmaps, and advisory roles.
Leading by influence rather than direct management.
Individual contributor role with a focus on influencing stakeholders, leaders, and other architects.

Internal Communication:
Knowledge of RPA (UiPath, Automation Anywhere) is a plus but not a deal-breaker.
RPA:
Google Cloud Platform preferred, but experience with other hyperscalers (AWS, Azure) is transferable.
Cloud:
Familiarity with AI/ML, GenAI, and conversational interfaces. Understanding of data collection from public domain (RAG architecture).
AI/ML:
Knowledge of managed services and cost implications.
Understanding relational vs. NoSQL databases (Postgres vs. MongoDB).

External Communication:
Technical expertise, presentation skills, and clear communication.
Key Attributes:
Should be able to analyze stuck development issues, come to calls and troubleshoot, and provide insights, though hands-on coding is not a primary responsibility.
Troubleshooting:
Engage with business counterparts for transformation programs.