Back to resources

Growing in Your Career and Becoming a Full-Stack Engineer

Mission / Vision / Charter
Goal Setting
Personal Growth
Feedback
Sharing The Vision
Juniors
Prioritization

7 January, 2022

Katerina Hanson
Katerina Hanson

Sr. Engineering Manager at Doma

Katerina Hanson, Sr. Engineering Manager at Doma, describes how she became a full-stack engineer, gaining experience as the first engineer of a passion project.

Searching for the Next Step in my Career

I had been working as an engineer for a long time, becoming a full-stack developer. With my technical abilities at their heightened level, I found myself searching for an opportunity that allowed me to be the first engineer in something. During my search, I learned that many junior engineers were calling themselves full-stack developers due to Hackbrights and other coding boot camps. I disagreed with this method as I felt that junior engineers should choose their passion and excel in that before learning many other coding languages.

Becoming a Full-Stack Engineer

Pursuing my Passion:

Initially, when I began my career, I started solid back-end development. I had more interest and a stronger skillset in back-end development and felt that I should pursue this passion. From there, I slowly moved further into the back-end and was writing deployment scripts. After fleshing out my abilities to excel in back-end tech, I transitioned to work with front-end development. Moving forward, I ramped up and came to the realization that I was truly a full-stack engineer.

Becoming the First Engineer:

After registering that I was a full-stack engineer, I pursued my interest in being the first engineer and developing everything from the front-end to back-end code. I had visions of setting up an application in a way that would allow junior engineers to work on it without moving my progress backward. If I established enough processes in place, it would replicate a sandbox environment in which a group of juniors could experiment and test their abilities without hurting my product.

My vision essentially came true, where I brought in multiple groups of student engineers to enhance my code and learn new techniques. They worked incredibly hard, but my application never made it to execution. Even though my product never made it to market, the leadership experience I gained was still a major step in my career.

The opportunity to lead a group of student engineers grew my technical and leadership skills. I was able to add management experience with front-end, back-end, and dev ops teams.

Growing as an Engineer

  • For an engineer looking to grow, I recommend specializing in one field before transitioning to learn new languages and departments. After learning one language, picking up a second and third language will be significantly easier and quicker.
  • Understand how you learn. The fastest way for me to learn a new language will not work for everyone. I do, however, recommend that you jump into a codebase and experiment with the new language to get a better understanding.
  • Not everybody is ready to learn new coding languages at the same point in time. For instance, Python usually has a tougher learning curve than other program languages, as it automates many things for the user.

Discover Plato

Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader


Related stories

How to measure Engineering Productivity?

30 November

When you grow fast, its normal to focus on Value delivery aka "Feature Releases". Too many releases too soon will inevitably lead to piling tech debts and before you know, inefficiencies creep in, performances goes down, and ultimately any new release takes too long. Sounds familiar? Then read on..

Productivity
Prioritization
Performance
Ramkumar Sundarakalatharan

Ramkumar Sundarakalatharan

VP - Engineering at ITILITE Technologies

Mindsets of High Performance team

14 October

Teams have tremendous impact on the products on they build. T.E.A.M definition - Together Everybody Achieves More is true. A collaborative and empowered team builds great product versus the good ones.

Innovation / Experiment
Mission / Vision / Charter
Building A Team
Productivity
Feedback
Motivation
Praveen Cheruvu

Praveen Cheruvu

Senior Software Engineering Manager at Anaplan

How I failed at my startup

14 October

There are nine specific building blocks and functional areas every org/company need to work to launch the product and provide services to customers. How effectively founders tackle them determine the destiny of the company.

Mission / Vision / Charter
Scaling Team
Building A Team
Impact
Strategy
Prioritization
Praveen Cheruvu

Praveen Cheruvu

Senior Software Engineering Manager at Anaplan

High Performance Team in Action

13 October

A high performance team refers to “ a group of goal-focused individuals with specialized expertise and complementary skills who collaborate, innovate and produce consistently superior results.”

Managing Expectations
Building A Team
Company Culture
Feedback
Coaching / Training / Mentorship
Praveen Cheruvu

Praveen Cheruvu

Senior Software Engineering Manager at Anaplan

Developing an Early Career Program in Technology Organizations

12 October

Why companies should invest in early career programs ?

Building A Team
Hiring
Coaching / Training / Mentorship
Juniors
Career Path
Praveen Cheruvu

Praveen Cheruvu

Senior Software Engineering Manager at Anaplan