Engineers have aggressive daily and weekly targets set for them and are required to work a standard working week with us. 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.
-Apparao A, Software Architect
Our factory is designed to deliver great quality at high pace. In every team that you work in you will be expected to deliver work to a high level of quality. Your work quality is measured through the First Time Acceptance Rate, which means passing the code review quality bar set by Chief Architects.
The code review team spends most of their time reviewing pull requests created by other teams. Members of the team review code which may be written in a variety of frameworks and tools. The members of this team are not product specialists but are expected to have very high coding standards, be able to clearly articulate what is wrong with a developers code and be able to defend their findings of poor quality code.
The easier team rebuilds the user interface of legacy products in our standard tech stacks and build new screens with a modern UI and enhanced usability. The team also creates 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 daily and weekly feedback about your performance. The regular feedback is used to help you improve immediately and to resolve blockers which may be slowing down your performance.
Provide feedback to the engineering leadership on areas of the software development process which can be improved or automate
Deliver a consistently high-quality product which has a high “First Time Acceptance Rate” from the engineering leadership.
Comply with engineering process playbooks
Ensuring that your output meets the teams quality bars before being passed on to further stages within the process
Meeting your goals, which are set by your manager, on a daily and weekly basis
Escalating issues to your manager as soon as a risk is identified or as soon as you are blocked in your work
Working a standard 40-hr week and mostly Monday to Friday
Keep up to date with the latest software engineering trends
Become a specialist in some of the parts of our software factory model, such as the development of automated unit test or bug fixes
How to have an obsessive focus on quality; constantly focus on improving the quality of your work and the quality of products
Measure your quality through the use of First Time Acceptance Rate
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
Through the use of worksmart pro,learn how to improve your efficiency during your standard working day
Master your software engineering skills by interacting with the top 1% global technical talent
The learning responsibilities belong to you. However, we can provide support and adequate content to help you. To be able to work with new technologies, you will need to re-apply and take the specific tests on the desired technology stream.
Besides the apparent technical knowledge required to do the role, and keeping yourself up to date with the latest technology updates, you should also have a comfortable and quiet environment to work from. You should set a good calendar for your week which is repeatable and which allows you to dedicate long blocks of time towards your work with Crossover.
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.
Do you use Agile?
Like most organizations, we make use of subsets of Agile. The one key difference though is that our teams are highly specialized in the task they do. For example, we have a maintenance team whose only task is to fix bugs on our products. Rather than being product specialists they are process specialists.
How can I get promoted to new roles?
In order to move across roles you need to apply through our crossover portal. From a Software Architect you may apply for a Chief Architect role. You should also be ensuring that your manager is always knowledgeable about any active applications you may have