(RD) Lead Principal Backend Engineer

The job in short

As Lead Principal Software Engineer you have an active role in defining and driving our technical vision. Through your role, you take the product to the next level, while improving related processes and empowering teams and other Software Engineers. Ensuring our solutions are tested, accessible, extensible, maintainable, secure and perform well, you drive the completion of deliverables. You are the go-to person for all Backbase departments thanks to your functional expertise. You act as a role model and a mentor for other Software Engineers and provide guidance in their development. Staying up-to-date with industry trends, competitor analysis, team compositions, you ensure we are well-prepared and dynamic.

Meet the job

You help the organisation to define and ensure the technical vision is known and implemented in development activities. You drive prototyping and validation of new architecture and technology ideas, ways of working, efficiency gains and refactoring initiatives.

Working across departments, foster collaboration, and are the face of our product vision and success internally and externally. You also interact with teams from pre-sales and customer success to ensure technology feedback from customers and field engineers is incorporated. You provide advice based on experience and deep technical understanding of software development, practices and frameworks.
Leading by example, defining our way of working and our path to success, you take on the expert role in all topics related to Backend.

How about you?

● Min 12 years of experience in a similar role;
●Bachelor in Information Technology, Computer Sciences or similar/related technical field, or equivalent practical experience;
●Experience with leading large teams, coaching team leads not only technically but how to be great leaders as well;
●Excellent English speaking, writing and presentation skills.

Role Competencies

Knowledge & Application:
●Meets all technical expectations of previous levels, working across their chapter, the guild and the organization;
●Able to make the right judgement what to focus on and what to delegate;
●Has expertise in a set of related team's domains, including the breadth of services, how they interact, and data flows between systems;
●Conducts test analysis and takes a proactive role in the formulation of quality considerations, that apply to strategic product and architectural decisions;
●Contributes to the testing frameworks for the organisation. Mentors less senior engineers on test automation.

Complexity & Problem Solving:
●Spends less and less time coding or on other sprint tasks, more and more time on design, planning, architecture;
●Spend most of the time to define/implement the organisation strategy/vision;
●Proficient at using systematic debugging to diagnose all issues within a set of related domains;
●Has a helicopter view of the product and influences the definition of the testing approach and strategy of the teams in their product line and in the wider organisation;
●Writes automated test cases in different testing levels for the whole system under test.

Collaboration & Interction:
●Acts as a bridge between their value stream and external groups (guilds, RnD, CS, customers);
●When asked and if needed they works with the security team, as well as across several teams, to apply the organization's security strategy;
●Fosters a security first mindset across those teams, leading by example;
●Fosters a culture of observability across several teams and helps them use operational data to improve stability, performance and accessibility of their domains;
●Works across teams to foster a culture of architecture that allows for iterative, autonomous development and future scaling;
●Guides several teams in anticipation of future use cases and helps them make design decisions that minimize the cost of future changes;
●Works across departments;
●Interacts with teams from pre-sales and customer success to ensure the technology feedback from customers and field engineers is incorporated into product;
●Establishes strong and trusted relationships with customers, internal and external stakeholders;
●Works across departments ensuring a unified adoption of existing tooling and processes;
●Aligns with stakeholders to ensure dependencies are met and there is sufficient reuse of processes and tooling across the organization.

Supervision:
●Reviews cross-team work critically and ensures it’s appropriately broken down and prioritised, and well understood by all involved teams;
●Ensures cross-team dependencies are noted and well understood by all teams involved and other relevant stakeholders;
●Works across teams to foster a culture of priority setting and urgency in alignment with organizational strategy;
●Takes overall responsibility and accountability for the quality of their product line.