Position Purpose :
The Software Engineering Solutions Architect leverages enterprise architecture techniques, software engineering principles, expertise, and team management experience to design scalable, secure, and highly reliable solutions using systems and software developed by Benchmark’s Software Engineering department. Benchmark Education builds software to meet the challenges facing literacy learners and teachers. Our software enables and supports a wide range of next generation learning experiences with the promise of doing even more with the right technology team members. The Software Engineering Solutions Architect defines technical systems and software solutions for customer facing and backend systems implemented by internal BEC teams or development partner teams using a variety of technologies.
Job Responsibilities:
Leadership
- Develops a highly performing Solutions Architecture team to design and guide development of Benchmark Education’s software applications and solutions
- Establish the processes and practices for Solutions Architecture
- Recruit, train, develop, and mentor Solutions Architecture staff
- Provides support through practical application of Solution Architecture responsibilities
Strategy
- Ensures the logical and systematic conversion of business, customer and product requirements into flexible, scalable, and high-performance technical solutions which support current and future needs.
- Performs functional analysis, timeline analysis, tradeoff, capacity modeling and interface definition studies to formalize customer requirements into solution architecture specifications.
Architecture
- Successfully manage interactions with many constituents including senior business and IT leaders, end business users, application development teams, and operational teams to clarify requirements.
- Define high -level solution architectures that prioritize scalability, fault tolerance, and security, and breaking them down to detailed designs which support all requirements and can be implemented by development teams and managed by operational teams.
- Defines in written documents non-functional requirements (availability, reliability, scalability interoperability, portability, manageability, scalability, maintainability, security, monitoring, SLAs, KPIs, regulatory and legal compliance) based on business vision, best practices, and company architectural direction.
- Ensures that all architectures support high availability, disaster recovery, and performance optimization, particularly for distributed systems
- Balances a variety of competing goals in a design, including project time, scope and budget constraints, system performance, message verbosity, and loose coupling.
- Assists with writing and communicating best practices, standards, and guide