---
title: "Discussion on \"8 signs you are on the way to becoming a software architect\" | Hashnode"
description: "Discussion on \"8 signs you are on the way to becoming a software architect\". A software architect is defined by a set of values and attitude. Every developer who joins a company secretly desires to be a Team Leader or Software Architect. So, what's the checklist? How do you know if you are on the way to becoming an architect?..."
url: "https://hashnode.com/posts/8-signs-you-are-on-the-way-to-becoming-a-software-architect/58f5edeeb168746ffba744b1"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [8 signs you are on the way to becoming a software architect](https://hashnode.com/post/8-signs-you-are-on-the-way-to-becoming-a-software-architect?utm_source=hashnode&utm_medium=feed)

A software architect is defined by a set of values and attitude. Every developer who joins a company secretly desires to be a Team Leader or Software Architect. So, what's the checklist? How do you know if you are on the way to becoming an architect?...

Apr 18, 2017 · hashnode.com  
Read the article

-   [#programming](https://hashnode.com/tag/programming)

## Written by

[Jack Kim](https://hashnode.com/@jack_kimO89)

@jack\_kimO89

  
[View profile](https://hashnode.com/@jack_kimO89)

## Responses 6

Markdown supported · ⌘↵ to post

[Snehal Kanzariya](https://hashnode.com/@geekdiv)

[Jun 11, 2017](https://hashnode.com/posts/8-signs-you-are-on-the-way-to-becoming-a-software-architect/58f5edeeb168746ffba744b1/comment/593cccd94286d443aa1d2cf8)

Wall said [Jack Kim](https://hashnode.com/@jack_kimO89 "Jack Kim's Profile - Hashnode") :)

[Adrià Castany](https://hashnode.com/@MrBrownser)

[Apr 26, 2017](https://hashnode.com/posts/8-signs-you-are-on-the-way-to-becoming-a-software-architect/58f5edeeb168746ffba744b1/comment/5900b6e353642a854cc0fe8a)

Hey nice post! Hardest skill for me is your #5, in my last job was at the time to speaking with the founders, changing the rhythm for a second, stop thinking technically and start seeing the BIG PICTURE. When you see it clearly, then you can organize for yourself all resources and can transmit the value and motivation to your team.

[Mev-Rael](https://hashnode.com/@mevrael)

[Apr 26, 2017](https://hashnode.com/posts/8-signs-you-are-on-the-way-to-becoming-a-software-architect/58f5edeeb168746ffba744b1/comment/5900b613a464d8d9977c9efc)

Well, it's very, very short marketing text which tries to sell "software architecture is easy and everyone wants to be an architect" which is not true. Yet it gives some basic points and I agree on all of them, however, they are true for any senior software engineer and solid team member and has almost nothing to do with software architect. It is also written from engineering perspective while there is also business perspective.

You have to **sacrifice** a lot, forget about perfect code, favorite tools, comfort zone, you have to operate with a limited budget, live in a real world, and every time adapt to situation and team you have or very often members/resources you don't have, your **main and only job is to deliver MVP of product or feature asap no matter what it takes**. Architect should understand business, speak business language very good, be a 50% tech sales person and be able to deliver notes to shareholders/top level executives, so yes, communication and presentation skills are #1 important but they are useless without the knowledge of the topics. Starting own business, selling, consulting would help to practice it.

I would also include a very important and missing point - "**design**" which also includes **design, architecture and other patterns**. Architecture is about designing and connecting, architect designs complicated system from scratch and **visual tools** are his main tools. You need to practice painting, diagramming, design thinking a lot, as well visualization of data, infrastructure and architecture altogether, relationship and messaging between entities.

Architect is also 50% **DevOps** and manager of infrastructure. You need to know answers to typical questions - like where do we get data, how SMS will be sent, what exactly would happen if production database will be damaged, how much SSD/RAM we need, how much it will cost us, etc.

Architect also is about **general math, data structures and algorithms**.

#### The hardest job of a Software Architect is to make complicated things maximum simple with resources you have to fulfill the need of the business.

In the end I, unfortunately, will disappoint you, software architects are very expensive, requires much more knowledge in a lot of domains and type of personality then you imagine, and many companies won't offer that position for you (not mentioning that every company has own definition of architect), they just don't need you or even more don't understand what is architect and why do they need one. In larger companies you will need to work as an engineer for at least year to earn a higher position.

Not everyone wants to be Architect, it's a mix of A, B, C, D, E, F. Some people fine to be Lead UI engineer, Lead DevOps, whatever, however if you like risking and very curious about many domains, are flexible and have a huge RAM in own brain, then Software Architect is definitely for you. The main difference between Software Architect and CTO is that CTO is 80% about business and CTO almost never writes code, yet, in smaller companies CTO may do everything but smaller companies really have no CTO even if you call yourself so.

P.S. be prepared that many people won't like your decisions or "orders". Still you have to practice soft skills and be able to sell any tech to your engineers as well.

[Mohammad Gouse](https://hashnode.com/@Gouse)

[May 7, 2017](https://hashnode.com/posts/8-signs-you-are-on-the-way-to-becoming-a-software-architect/58f5edeeb168746ffba744b1/comment/5900b613a464d8d9977c9efc#reply-590eb109042257bf29db790e)

well said

[Rowland Ekemezie](https://hashnode.com/@rowlek)

[Apr 26, 2017](https://hashnode.com/posts/8-signs-you-are-on-the-way-to-becoming-a-software-architect/58f5edeeb168746ffba744b1/comment/59009eaf9863a67f4cc92f76)

Great piece. Big picture thinking and requirement analysis. Boom!

[Kevin Scott](https://hashnode.com/@kev8144)

[Apr 26, 2017](https://hashnode.com/posts/8-signs-you-are-on-the-way-to-becoming-a-software-architect/58f5edeeb168746ffba744b1/comment/59009e4ccb8194df974e594a)

A beautiful read, thank you. A request for your next post: A road map for aspiring developers.

[Sandeep Panda](https://hashnode.com/@sandeep)

[Apr 18, 2017](https://hashnode.com/posts/8-signs-you-are-on-the-way-to-becoming-a-software-architect/58f5edeeb168746ffba744b1/comment/58f5eef2977c5336c6f49030)

I think, the #1 point is the key differentiator. Clear Communication is a must for any technical architect.
