Loading…
turnkeyafricaFrom company careers page
Lagos · Internship · Lead · Posted 19 Oct 2026
JOB DESCRIPTION
Entry Level Backend Engineer
Caava Group · Group Technology · Evolve Platform
Reports To
Technical Lead of the assigned Evolve team
Works With
Backend and Frontend Engineers, QA Engineers and Product
Scope
Assigned Evolve backend features, bug fixes, testing and release support
Tech Stack
Java, Spring Boot, REST APIs, SQL and Git
Growth Path
Associate Software Engineer, based on performance and business need
Role Purpose
Evolve is Caava Group’s insurance management platform, built on Spring Boot services with Angular and Next.js frontends, and used by AIICO for its insurance operations. Working with experienced engineers, you will implement clearly scoped backend changes, test and debug services, and build practical knowledge of insurance workflows and dependable engineering practice.
This entry-level role suits candidates with internship, academic or personal project experience. Technical decisions, code reviews and production changes are supported by experienced team members. Growing towards full-stack work is encouraged.
Career Path
Progression to Associate Software Engineer depends on consistent delivery against these measures, growing independence on larger tasks, code and test quality, and business need.
Core Accountabilities
Build and maintain Evolve services
Test changes and work through code review
Investigate issues and communicate clearly
Apply secure practices and support releases
Key Performance Indicators
KPI
Measure
Target
Sprint delivery
Original sprint items Done by sprint end ÷ items committed at sprint start × 100.
≥85% each sprint.
Test completeness
Agreed unit and integration cases executed for each change.
All agreed cases run; failures resolved or accepted by the Technical Lead before merge.
Release quality
Own released changes linked to a production defect or rollback ÷ own released changes × 100.
Proposed: ≤10% over a rolling 4 weeks; 0 critical defects.
Code review
Peer PRs reviewed and time to first response on assigned reviews.
3–5 reviews per sprint; <6 working hours.
Docs and handover
Changes affecting APIs, setup or support behaviour with notes updated before handover ÷ such changes × 100.
100%.
Review weekly with your lead: sprint measures are scored per sprint and release quality over a rolling 4 weeks. Snapshot scope at sprint planning and record changes separately. Report N/A where no work is eligible. Proposed targets are confirmed after the first quarter of data.
Experience and Working Style
Working Style
Nice to Have
Listing gathered from the employer's careers page by freehire.me.