Skip to main content

Career Roadmap

I went through most of my career without a roadmap.  I got lucky because a lot of the things worked out: some of it was accidental, some of it was great mentorship.  Some of it were setbacks that I could have probably avoided.  Over 24 years of doing software development I have accumulated a few lessons I can share with engineers that are embarking on this journey.  The number one lesson: find a mentor who can help you craft a roadmap.

If you are not being strategic about your career, you might waste years bouncing around or stuck in an unhappy place.  Being strategic about your career helps you know when you are making steps that will add up to something. Blog posts or books can’t guide you through this journey.  I would recommend getting a career coach or a mentor who can help you evaluate and steer.

I did want to share a document that can help you get started with that conversation.  You can’t get someone to help you unless you can figure out where you want to go.  The document below, while help you by asking a few questions and get you started thinking about goals for the next 6 months and 5 years:

https://tiny.one/career-roadmap

You can use the document as a framework of a conversation with a mentor or a coach.  I would recommend filling it out prior to taking up someone’s time.  It should not be hard to write down what people you respect and what qualities you find appealing.  It takes a few weeks of observations to figure out what activities make you feel good during the day and which ones feel like a drag.

Some of the folks I have mentored were totally surprised when they really unpacked what made them happy.  They though they wanted to be a high level manager, but then said they can’t go a week without writing code.  That’s a hard combination to pull off in most of the companies.

If you do take a look at the career roadmap, I’d love to get your feedback!

Comments

Popular posts from this blog

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team. I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me! SDE/T or QA Engineer interview checklist from Mike Borozdin If you like this checklist you might want to check out these posts: Emotional Intelligence in Software Teams   and  Good-bye manual tester, hello crowdsourcing!

Code versus Configuration

At Ethos we are building a distributed mortgage origination system and in mortgage there is a lot of different user types with processes that vary depending on geography.  One of our ongoing discussions is about how much of the logic resides in code vs. being in a workflow system or configuration.  After researching this topic for a bit, I have arrived at a conclusion that the logic should live outside of code very infrequently, which might come as a surprise to a lot of enterprise software engineers. Costs of configuration files and workflow engines First thing that I assume is true is that having any logic outside of the code has costs associated with it.  Debugging highly configurable system involves not only getting the appropriate branch from source control, you also need to make sure that the right configuration values or the database.  In most cases this is harder for programmers to deal with.  In many FinTech companies where the production data is not made readily acce

Intuitive Programming - Comments

Comments are a topic of vibrant discussion.  Ever since programmers could leave some text in the program that was ignored by the machine the debate started: “what’s a good comment, what’s a bad comment, why comment?” There are endless instructions to programmers that say many of the following things: 1) Describe your function! 2) Don’t write in the comment what you wrote in the code. 3) Tell people why you are doing what you are doing. What I think has been missing from this discourse is the audience for comments and through those audiences there is intent.  The code is being read, skimmed or analyzed by people and tools.  So what are the audiences and reading modes? 1) Maintaining and enhancing the code 2) Skimming through the entire module or file to figure out what the overall structure is 3) Reviewing the test files to check out the test coverage and edge cases 4) Seeing the docstrings of functions while being in a separate file altogether 5) Reviewi