Technical Platform Director

Key Responsibilities

• Manage a team of very senior engineers in such a way to obtain the respect of the team members: technical authority (capability to lead, challenge and consolidate technical conversations), program authority (ability to prioritize, communicate, plan and deliver on time)
• Co-develop (with the Principal Engineers) the architectural platform strategy for the product domain, ensuring alignment with the cross-product architectural vision.
• Co-develop and maintain a comprehensive technical platform roadmap that guides the whole engineering
• Guarantee that the platform architecture is designed for scalability, reliability, testability and resilience.
• Ensure that all the individual product architectures adhere to the platform architectural principles and guidelines
• Make well-informed platform architectural decisions that align with the product strategy
• Collaborate with the CPTO, VPs and Product managers to define and prioritize products roadmaps, balancing feature development with technical initiatives
• Clearly communicate platform architectural decisions, strategies, and their implications to stakeholders at all levels.

Qualification & Requirements

Main Qualifications

• Master’s in Computer Science, Software Engineering or related discipline
• 8+ year experience in Software development
• 5+ year experience in people management
• 3+ year experience in managing technical roadmaps
• A strong background in OOP
• Experience in Software design/architecture (microservice, synchronous/asynchronous communications, etc.)
• Excellent knowledge of development best practices (testing, design patterns, etc.)
• Experience interfacing with databases (SQL and/or NoSQL)
• Experience in DevOps and agile practices CluePoints Intelligent Statistical Monitoring Confidential and Proprietary Page 2 of 2
• Experience in implementing SaaS/Cloud-based solutions is a big plus

Leadership Skills

• Critical Thinking: The ability to analyze technical challenges deeply, consider multiple perspectives, evaluate evidence objectively, and make well-reasoned decisions.
• Ownership: The capability to make technical decisions independently without deferring to upper leadership, while taking full accountability for the outcomes.
• Stakeholder Management: The skill to navigate cross-functional relationships, ensuring collaboration and alignment with the product management and the technical leadership.
• Non-technical Communication: Excellent verbal and written communication skills in English, with the ability to convey complex technical concepts to non-technical stakeholders, including senior leaders, presenting ideas clearly, persuasively, and with appropriate details.
• Leading, Not Dictating: Inspiring and motivating others through a clear architectural vision, engaging the development squads and empowering them with autonomy.
• Self-Awareness: Understanding one’s strengths and weaknesses, seeking feedback, and continuously striving for personal and professional growth.
• Strategic thinking: The ability to communicate clearly the architecture and the technical roadmap. The capability to align technical architectural goals with product (management/operations) objectives.
• Technical passion: a genuine passion and curiosity towards tech, with a willingness to experiment, evaluate, and introduce other team members to new frameworks, technology, and workflows, and be willing to work on a huge array of differing technology solutions.

Benefits

• Health Insurance
• 401k
• Vacation and Time Off
• Other Perks and Benefits…