Portfolio CTO, gt.school (Remote) - $640,000/year USD

We believe in continuous growth and strive for constant improvement. As part of our CTO family, you will be exposed to a multitude of new technologies, products, and industries on a daily basis, and our comprehensive suite of playbooks will equip you with the foundation to develop and enhance your existing expertise.

We also provide a unique CTO-Level Remote Camp for all new hires. This full-time, fully-paid training program covers all of the unique aspects within our approach to Cloud Architecture and Design, including:

• SME engagement and how to elicit the important information
• How to uncover CIV (Challenging, Important or Valuable) Problems in a particular domain/industry
• How to define Core Functions to address CIV problems and ensure optimal product-market fit
• How to make the Important Technical Decisions to ensure that:
• Core architecture decisions are not left to chance
• Core functionality will be delivered effectively
• Architecture and development teams are not micro-managed by imposing unnecessary constraints (low-level, unimportant decisions)

Throughout your training, you will get daily feedback to accelerate learning and growth far beyond typical classrooms or training programs.

Our curriculum includes a number of bite-sized training videos where we explain how we design great software. Here’s an example where we show you how to make and validate Important Technical Decisions.

How do you enhance an application that is expensive to maintain? We believe that before adding features to a product, it is vital to ensure that it has a simple and strong core. We acquire dozens of products each year that aren't simple and don't have a strong core. The first thing we do is to challenge ourselves to rebuild the entire product using today's cloud services and patterns in under 5,000 lines of code. This challenge helps us quickly get to the core and identify all the gems that can't be replaced with off the shelf software and services.

Our approach begins with writing the spec to build the existing product as-is. The purpose of this "Technical Teardown Spec" is to document what is core and why all the important technical decisions (ITDs) were made. Sometimes, historical decisions are made for a great reason that still holds true today. Often we'd do things differently. While we write the teardown spec, we inject our opinions and insights alongside the facts we've learned. 

Once the technical teardown is complete, we write the Prod2 rebuild spec that describes the important decisions necessary to rebuild the product in 5k loc.

These are examples of specs our organization has produced for Sococo:

• Sococo - Technical Teardown
• Sococo - 5k Rebuild spec
• Sococo - Prod1 Milestone 2