You wouldn’t try to win a race in a pair of hiking boots

Below, you can find a few examples of pre­defined team setups that we’ve found best suit the most common cases we work with, from small improvements up to core product de­velopment.

Below, you can find a few examples of pre­defined team setups that we’ve found best suit the most common cases we work with

  • Need a Core Team?

    • Team lead
    • Senior backend (DB)
    • Senior backend (frameworks/code)
    • Senior frontend (Javascript)
    • Senior frontend (HTML/CSS)

    Development of a product from scratch to a production-ready so­lution within an agreed pe­riod and to a high stan­dard.

  • Or a Feature Team?

    • Feature lead
    • Senior backend
    • Senior frontend

    Supports an existing pro­duct de­velopment team with se­parate feature de­velopment. Or, alternatively, can create an MVP in a short time with great technical scalability.

  • Maybe a Task Team?

    • Middle/senior full-stack

    Supports an existing product de­velopment team with de­velopment tickets.

  • Or just a Support Team?

    • Junior full-stack

    Supports an existing pro­duct de­velopment team with occasional de­velopment tasks or bug fixes.

Quick Reference

  • Team leader - provides guidance, inst­ruction, di­rection and leader­ship to the team in order to achieve the best re­sults. Features, tasks and priorities are assigned to the team leader di­rectly from your managers. Is responsible for en­suring that the pro­duct is de­veloped on time.
  • Feature leader — leads the de­velopment of a spe­cific feature for the pro­duct. Res­ponsible for overall feature de­velopment and de­livering it on time.
  • Senior developer — an experienced de­veloper fo­cused on a spe­cific area (backend/frontend). Responsible for the under­lying archi­tecture of the soft­ware program, as well as over­seeing the work being done by any other soft­ware engineers on the project.
  • Middle developer — a programmer with strong technical expe­rience, but without ma­nagement expe­rience. A good fit for on­going sup­port or feature de­velopment in com­bination with senior de­velopers. Responsible for task de­velopment.
  • Junior developer — implements small tickets, bug fixes and odd jobs. Has the potential to accrue enough experience to become a senior de­veloper, meaning that long-term cooperation can lead to gaining a senior de­veloper with an intimate knowledge of a given product.