| Level ends up depending on two things: Skill - Do you have the raw skills to do the task at hand. Scope - What scope are you doing that task at. Example: - Setting up a single file server for your team, pretty easy, low effort. - Setting up a file server / SAN to hold corporate data. - Designing file servers for the core of your business operations. - Doing that for a vendor, where your software and architecture choices will impact possibly impact N companies. (Ironically the last two are closer than you think.) But it isn't about setting up the file server software, it is about the scope, the size of the team you are likely leading, the impact of the decisions etc. Automation, repeatability, etc... Actually architect the thing instead of winging it... The bigger the numbers get... the bigger the title, and the better, you better be, both as an engineer and as a human, willing to accept that you are wrong, and find that better answer... People are relying on you to deliver. |