Assignment description 

For this assignment we are looking for a person to fill the position of Area Tech Lead at our client in Stockholm.

In the role you will enable delivery of business objectives by taking high impact decisions within assigned business areas, or making it clear how areas and teams can take aligned technical decisions. You will be a change leader and connector, needing good communication skills for both upwards and downwards management. As well as be the technical conscience of the area, managing, communicating and prioritizing tech debt against business priorities.

As the Tech Lead you will have the Final say on area level tech decisions if needed, and point of conflict resolution when needed. You will also be the owner of technical debt across teams that each team individually cannot remove, and driver of initiatives to reduce debt to acceptable levels.

Main responsibilities:

• Collect, combine and distill information in order to deliver high level technical designs to support key business objectives
• Participate in area tech lead forum, reviewing and discussing future directions, requirements and principles
• Making sure teams have and understand which capabilities they are responsible for within an area (can decide if needed), helping them deliver on desired business outcomes by loosely coupled designs
• Support and guide development, including coaching and mentoring teams and tech leads
• Engage with product and engineering directors to ensure delivery of business and tech objectives
• Organise and lead meetings and workshops around technical design, tech streams etc across teams within area
• Drive alignment with strategic and business objectives and follow through on decisions, requirements and principles
• Monitor the continued evolution of best practices, changes in the technical solution space, and internalise when it creates value
• Evaluate technical capabilities together with team tech leads, and decide on actions
• Read and understand code (should not be part of the critical path of a team, and coding should be more PoC and tooling related. Most of the time will not be spent on coding, but helping teams.)
• Contribute up to 25% of their time outside their area, often on topics decided by principal engineers