A
A
argakon2019-06-16 18:20:42
Summary
argakon, 2019-06-16 18:20:42

How to correctly describe the experience in a resume if you worked in a start-up incubator company on many projects?

The company I currently work for. Engaged in the development of start-ups, creates them, develops and receives profit from them.
I have been working in the company for more than 7 years, I came as a junior to the php/js/html/css full stack (well, that's all the game), then moved to the backend, then to the php seniors. I write not only code, but also design the project architecture, perform the duties of devops, participate in setting tasks. All projects during the work were different and there were about 6 of them, all have different architectures and different stacks. In fact, it turns out that there seems to be one company, but it seems to have worked in a multitude (and in the resume on the same hh you write the company and since when you have been working there and in the end it looks like you have been sitting on your ass for 7 years).
How would you arrange?

Answer the question

In order to leave comments, you need to log in

4 answer(s)
E
Evgeny Romashkan, 2019-06-16
@argakon

And working 7 years in one place has already become something shameful?
Indicate where you worked, write in the description that there were many different projects, you can indicate the most significant ones, and what is more important is what you know how, and not where you worked.
Somehow I saw another option in the resume - transitions Middle -> Senior -> Lead were separate positions decorated.
ps Only devops is still an approach in which the same developers and admins remain, and not the position)

A
Alexey Bespalov, 2019-06-17
@FreeArcher

We are currently being interviewed. So sometimes a good experience in a resume is easy to turn against. For example, you write what you know and php and js and devops. And they will tell you that for sure it means that you don’t know one technology deeply. So, here and there it looked like. Scattered knowledge so to speak.
So it turns out that the resume should not be written one at all, but individually for a specific employer. By focusing on the skills that the employer needs and tempting the ones that are not. It is better to mention them in a conversation if necessary.
And it’s better to make a summary of 2 parts. One official for Ichars, and the other about skills for the leader. Well, this is if you send it yourself in the old fashioned way.

S
Sergey Epifanov, 2019-06-16
@kacheleff

Here is some good advice and an example of a resume. I advise you to read

P
Puma Thailand, 2019-06-18
@opium

On the contrary, if you sit for seven years, this is a plus.
The less often you change employees, the less you need to invest in training new ones.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question