Skip to content
Chongsong
Sign inRequest access
Member sign in

ChongsongAI, Bittensor & software engineering

An engineering company, with a ladder you can read.

Chongsong Econ & Tech Cooperation Co. works in AI, Bittensor and software engineering. Members build their own income through job applications, Bittensor work and freelancing, with support from the company, and move from Student to Principal Dev along a ladder where every level has a stated way in.

Request accessMember sign in

Newcomers request an account; an admin accepts it.

Fig. 1The developer ladder
  1. Student1st-semester entry
  2. InternFrom 2nd semester
  3. Junior Dev6 mo Intern, or graduate
  4. Senior Dev+ PM trackCEO's decision
  5. Staff DevCEO's decision
  6. Principal DevCEO's decision
Each level has a stated way in.From Senior Dev: outcomes, not hours
Disciplines
3
AI, Bittensor, software
Developer levels
6
Student to Principal
Project stages
7
Pitch to outcome
Trial period
2 mo
One optional month more
01What we build

Three disciplines, one technical direction.

Our technical work spans AI, Bittensor and software engineering. The CTO leads all three and writes the official plan for every project we take on.

  • AI

    AI engineering, with technical direction from the CTO.

  • Bittensor

    Work on the Bittensor network. For qualifying developers, the company also invests in Bittensor mining, in limited amounts.

  • Software engineering

    The craft under everything else, practised in company projects and in members' own freelance work.

How members build income

Members earn on their own account, through three routes, with support from the company.

  1. 01

    Job applications

    Applying for jobs, with support from the company.

  2. 02

    Bittensor work

    Earning from work on Bittensor, with limited company investment in mining for qualifying devs.

  3. 03

    Freelancing

    Freelance work, supported by the company.

02Progression

A path you earn.

Six developer levels, each with a stated way in. Early on, time and approved hours and points set the pace; from Senior Dev up, every promotion is the CEO's own decision.

  1. 01

    Student

    sem 1
    Way in

    Entry in the first semester.

  2. 02

    Intern

    sem 2+
    Way in

    From the second semester.

    Asks

    4 approved company-work hours and 40 approved points per working day.

  3. 03

    Junior Dev

    6 mo
    Way in

    Automatically after 6 continuous months as Intern, or by direct entry after graduation.

    Asks

    8 hours and 100 points per working day.

  4. 04

    Senior Dev

    CEO
    Way in

    When the CEO decides you are ready, on their own judgement.

    Asks

    Works by outcomes, with no mandatory hours. May apply for the PM track.

  5. 05

    Staff Dev

    CEO
    Way in

    By the CEO's decision.

  6. 06

    Principal Dev

    CEO
    Way in

    By the CEO's decision.

The PM track

Any Senior Dev may apply to lead.

PMs run approved projects, build the team and coordinate revenue allocation. Staff PM and Principal PM are the CEO's decision.

  1. 01

    Senior Dev

    Applies to lead

  2. 02

    PM

    By application

  3. 03

    Staff PM

    By CEO decision

  4. 04

    Principal PM

    By CEO decision

03How a project runs

One path for every project.

From pitch to outcome in seven stages, with the CTO, CEO, PM and COO each owning one. New work starts as a trial, so an idea earns its place before it becomes ongoing.

  1. 01

    Pitch

    An idea is put forward.

  2. 02

    C-Level meeting

    Leadership weighs it together.

  3. 03

    CTO plan

    The official project plan.

    CTO

  4. 04

    CEO approval

    Final authority signs off.

    CEO

  5. 05

    PM execution

    The PM runs it and builds the team.

    PM

  6. 06

    COO monitoring

    Operations keeps watch.

    COO

  7. 07

    Outcome

    The CEO marks it successful, ongoing or failed.

    CEO

Trials first

A new project runs as a two-month trial, with one optional one-month extension. Then it becomes an ongoing project, or it closes.

Project types

  • PM Trial Project
  • Solo Trial Project
  • Ongoing Project
Fig. 2Trial lifecycle: a two-month trial, an optional one-month extension, then Ongoing or Closed.

Every trial ends in a decision, and the decision goes on the record.

04How we work

Written rules. Clear roles.

The rules are written down, and every role has a stated remit. These are the ones every member works under.

  • § 1

    Outcomes over hours

    Senior Devs work by outcomes, with no mandatory hours. Interns and Junior Devs have set daily hours and points instead, so everyone knows what is expected.

  • § 2

    Revenue split by consent

    A project's revenue split must be agreed by every participating developer before it reaches the CEO.

  • § 3

    Every decision on the record

    Every approval and decision is written to an append-only audit trail. Nothing is quietly changed after the fact.

Who does what

Five roles, each with its own remit. Approvals go to the role that owns them.

CEO / CFO
Company direction, final authority and financial control.
CTO
Technical direction across AI, Bittensor and software engineering, and the official plan for every project.
COO
Project operations, coordination of PMs, and monitoring of work in progress.
General Manager
Daily operations, member welfare and work-time administration.
PM
Runs an approved project, builds its team and coordinates revenue allocation.
05Learn together

Share what you know. Dig into what's next, together.

Experience is shared through internal presentations: members teach what they have learned on real projects, and the team digs into cutting-edge AI, Bittensor and software engineering together. The CTO runs the programme, and Senior Devs also mentor Junior Devs and Interns.

  1. 01

    Propose

    Anyone can propose a presentation to the CTO: the topic, who presents it, a date and a room.

  2. 02

    Accept

    The CTO accepts it, moves it to another date or room, or declines it, and manages it from there. Only an accepted presentation is published.

  3. 03

    Learn together

    A short internal course of 60 to 90 minutes, open to every member to join, then kept on record with the rest.

On the edge, together

Every presentation draws on the work itself: the AI, Bittensor and software engineering the company builds.

  • AI
  • Bittensor
  • Software engineering
Format
60–90 min internal course
Given by
Any member, accepted by the CTO
Open to
Every member, once accepted

Find your step. Then earn the next one.

Members sign in to the internal system. Newcomers request an account, which an admin reviews and accepts.

Request accessMember sign in