Principal Software Architect, Trilogy (Trilogy Principal Software Architect)

Description

Every technical decision-maker has the same gripes. The architecture is outdated. Past product decisions don’t make any sense. Technical debt is mounting. Plus, the higher you rise in your organization, the less time you get to spend actually doing the technical work you love (and the more time you spend managing the people who are doing it).

Not at Trilogy.

In this Product CTO role, you’ll have carte blanche to make architectural decisions based on technical merit — not whatever decision the board decided was most cost-effective. No more working on the same product every day for years, wishing you could go back in time and backhand whoever thought it was a good idea to write custom code for something that could’ve been purchased from AWS for $20/month.

Instead, you’ll design for a diverse portfolio of products (hundreds, in fact) using the newest, most interesting cloud technologies. As a senior technical decision-maker, you’ll face a new architecture challenge each week and make important architectural decisions every day. Instead of tending to multiple stakeholders and a wishlist of features from customers, you decide the critical features for the product. Use and grow your expertise to design products for maximum performance, efficiency, and scale.

Ready to get back to doing the technical work you love, while guiding the development for products that reach millions of customers?

What you will be doing

Tackling design problems and writing technical specs to create products for distinct tech stacks and business domains.
Uncovering “high-order bit” decisions by interviewing technical leads and analyzing data structures and code/design documents.
Making important design and technical decisions that specify how to rearchitect products in a cloud-first way on systems such as AWS and GCP.

What you will NOT be doing

Managing projects or employees — thanks to Trilogy’s highly automated processes and streamlined org structure, there’s very little time spend on this type of admin
Participating in daily scrum meetings, making low-level decisions, performing code reviews, or debugging
Talking to customers (while you’ll build products customers love, other roles in the organization will take care of these important interviews for you!)
Developing a backlog of wishlist features
Creating high-level strategies or roadmaps — instead, you’ll be making the rubber-meets-road tech decisions

Candidate requirements

7+ years of experience making important architecture and design decisions on software projects, such as the application of architecture design patterns or significant open source technologies.
Experience making technical design decisions involving the use of cloud computing services
Experience making technical design decisions for complex software products or systems
Ability to simplify complex ideas and communicate them in writing with clear and logical thinking

Frequently asked questions

About the role

Who is successful in this role?

How many products does each role manage? What is the typical size of each product team?

How do you measure success in this role?

Do you use a common tech stack across the portfolio of products?

About Crossover

Am I eligible to apply for a job on Crossover?

How is the pay calculated?

What are the employee benefits?

How much English do I need?

Why do I have to pass difficult assessments?

How will my productivity be monitored?

View All FAQs

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:

Watch Interview

Isuru | Software Engineer

Sri Lanka

Isuru saves two hours a day by cutting his daily commute around Colombo, Sri Lanka's capital. Working remotely as a Software Engineer for Tr...

Meet Isuru

Reviews

View All Reviews

Meet some people who've landed similar jobs

Matheus | Frontend Software Architect

Brazil

Matheus comes from a tiny town in Brazil, and thought his dreams were only possible for rich people. But he was determined to find a way.

Meet Matheus

Alex | Dynamo DB Expert

United States

Alex now consults for Trilogy, where he coaches the world's top remote software engineers. He lives in Nebraska, USA.

Meet Alex

Krystian | VP of Software Engineering

Poland

Krystian started his career as a Senior Software Developer at Trilogy five years ago. Now as a VP of Software Engineering, he's now responsi...

Meet Krystian

Principal Software Architect
$400,000 USD/year ^{Pay is set based on global value, not the local market.

Most roles = hourly rate x 40 hrs x 50 weeks}($200 USD/hour)

Description

What you will be doing

What you will NOT be doing

Key responsibilities

Candidate requirements

Meet the hiring manager

You will be working for

Quick links

Meet a successful candidate

Isuru | Software Engineer

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

Pass Cognitive Aptitude Test.

Pass English Proficiency Test.

Prove Real-World Job & AI Skills.

Ace An Interview Or Two.

Accept Job Offer.