Answer the question
In order to leave comments, you need to log in
How to retrain from an analyst to a developer?
After 3 years of working as a SA / BA on various projects, I got the feeling that I was tired of working as an analyst and every day the degree of burnout is increasing. Rather, it’s not the tasks themselves that are tired, as such, but the very specifics of the work - working with requirements, developing technical specifications, constant communication with customers and all the other “routine” of analytics no longer brings any pleasure. It was writing various kinds of scripts in SQL or Python that brought most pleasure in the work of the SA, rather than the duties described above.
There was a strong desire to retrain in development (most of all impresses Swift). I set myself a goal in six months to try to get a job as a junior. As part of the training, I study for a course on iOS development, read Usov and take courses on swiftbook and plan to develop a couple of pet projects for my portfolio.
From hard skills, I can highlight a good level of SQL, basic Python, experience with DWH, a basic understanding of client-server architecture, I have experience with API, JSON.
Interested in:
1) How "IT" background as a SA / BA will be useful for employment?
2) Will there be a prejudice among hiring people due to a rather abrupt change in activity?
3) I will also be very happy with the advice of analysts who have become developers and the advice of more experienced developers or hiring!
Answer the question
In order to leave comments, you need to log in
Op, hello to a colleague in the specialty) Just my story) I also worked as a SA / BA for 2.5 years. At the beginning of this year, I decided to switch to C# development, as I had the experience of an intern in the company in the last year of study at the university. I myself left the company not so long ago from the position of SA / BA, I decided to devote more time to training and have been looking for a junior position for a week and going through social security. From my own experience, I can advise you to inform the heads of the analytics department or HR in your company that you plan to leave now and move into development. If the company is large, there are many projects, and you yourself have shown yourself well as a specialist in analytics for 3 years, then HR will either offer a salary increase or start looking for a vacant junior position on other projects. In my case it was. Unfortunately, the company may not work at all with the technology stack you are interested in, or there simply will not be a place I was eventually offered a place as a PHP developer, I even went through social security for interest, even though I had never seen PHP in my eyes. As a result, they were ready to take it, because they knew the database very well, and especially PostgreSQL, but with a small salary. Refused for a logical reason. And so, from the experience of going through social security services as a former SA / BA who wants to be developed, I can say that it’s worth remembering the times when you got a job as an analyst. It will be the same, or even worse. Get ready to constantly remember your mistakes and gaps in knowledge after each failed social security service in order to fill them in, since the level of knowledge of an analyst and a developer is simply incomparable. If you scored a good salary in the place of an analyst, then get ready for its fall to a level slightly higher than the starting analyst. But considering how much juniors are offered on Swift, it can come out no less, or even more, than in the previous place. At the same time, I had a strong feeling that my previous work experience would at least help in the fact that recruiters would not look at me as a student of those universities who had just graduated or who had taken courses from infogypsies. In half the cases, they don’t care who you worked there before development, even as a PM, they will be treated like a beginner. And so I can agree withJacen11 , the experience of an analyst will simply raise you a little higher among specific beginners, but lower than the juniors, who have already managed to gain half a year or a year of experience somewhere.
1) How "IT" background as a SA / BA will be useful for employment?
2) Will there be a prejudice among hiring people due to a rather abrupt change in activities?
Tired of people? Come over to the dark side
DBA in general can put down on these "vile users". They only create a load on the DBMS, interfere with its harmonious life.
You can dig in there and limit your social circle only to management, other admins, and arrogant developers who put their dirty code into production.
1) How "IT" background as a SA / BA will be useful for employment?First you need to understand what a market is. If you need an apple, then you will take the one that is better for the same price. If they choose between you and a person with the same knowledge but without the experience of an analyst, they will take you, there will be a person with developer experience, they will take him. They do not particularly look at the experience of this kind, first of all they look at the experience in the profession. If other candidates with this will be bad choose you.
2) Will there be a prejudice among hiring people due to a rather abrupt change in activities?will not, they have no choice, now there is a shortage of good personnel. Although he rewound 10 years in prison, but according to the experience of a senior, they will take
3) I will also be very happy with the advice of analysts who have become developers and the advice of more experienced developers or hiring!learn questions for social security and do small projects
If I were you, I would continue to develop in the field of analytics, where you can go into management.
Just a good level of SQL, basic Python, experience with DWH, basic understanding of client-server architecture, experience with API, JSON - it's not enough for a junior.
Plus, a strong drawdown in wages will follow, which will also not motivate. And the developer has a lot of routines, as well as vague requirements and everything that you don’t like in your current job.
And from burnout, a change of company or a short vacation can help.
3) You don't have a lot of experience as an analyst, perhaps professional deformation has not occurred.
Imagine that they send you technical specifications into development, and there you see lame logic, clumsily built power supplies, and the fact that the planned functionality is a set of crutches and bicycles ... What will you do?
This is not very applicable to Swift, I think, but if we are talking about some kind of business systems, I would think hard.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question