🦍 Evolution of a Developer v1.3 "Delicious Development Branches" 👨💻
In previous posts, we discussed growth in quality and side development branches.
Now, I will complete the last 3 development branches.
These branches are very cool and quite accessible to any developer from Middle+ in 2-3 months.
! Disclaimer ! In the next 2 weeks, I will host a series of webinars, in which I will analyze all the pros and cons of each position, how to grow into them, what earning prospects they offer, and what is required for employment. Follow the news in the channel.
1. Business System Analyst (BSA) – not many people talk about this role, but it's incredibly interesting.
Conditionally, this is a local business Architect. Their task is to fully study the business process and user needs, and then design a system and pass it on to development (Team Lead, for example), which will formulate specific sprints.
You will no longer be working with code, your main task will be to analyze huge amounts of information and come up with the most optimal solutions, creating documentation and schemes. But you will still need many technological skills in architecture and design, since all your decisions will have to be incorporated into the code of multiple services.
There are enough vacancies, and they are well-paid.
2. Data Engineer – few people know about this role, but its main task is to design and implement data flows and their transformations to target systems.
Most often, this involves working with creating a data source repository, validation, and cleaning, preparing for business tasks (through BI visualization and data analytics).
You will be writing code for data extraction from sources, transformation, and visualization (ETL). These tasks require a good understanding of business, working with data structures and databases, but not particularly much data science or analytics.
The market is of medium size, and the pay is good.
3. Product Engineer – and this is the most interesting and new trend. A trend that I noticed at the beginning of 2021, which will soon become "de facto".
This is not quite a "specialization", it's rather a role / approach to thinking, when you set a task for development not to "develop a menu", but to "make a more efficient way for the user to work with the system".
A Product Engineer knows what users want and sets tasks to satisfy these needs through development of features.
This is something in between PO, BSA, and Team Lead.
I can talk about this role for a long time, so get ready for a series of articles, in which I will reveal the specifics of their work.
If you liked it, then put 🔥 sexy-emoticon 🚀 in the comments, write what you would like to hear more about, and wait for the webinars 😘