Telecom Integration Chief Architect$ 100k/Year Flexible Long-term
Do you have a telecoms IT background and do you have the ability to analyze, research, and resolve challenges on all aspects of an IT solution being deployed in a customer environment? If yes, then this role may be for you.
We have high expectations for our chief software architects to implement solutions within a telecoms customer base. You will have aggressive daily and weekly targets set for you. Your output of work is measured daily, both from a quantitative as well as a qualitative aspect. You will receive daily and weekly feedback on your performance which will help you resolve blockers and ensure you are meeting your targets.
Carlos R, Chief Architect
A Telecom Integration Chief Architect is expected to lead a team of Telecom Integration Architects and Engineers. As a Chief Architect, you will be faced with different work and country cultures which you will need to adapt to. Chief Architects work remotely and also on-site at client premises.
Telecom Integration Chief Architects have aggressive daily and weekly targets to work against and can expect to receive daily and weekly feedback about performance. The regular feedback is used to help you improve immediately and to help you resolve blockers which may be slowing down your performance.
Onsite and remote team lead of engineers
Technical interface to the project manager and customer
Planning and execution of on-site integration for complex BSS architectures
Working with 3rd parties in trouble resolution and ensuring compliance with requirements
Accountable for all tasks and deliverables of solution integration within a BSS project
We believe in continuous growth and strive for continuous improvement. We also have an obsessive focus on improving the quality of teams and you will learn how to do this as part of your work in our continuous journey towards improving the quality of products.
You will learn how an organization operates with an automated continuous deployment pipeline; you will learn how innovation and experimentation with technology can help drive productivity improvements, reduce costs and free up your time to do more meaningful and interesting tasks.
You will also learn how to operate in our metrics-driven culture, which is the foundation of our success in measuring and improving every engineering process and product we deliver. This also ties in to the use of WorkSmart Pro, where you can learn how to improve your efficiency during your standard working day. You will learn how our centralized software factory model benefits an organization and gains from economy of scale; the more we grow the more efficient we become.
At the end of the day we want you to become a specialist in some of the parts of our software factory model and allow you to master your technical skills while interacting with the top 1% global technical talent.
As a Vice President of software engineering, your mission is to manage a team of IT professionals that will provide expert techno-functional consulting services to telecommunications and enterprise software companies.
As a Software Engineering Manager, you will be managing a team of 5-10 engineers and/or architects following best practices in management. You will be accountable for delivering business value for our extensive portfolio of products and services.
Telecom Integration Chief Architects work with the newest IT products in a demanding environment. You should have already worked as a Telecom Integration Architect in various projects, and this will be the next step in your professional career.
Watch this video presentation by Danielle Royston, CEO of Optiva, which demonstrates a solution some of our teams have put in place using Google Spanner
How can a Telecom Integration Chief Architect get promoted to new roles?
If you are a top performer in your role then it is possible for you to apply to new roles and move up the career ladder. From a Chief Architect role you may apply for a Software Engineering Manager role then progress to VP of Engineering. The possibilities exist and your career path is only dependent on your performance.
As a Telecom Integration Chief Architect, what are the opportunities to learn and work with new technologies?
The learning responsibilities belong to you and are endless. Chief Architects are expected to be versatile in various technologies and open to learning new tools and new technology stacks. Chief Architects are also expected to be innovative and identify new technologies which can be leveraged to automate manual tasks and therefore freeing up time for more intelligent and interesting work. .
What does a Telecom Integration Chief Architect day look like?
A standard day in this position is typically comprised of the following tasks: a short daily check in with your manager to review blockers which you may have and request assistance when needed, a commitment to your manager on what you are going to achieve that day, potentially a short team meeting to review overall team progress, working on your actual tasks as set for the team..
Once a week you can also expect to have a coaching session on your performance as well as demo your work to our internal or external clients.
How do you measure the productivity of a team?
We do not measure the productivity by technology. Every team has a metric which they deliver against; by default, every person within the group is measured by the same metric on a weekly basis. For example, the metric for our maintenance team is “number of bugs fixed.” The cost per unit of the maintenance team on a weekly basis is the total headcount cost of the team for a week divided by the number of bugs fixed during the same week.
I heard you have a tracking tool to monitor your teams, why do you use it?
One of the key objectives of our productivity tracker is for it to be used by our Crossover partners to log time and eventually get paid. We also record information about our Crossover partners to understand what tools and applications they are using. This helps us to build work patterns of our people and identify best practices which we can share with all our teams. As an engineer, we expect that you would be spending at least 80% of your time in your relevant IDE with the remaining 20% spent on email, meetings and reviewing documents.