Skip to content

How we work

An operating model you can read before you sign: how we select, how we govern delivery, how we ensure continuity and how we use AI.

Selection and seniority

Senior is a published definition. The standard below applies to every professional presented as senior.

Seniority standard

  • Proven experience with production systems
  • Architecture decisions documented and defended
  • Track record of mentoring other engineers
  • Clear communication with business stakeholders

Steps

  1. 1

    Technical screening of the candidate’s background

  2. 2

    Technical interview run by senior engineers, never by recruiters alone

  3. 3

    Hands-on exercise tied to the client’s context

  4. 4

    Final validation by your team before the start

Steps

Delivery governance

For us, governance is a set of rituals, metrics and roles — not a word on a slide.

Rituals

  • Planning and review with your team every cycle
  • Technical architecture review when structural decisions come up
  • Monthly steering meeting with the delivery manager
  • Defined escalation path for risks and blockers

Metrics we track

  • Lead time
  • Throughput
  • Rework
  • Defects escaped to production
  • Test coverage
  • Open risks and pending decisions

Continuity

Continuity is treated as a contractual commitment, with four layers: who directs the work, people, knowledge and contract.

Who directs the work

CG Tech directs the work and manages the people. That is why we can commit to replacements: replacing a professional is our responsibility.

People

A named backup for every critical role, following the product context before they need to step in.

Knowledge

Mandatory documentation: access, runbooks, architecture decisions, known debt and open items.

Contract

Replacement, overlap and notice periods written into the contract.

How a replacement works

  1. 1

    Notice

    Departure announced or change requested. Changing a key person on our initiative requires contractual prior notice.

  2. 2

    Backup picks up the context

    The named backup starts following the day-to-day work.

  3. 3

    Replacement presented

    A replacement of the same seniority presented within the contractual deadline.

  4. 4

    Overlap

    A period working alongside the outgoing person, at no cost to you.

  5. 5

    Validated handover

    Handover checklist validated by your team before the outgoing person rolls off.

Timeline of a professional’s replacement

Handover checklist

  • Access and credentials transferred
  • Runbooks updated
  • Architecture decisions recorded
  • Known technical debt listed
  • Open backlog items reviewed
  • Handover session recorded

Getting started

  1. 1

    Kickoff with goals, acceptance criteria and metrics

  2. 2

    Access, environments and existing documentation

  3. 3

    Small first deliveries to calibrate the pace

  4. 4

    First weekly report and adjustment of rituals

Getting started

Governed AI

  • Client data and code are not used to train models
  • Every AI-generated suggestion goes through human review
  • Approved tools listed in the contract
  • AI use recorded and traceable in the delivered code

Security, LGPD and contracts

Map your team’s continuity risks

You leave the conversation with a risk map, even if you don’t hire CG Tech.

We reply to the email address you provide.