6 Comments

very interesting article thanks.

Expand full comment

Glad you found it helpful and interesting, Alessandro!

Was anything particularly helpful to you that we might right on further in the future?

Expand full comment

I think I made my first step two weeks ago when I contacted my supervisor and told them I was interested in an open Staff Engineer position inside my company. Now I’m sure 😄 I’m used to working with higher-level requirements, multiple stakeholders, and teams, thanks to my freelancer past. I think this role will be more interesting for me than a senior engineer role. Thanks for sharing your thoughts!

Expand full comment

Awesome, glad to hear Akos! Cheering you on in your next step of your journey 🙌🏼

Expand full comment

Thanks Caleb!

Expand full comment
7dEdited

In my experience, titles are pretty much meaningless. I've been everything from a peon, to a Staff Engineer, to a Principal Software Engineer, to a "Technical Specialist" and my responsibilities have been pretty much the same.

I probably should say that no matter where I've ever worked on software that with in a few months I've become the "goto person" to answer questions. For example: overheard a couple of co-workers years ago: CW1: What does "X" mean? CW2: I don't know, but go ask RIck. If he doesn't know, then he will either give you some good ideas where to ook to figure out or figure out himself.

Yes I have a minor ego problem when it comes to software, but I know that I don't know everything (which is why I have a HUGE library of Computer Science related books and I try to learn something everyday).

P.S. My handle in many place is "joast" (an acronym). Anyone care to figure what it means? :-)

Expand full comment