Skip to main content
Institute of Advanced Technological and Commercial Studies

Careers

Development team lead

Moving from developer to team lead changes the job more than people expect: you write less code and build more conditions. Architecture, quality, growing your teammates, holding delivery commitments.

Building the conditions for others' work

The day splits across three responsibilities. Technical: settling an architecture, arbitrating debt, guaranteeing that what ships holds up. Human: supporting a teammate, running a demanding and generous review, hiring. Commitment: breaking down a request, estimating honestly, holding a date or warning early. The most decisive skill is the last — saying in time what will not be ready beats discovering it the night before.

  • Settle an architecture and document the decision taken
  • Run a demanding code review and help a teammate grow
  • Break down, estimate and hold a delivery commitment
  • Hire, onboard and organise the team's skill growth

Teams that are getting structured

  • Software vendors and digital service platforms
  • IT departments of banks and operators
  • Digital services companies running client projects
  • Startups moving from three to fifteen developers
  • Distributed teams working for foreign principals

What the commitment represents

Training takes time, and that time can be counted. Here is how many months, how many taught hours, how many credits, and for what recognised level of responsibility. You can set these figures beside your professional calendar and decide with full knowledge, which is the only way to see a programme through.

Manager and professional

qualification level
6
months of programme
12

Led by an instructor.

taught hours
800 h

1 credit = 25 h of work, 10 of them taught.

credits
80

Framework of the « Development Team Lead » qualification, code TP56.

competency blocks
5

The programme, exactly as filed

What you read here is the filed content, with no marketing rewrite. Each block carries its official title, its scope and its taught hours. It is the document a panel consults, the one an employer receives when funding, and the one the final certificate rests on.

Competency blockWhat it coversTaught hours
Architecture and software qualityArchitectural choices, technical debt, standards, review, testing, application security210 h
Steering deliveryCadence, estimation, scope commitment, continuous integration, release200 h
Technical leadershipAllocation, skills growth, constructive review, technical hiring190 h
Business relations and trade-offsTranslating needs, cost-time-quality trade-offs, a reasoned refusal150 h
Managerial conductProtecting the team, reporting, deciding on incomplete information50 h

From code to leading a team

The path to this occupation is chosen on facts: how long, how many hours with an instructor, how many recognised credits and what amount in Guinean francs. The table gathers them for every open option, in the order a candidate reviews them before filing an application.

ProgrammeDurationCreditsTaught hoursFees
Computer Science programme — Bac+3 level · Bachelor's degree3 years1801800 h5 400 000 GNF per year
Management and Project Management programme — Bac+5 level · Master's degree2 years1201200 h6 500 000 GNF per year

Useful to know before you apply

Do I have to stop coding?

Practice is maintained, in reduced doses, because it preserves credibility and clear-sightedness on estimates. What changes is the split: time spent removing others' obstacles becomes the main activity, and that is what the qualification recognises.

What follows this level?

The chief technology officer, at level 7, carries technology strategy, structuring choices and budget. The enterprise architect, also at level 7, offers the other trajectory, centred on the coherence of the application estate.

Development team lead — Careers | IHETC — IHETC