About the job
About iwoca
At iwoca, we recognize that small businesses need to stay agile in a fast-paced environment where opportunities can arise unexpectedly. Cash flow challenges can emerge overnight, and that's why we provide financing solutions that are as flexible and responsive as our clients.
Our innovative technology, combined with our data-driven approach and exceptional customer service, empowers business owners to make informed decisions with speed and confidence. We have successfully facilitated over £4 billion in funding for over 100,000 businesses, and we are committed to supporting even more SMEs in their critical moments.
Our mission is to assist one million SMEs in achieving their goals, creating a lasting impact on local communities and economies.
The Credit Risk Team
Our Credit Risk team is responsible for the development and maintenance of the technology and models that drive our lending decisions. This includes credit scoring, scorecard development, and portfolio monitoring, all aimed at maximizing lending volume while managing risk effectively.
With nine data scientists, four engineers, and two strategy analysts, our team collaborates to analyze historical data, build robust models, and translate insights into actionable lending decisions.
Your Role as Tech Lead
As the Tech Lead, you will oversee the engineering systems that support Credit Risk modeling at iwoca. Your focus will be on enhancing the platform, pipelines, and production systems rather than directly building models. This role combines hands-on technical leadership with line management and individual contribution.
Responsibilities:
Guide a team of four engineers in delivering high-quality solutions for the modeling platform and its associated systems.
Elevate engineering standards across modeling systems with an emphasis on reliability, observability, and safe changes.
Define the technical direction by comprehending interconnected systems and workflows to prioritize the right challenges.
Individual Contribution
Maintain an active role in the codebase, particularly during periods of ambiguity or complex problem-solving.
