Describe in detail the activities of a front-end developer in an outsourcing company?

Question

Work organization

I am a writer, and at the moment I need help on the mat. part: I am collecting information about working in an IT company.

My main character is a front-end developer, and the company he works for (large and leading in the country) is engaged in outsourcing and consulting in the IT field.

In theory, the hero works in a team where there is another frontend, one backend, two testers, a server manager (sysadmin), sometimes iOS and Android developers and an analyst are connected to them. The team has a leader (or a team leader, or a manager - which is more correct?)

A huge plus for you in karma if you worked in a similar company (or just with a team), you know how it all works and answer the following questions:

1. Is it correct selected team composition for a large company? Maybe someone should be excluded/added?

2. What kind of projects are usually given to the team? Websites, software, applications? Since the main character is a front-end, and the team itself does not shine with talents, something not too burdensome is needed.

3. The role of the leader (teamlead). How does he explain to his team what the customer wants? How often does he appear in the office and does he control the work process? How does he communicate with subordinates - in the role of an evil boss or on an equal footing?

4. Deadlines for different projects (for example, how long does one site take to complete and in how many stages?)

5. Can the customer advise making changes if he is not satisfied with the result? Before work, any contracts are generally concluded and who is responsible for this?

6. The work process of a front-end developer. Where does he start his work in the first place? What is the hardest part of his job and how does he interact with other team members? Are there any times when the frontend and backend need to do something together? And are there other cases where the frontend needs to technically interact with other professionals?

7. Sysadmin. Does he work in the same office with everyone or somewhere else? What does his workplace look like? More process is needed. If possible, describe in simple terms.

8. Testers. They seem to be testing almost at the very end, when everything is ready. But, probably, at the beginning of the project they do something?

9. Developers for ios and android. If you want to make a mobile application, how do these developers interact with the rest of the team?

10. Analyst. Is he definitely needed, or can the team leader play his role?

11. The composition of the team, in general, can change, depending on the project? Where, in this case, are the "unnecessary" workers sent? To another team?

12. Mittaps, meetings, meetings. How often do they take place, who participates and what is discussed there?

13. Working atmosphere. How do programmers communicate with each other during a break? Do they have any special topics for discussion or can they, like ordinary people, talk about any extraneous? Do you have "their chips" in communication?

14. Office organization. It looks like the most ordinary office, only there are computers on the tables? Are there special (service) premises, for example, for servers?

15. Are there any particularly important nuances that should definitely be mentioned when describing the work?

Answer 1

Chuvaaak .... I'll tell you as a writer to a writer - do not undertake to write about IT, not knowing at least a little of it from the inside :) You will immediately see that you are a "stranger". It's like writing a book about the work of a cardiac surgeon of the highest category, without knowing human anatomy :)
The answer to your question would be a huge footcloth - if someone wanted to write it. But my advice to you is don't. Will not work. Everyone who works in IT - they will laugh at you out loud and roll on the floor.
And there is nothing interesting in office work...

Answer 2

My main character is a front-end developer, and the company he works for (large and leading in the country) is engaged in outsourcing and consulting in the IT field.

In theory, the hero works in a team where there is another frontend, one backend, two testers, a server manager (system administrator), sometimes iOS and Android developers and an analyst are connected to them. The team has a leader (or a team leader, or a manager - which is more correct?)

A large company is a minimum of 1000 people. And better 3-5k people.
A project with only 2-3 developers is just about nothing. In outsourcing, such small projects are nonsense, it makes no sense to look for a customer and conclude an agreement with him, allocating only 3-5 people. Unless these are small sub-projects within one large customer.
And if the hero is the only main developer, then he will be the team leader, because the team leader is the lead developer, sometimes combining the system architect.

1. Is the composition of the team chosen correctly for a large company? Maybe someone should be excluded/added?

Either make GG a team leader, or add at least 10-15 more people to the project.

2. What kind of projects are usually given to the team? Websites, software, applications? Since the main character is a front-end, and the team itself does not shine with talents, something not too burdensome is needed.

Lead a thread of a small project within a large customer, for example, an INTERNAL reporting system that the customer uses for his own needs, and not for working with his clients.

3. The role of the leader (teamlead). How does he explain to his team what the customer wants? How often does he appear in the office and does he control the work process? How does he communicate with subordinates - in the role of an evil boss or on an equal footing?

Team Lead is the lead developer. Actually works on the architecture of the project, coordination of interaction with other services at the technical level. Do not confuse the team lead and the project manager.

4. Deadlines for different projects (for example, how long does one site take to complete and in how many stages?)

If you don’t know about software other than websites, then don’t write about large-scale outsourcing. Write about the small but proud "horns and hooves". The project can take years, decades. There are not many large companies that exist for only a few months.

5. Can the customer advise making changes if he is not satisfied with the result? Before work, any contracts are generally concluded and who is responsible for this?

Certainly. It depends on the project manager how much he will convince the customer to pay for additional edits and advice. It depends on the project manager how he concluded the contract and how he agreed to accept a satisfactory result.

6. The work process of a front-end developer. Where does he start his work in the first place? What is the hardest part of his job and how does he interact with other team members? Are there any times when the frontend and backend need to do something together? And are there other cases where the frontend needs to technically interact with other professionals?

There is a system architect, there is UML and other words. Can you really find a friendly developer from a large company who will consult regularly? Because otherwise it will not be a story about a developer, but a story about a fictional world with fictional technologies and processes.

7. Sysadmin. Does he work in the same office with everyone or somewhere else? What does his workplace look like? It needs more process. If possible, describe in simple terms.

In outsourcing, there is a separate system administrator, a separate devops. They work similarly, people have been studying the process of work for years. Most juniors don't know about the work process, and you just want to find out with a couple of questions.

8. Testers. They seem to be testing almost at the very end, when everything is ready. But, probably, at the beginning of the project they do something?

Testers are different. It even happens in tdd, when tests are written first, then the application. You can test immediately, later, or write autotests and constantly update them.

9. Developers for ios and android. If you want to make a mobile application, how do these developers interact with the rest of the team?

Just like everyone else.

10. Analyst. Is he definitely needed, or can the team leader play his role?

You don't need to write a website. To write a business application you need.

11. The composition of the team, in general, can change, depending on the project? Where, in this case, are the "unnecessary" workers sent? To another team?

12. Mittaps, meetings, meetings. How often do they take place, who participates and what is discussed there?

Depends on which agile is configured. In addition, they can be between specific teams or even between specific people.

13. Working atmosphere. How do programmers communicate with each other during a break? Do they have any special topics for discussion or can they, like ordinary people, talk about any extraneous? Do you have "their chips" in communication?

They have some special topics for discussion or they can, like ordinary people

they can just like ordinary people

No, we are Martians.

14. Office organization. It looks like the most ordinary office, only there are computers on the tables? Are there special (office) premises, for example, for servers?

There may be special offices. For example toilet, kitchen, reception. Maybe a server.

15. Are there any particularly important nuances that should definitely be mentioned when describing the work?

Yes. Don't write a book about IT if you haven't worked in IT yourself. Or find an IT specialist you know who works and write a book about his work.
I'm sorry, but your questions cause such dissonance that it's kapets.

Answer 3

If as detailed as possible:
points 1-14:
Yes, anything can be, come up with any fantasy, and somewhere it is exactly like that. In each office everything will be completely different
point 15:
yes, but it depends on your hero, then think for yourself. The only very important nuance common to all front-end developers is that they work on the keyboard.