Tech Lead
Brief Description:
Tech Lead — Head of Development – 5 team members – Fintech product – Astana – Hybrid/Remote format – Reports to: CPO.
About the product:
A fintech product for clients/users, addressing financial scenarios where reliability, security, and predictability are critical. The role is open due to product development and the need to strengthen technical leadership. The Tech Lead is responsible for the product team (5 people) and its technical development. The main challenge over the next 12 months is to ensure sustainable product development, scale engineering practices, and mitigate technical risks. Decisions regarding architecture, tech stack, engineering practices, and team composition are your responsibility within the agreed-upon strategy.
Example of what success will look like in 6-12 months:
– Releases are released at an agreed-upon frequency and with a predictable lead time.
– Critical incidents are handled with RCA, recurrence is reduced, and SLOs are met at level X.
– Key knowledge is distributed within the team, there is no critical dependency on a single specialist; the team is capable of independently solving basic technical problems.
Key Responsibilities:
1. Team Management
5 people in 1 product team: PM, Business Lead, Anti-Fraud, Operations, Developer.
● Build the structure and responsibilities of teams, set clear goals, and ensure transparency of priorities.
● Grow team leads and key specialists, reduce dependence on individuals, and build a sustainable engineering structure.
● Participate in hiring and make decisions on the technical aspects of selecting specialists for your team.
2. Technical Leadership
● Make and coordinate key decisions on architecture, technology, and engineering practices (e.g., split a monolith/transition services to a new architecture/scaling a platform).
● Responsible for the technical stability of systems
● Develop engineering standards: code review, testing, CI/CD, observability, secure SDLC, architectural documentation, and ADR.
● Organize incident management and postmortem/RCA, eliminate systemic causes of failures, and conduct technological research where they affect the product and architecture.
3. Planning and Delivery
● Work with the PM/PO and teams to plan delivery: estimate deadlines, technical complexity, dependencies, and risks.
● Manage the technical backlog and technical debt.
● Manage technology costs and infrastructure within budget.
4. Interacting with the Business and Clients
● Translate business needs into technical solutions and explain the costs, constraints, risks, and consequences of choices.
● Represent the technical position to stakeholders, defend architectural decisions, and, when necessary, argue "no" in a convincing manner.
● Escalate controversial decisions to another level.