Android Chief Software Architect$ 100k/Year ($ 50/Hour for 40 hours of productive work per week) Remote Position Long-term
Want to learn how to guide a talented pool of architects to come up with new ideas to continuously improve our cloud-based SaaS systems and solve business problems?
Are you inspired to drive up the code quality for our 100+ products portfolio? Interested in utilizing your years as a Android Chief Architect to help to solve anti-patterns and increase our customers’ experience? You may want to join a team which is revamping all the front end technologies of our products. If yes, then this role may be for you.
You will work on a variety of products in various industries, work with top talent, and be on some of the most interesting technical projects which you may find. Your mandate is to redesign front ends, improve code quality, shrink the code, release products every week.
-Carlos R, Chief Architect
As an Android Chief Software Architect, you will be a crucial member of one of the central assembly line teams such as the easier team. You may also be in the role of a product Chief Architect, responsible for a product’s quality and weekly release.
As a member of the easier team, you will be assisting in the rebuild of the user interface of legacy products to a standard tech stack. This means you will build new screens with a modern UI and enhanced usability. You will also create the REST API layer required to connect the new UI with the product legacy backend and business logic. You will also be required to deliver UI unit tests, REST API unit tests and integration tests, and functional browser compatibility testing.
In all cases, you will have aggressive daily and weekly targets to work against, and you can expect to receive timely feedback about your performance. The frequent feedback is used to help you improve immediately and to resolve blockers which may be slowing down your performance.
Achieving an expert level understanding of our customers’ environments and their use of our products
Architecting and leading technical delivery of one or more products and match the needs of the target customer base
Creating solutions architecture, algorithms, and designs for solutions that scale to the customer's enterprise/global requirements
Mentor Front end architects and engineers to deliver high quality of code
Deliver a consistently high-quality product which has a high “First Time Acceptance Rate” from the engineering leadership.
Comply with Chief Architecture process playbooks
Working a standard 40-hr week and mostly Monday to Friday
Keep up to date with the latest software engineering trends
We believe in continuous growth and strive for constant 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 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 into the use of WorkSmart Pro, where you can learn how to improve your efficiency during your standard working day.
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 software architect skills by interacting with the top 1% global technical talent.
Work ExamplesEvery job creates excellent work. We want to show you the types of things you will learn, using real work examples of the processes, training examples, playbooks, projects you will build on the job.
Easier development Playbook
This is a copy of the playbook used by our Easier team. Take a look at the processes and methods used by the team
Relevant Files and LinksHere you can find external resources relevant to this role.
How can a Android 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 Android 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 Android 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 an Android 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 Android team?
We do not measure the productivity by technology. Every team has a metric which they deliver against; by default, every person within the team 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 log 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.