In my career, I have had the opportunity to interact with engineers from all levels. Often, they ask me what they need to get to the next level. It is not an easy question to answer or to explain as it is hard to visualize the complexities of software engineering. Still, the other day, when my wife, an architect, asked me the difference between the levels of individual contributors (IC), I knew I had to explain it in a way that resonated with her world. So, I used a construction and architecture analogy. Here’s how I broke it down to her — and how it’s become my go-to explanation ever since.

IC1 and IC2: The Apprentices

Think of Associate Software Engineers (IC1) and Software Engineers (IC2) as the apprentices on a construction site. They might be helping with drywall, painting, roofing, or wiring. They know how to swing a hammer and connect a wire, but they need someone more experienced to guide them. They’re learning the ropes and building the foundational skills they’ll rely on throughout their careers.

In software, they write code, debug, and perhaps even contribute to small features. They’re doing important work, but they’re not expected to take the lead just yet. It’s all about gaining experience under the guidance of senior engineers.

IC3: The Certified Professionals

Senior Software Engineers (IC3) are like certified electricians or plumbers. They’ve mastered their craft and can be trusted to complete tasks independently. If a house needs rewiring, the electrician knows exactly what to do. Similarly, IC3 engineers can tackle complex features, debug challenging issues, and handle production incidents without constant supervision.

At this stage, engineers are no longer just following instructions; they make decisions and ensure the work meets professional standards.

IC4: The Contractors

When you reach Staff Software Engineer (IC4), you’re the contractor who can lead a team of specialists to remodel a house or even build one from scratch. You’re not just focusing on one job, like plumbing or painting; you’re overseeing multiple disciplines, coordinating efforts, and ensuring the result is a cohesive structure.

In software, IC4 engineers are taking on large-scale projects that touch many parts of the system. They’re often the go-to for cross-functional initiatives, ensuring everything works seamlessly.

IC5: The Architect

Senior Staff Software Engineers (IC5) step into the role of an architect. They’re not hammering nails or laying tile; instead, they’re designing the blueprints for the house. They’re thinking about the big picture: how the foundation supports the structure, how the plumbing and wiring interact, and how to make the house functional and beautiful.

These engineers are focused on high-level design, creating scalable systems, and setting the technical direction for entire teams. They ensure that all the components built by contractors (IC4s) and other engineers fit together perfectly.

IC6: The Urban Planner

Principal Software Engineers (IC6) are like architects who design office buildings or small apartment complexes. They’re responsible for systems that serve multiple tenants, each with unique needs. They ensure the infrastructure supports everything from elevators to HVAC systems, considering present needs and future growth.

In the tech world, IC6 engineers work on large-scale systems that serve multiple teams or products. They think about scalability, reliability, and how to future-proof the architecture.

IC7: The Community Designer

Distinguished Engineers (IC7) take it to the next level. They’re like urban planners designing entire communities, including roads, parks, utilities, and zoning laws. Their work impacts thousands, if not millions, of people, and their decisions must last for decades.

In software, IC7s shape the technical vision of entire organizations. They’re responsible for systems that span multiple teams and departments, solving problems at a scale most of us can only imagine.

IC8: The Skyscraper Visionary

Finally, we have Engineering Fellows (IC8). These are the architects who design skyscrapers. They deal with unique challenges like wind resistance, altitude, and environmental factors. Their work defines skylines and pushes the boundaries of what’s possible.

For IC8 engineers, this means working on groundbreaking technologies or systems that few others are qualified to tackle. They’re the pioneers, the visionaries, and the ones who leave a legacy in the industry.

The Bigger Picture

When I explained this to my wife, she smiled and said, “So, you’re saying software engineers are like builders, but instead of houses, they create digital worlds.” Exactly. Every level of an IC has a role, from laying the first brick of code to designing systems that touch millions of lives. And just like in construction, the collaboration between these roles makes it all possible. It is hard to visualize the complexity associated with building software, even though the comparison is not one-to-one; this analogy helps to visualize what might be needed to reach each IC level.

Next time someone asks me about the different levels of ICs, I’ll probably share this analogy. After all, we all are building dreams — whether they’re made of bricks or bytes.