Portfolio CTO
$640,000 USD/year Pay is set based on global value, not the local market. Most roles = hourly rate x 40 hrs x 50 weeks ($320 USD/hour)

Not accepting applications on crossover.com at this time.

Description

Are you an accomplished software architect who is hitting a ceiling in your company? Are you looking for the next step, perhaps a bridge to a high-level CTO role? If so, GT School is looking to build the next generation of educational software for gifted and talented ("GT") children, and we have a role for you!

We are GT School, and we are going to change gifted and talented lives forever. We believe educational software has become stale, and gifted children are missing out on enrichment that could change the trajectory of their future. We want to make the next generation of educational software for the top 10% of young learners. 

This role requires you to make long-term, strategic technical architecture decisions for our portfolio of educational products. You will review specs from Product CTOs and manage a specific portfolio of products. We're creating an educational software metaverse, and your decisions should last over a 10-year horizon.

If you're deeply technical – and you believe you have a great sense of where technology is trending and what it can do for gifted education – then we want to hear from you!

What you will be doing

  • Create full specs: learn about problems facing users and then make important technical and long-term architectural decisions using logic, data, and domain knowledge 
  • Coaching: provide written, technical, and actionable feedback to authors of technical specifications to improve the quality of their work

What you will NOT be doing

  • Managing an engineering team's day-to-day work
  • Making decisions without careful logic or showing your work
  • Speaking to customers

Key responsibilities

This role delivers a simplified product architecture via a series of important technical decisions to define a long-term roadmap for a next-generation educational software product and its features

Candidate requirements

  • Experience as the most senior technical design decision-maker for a software engineering organization of at least 150 people
  • 15+ years of experience making important architecture and design decisions on software projects
  • 2+ years of experience writing production-quality code

Meet a successful candidate

Watch Interview
Catalin Adler
Catalin  |  Subsystem CTO
Romania  

Catalin, Subsystem CTO, describes his experience at Crossover in one word: extraordinary. “Each week you get to learn a lot of new things: c...

Meet Catalin
How it works

Applying for a role? Here’s what to expect.

We’ve curated a series of steps that take the guesswork (and cognitive bias) out of recruiting the best person.

Pass Cognitive Aptitude Test.
STEP 1

Pass Cognitive Aptitude Test.

Pass English Proficiency Test.
STEP 2

Pass English Proficiency Test.

Prove Real-World Job Skills.
STEP 3

Prove Real-World Job Skills.

Ace An Interview Or Two.
STEP 4

Ace An Interview Or Two.

Accept Job Offer.
STEP 5

Accept Job Offer.

Celebrate!
STEP 6

Celebrate!

Frequently asked questions

About Crossover

What you will learn

We believe in continuous growth and strive for constant improvement. As part of our team, you will learn new technologies, products, and industries daily, 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 Remote Camp for all new hires. This full-time, fully-paid training program covers all of the unique aspects of our Cloud Architecture and Design approach. You will get daily feedback to accelerate learning and growth far beyond typical classrooms or training programs throughout your training. Our curriculum includes several bite-sized training videos explaining how we design great software. Here’s an example of how to make and validate Important Technical Decisions.

Work examples

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. When we acquire a product, we challenge ourselves to rebuild it entirely 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. This "Technical Teardown Spec" aims to document what is core and why all the important technical decisions were made. Sometimes, historical decisions are made for great reasons that still hold 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 rebuild spec that describes the important decisions necessary to rebuild the product in 5,000 lines of code.

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

Meet some people who've landed similar jobs

Why Crossover

Recruitment sucks. So we’re fixing it.

The Olympics of work

The Olympics of work

It’s super hard to qualify—extreme quality standards ensure every single team member is at the top of their game.

Premium pay for premium talent

Premium pay for premium talent

Over 50% of new hires double or triple their previous pay. Why? Because that’s what the best person in the world is worth.

Shortlist by skills, not bias

Shortlist by skills, not bias

We don’t care where you went to school, what color your hair is, or whether we can pronounce your name. Just prove you’ve got the skills.