-
Notifications
You must be signed in to change notification settings - Fork 50
Issue 498 mid senior engineer blog #532
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
khairahscorner
merged 7 commits into
Women-Coding-Community:main
from
Amenawon:issue-498-mid-senior-engineer-blog
Jul 20, 2025
Merged
Changes from 4 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
e44de70
feat:add blog post
Amenawon 2f07653
Merge branch 'issue-498-mid-senior-engineer-blog' of https://github.c…
Amenawon 8ccf189
fix : revert change
Amenawon 946627b
fix: update blurb image and improve content structure in mid-senior e…
Amenawon 50d94eb
Update _posts/2025-06-10-mid-senior-engineer.html
khairahscorner f1c32dd
Update _posts/2025-06-10-mid-senior-engineer.html
khairahscorner e5c9603
Apply suggestions from code review
khairahscorner File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,143 @@ | ||
| --- | ||
| layout: post | ||
| title: "Mid-Senior Engineer: A Journey of Self-Discovery" | ||
| date: 2025-06-10 | ||
| author_name: Irina Kamalova | ||
| author_role: | ||
|
khairahscorner marked this conversation as resolved.
Outdated
|
||
| blurb_img: /assets/images/blog/2025-06-10-mid-to-senior-engineer-banner.png | ||
| blurb_img_source: | ||
| description: | | ||
| So, you've mastered the fundamentals, you're a reliable contributor, and the "Mid-Level | ||
| Engineer" title feels comfortable. But the ambition to grow, to take on more responsibility, | ||
| and to reach that coveted "Senior Engineer" status is bubbling beneath the surface. You're | ||
| not alone! The journey from Mid to Senior is a significant step in any tech professional's | ||
| career, and understanding the available pathways is crucial for strategic advancement. | ||
| category: Career-progression | ||
| --- | ||
|
|
||
| <div class="text-justify"> | ||
| <p> | ||
| <i>So, you've mastered the fundamentals, you're a reliable contributor, and the "Mid-Level | ||
| Engineer" title feels comfortable. But the ambition to grow, to take on more responsibility, | ||
| and to reach that coveted "Senior Engineer" status is bubbling beneath the surface. You're | ||
| not alone! The journey from Mid to Senior is a significant step in any tech professional's | ||
| career, and understanding the available pathways is crucial for strategic advancement.</i> | ||
| </p> | ||
|
|
||
| <p> | ||
| I suggest to look at two strategies following the chart: | ||
| </p> | ||
|
|
||
| <div class="article-media"> | ||
| <img class="img-fluid" src="/assets/images/blog/2025-06-10-mid-to-senior-engineer.png" | ||
| alt="mid-to-senior engineer chart"> | ||
| </div> | ||
|
|
||
| <p> | ||
| <b>Path 1: Get a promotion within your company </b> | ||
| <ul> | ||
| <li><b>Goal: </b>Get a promotion within your company. </li> | ||
|
khairahscorner marked this conversation as resolved.
Outdated
|
||
| </ul> | ||
| <p><b>Plan:</b></p> | ||
| <ol> | ||
|
|
||
| <b> | ||
| <li> Align your goal with your manager.</li> | ||
| </b> | ||
| <p> | ||
| This is the first and the most crucial step. Unless you come to the person who is responsible for your promotion | ||
| and ask for it there's no sense in preparing a plan with steps, enrolling in certifications for promotions, and | ||
| getting more projects on the plate without any advice. | ||
| </p> | ||
|
|
||
| <b> | ||
| <li> Set up exact steps with your manager.</li> | ||
| </b> | ||
| <p> | ||
| From the first step, you should learn what you need to do: where your gaps are, where your strengths are, where | ||
| your weaknesses are. | ||
| </p> | ||
|
|
||
| <b> | ||
| <li>Execute those steps</li> | ||
| </b> | ||
| <p>User SMART technique for each step. </p> | ||
|
|
||
| <b> | ||
| <li>Ensure recognition across teams.</li> | ||
| </b> | ||
| <p>It's crucial for promotion to be visible inside your company. The more you help others, the more scope you touch | ||
| and your knowledge increases. </p> | ||
|
|
||
| <b> | ||
| <li>Work for the review & feedback. </li> | ||
| </b> | ||
| <p>The important point is to know exact dates where reviews and promotion windows inside your company are happening. | ||
| Your review date is your hard deadline. | ||
| </p> | ||
| </ol> | ||
| <b> Outcome (if your goal is not yet achieved): </b> | ||
|
|
||
| <br> | ||
| <ol> | ||
| <div> | ||
| <b> | ||
| <li>Gather the feedback and create an actionable plan from it to close gaps.</li> | ||
| </b> | ||
| All those steps gave you an amazing experience. How could you do better? What is left for the next time? Through | ||
| several iterations you're guaranteed to get the promotion. However, it could be from 2 to 5 iterations with a | ||
| feedback loop. | ||
| </div> | ||
|
|
||
| <b> | ||
| <li>Go from 1 to 5 from the previous block again.</li> | ||
| </b> | ||
| </ol> | ||
|
|
||
| <p> <b>Outcome (if your goal is achieved):</b> Promotion to Senior Engineer. </p> | ||
| <b>Pass the Interview to obtain the Senior position </b> | ||
| <ul> | ||
| <li><b>Goal:</b>Pass the Interview to obtain the Senior position. | ||
| </li> | ||
|
khairahscorner marked this conversation as resolved.
Outdated
|
||
| <li><b>Plan:</b> | ||
| <ul> | ||
| <li> | ||
| Apply for the interview. | ||
| </li> | ||
| <li> | ||
| Ask HR what stages and how to prepare; ask for feedback in advance. | ||
| </li> | ||
| <li> | ||
| Prepare for the interview. | ||
| </li> | ||
| </ul> | ||
| </li> | ||
| <li><b>Possible Outcomes:</b> | ||
| <ul> | ||
| <li> | ||
| Obtain the role in a company with a quicker feedback loop and get the promotion there. | ||
| </li> | ||
| <li> | ||
| Analyse the feedback and apply for the next interview. (This outcome loops back to the "Plan" stage for | ||
| passing the interview). | ||
| </li> | ||
| <li> | ||
| …and, of course, obtain the role of Senior Engineer! | ||
| </li> | ||
| </ul> | ||
| </li> | ||
| </ul> | ||
|
|
||
|
|
||
| <p> | ||
| Now, the great question: should you follow both paths simultaneously? It's up to you, however, the balanced model | ||
| will be to go through Path 1 for a year and if you've not succeeded go through Path 2 for the next year. The | ||
| iterative approach will lead you to the goal. However, the common trap for engineers is to try to do both paths at | ||
| the same time and it leads to burnout. One path can be the background while the other is the focus. Regular | ||
| interviews wouldn't hurt but be mindful of your time and remember that they were in the background path when you've | ||
| got a rejection. | ||
| I wish you the best of luck on your way! | ||
|
|
||
| </p> | ||
|
|
||
| </div> | ||
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.