Principal Engineer vacancy for my team
I have a great job directly to my team as Principal Engineer, who will be my deputy in engineering activities at the level of my 1K unit. Let me tell you right away that the unit is divided into 4 management 1 The department where these issues are also separately worked out, but I need my deputy to oversee the development of important topics and track the movement on them. Now let's take a closer look. n
1) Observability & reliability In fact, in my concept of the world, the technical directors themselves are responsible for the observability and reliability of the services of their teams, but centralization is necessary, because
- we have standard approaches to logs/metrics/alerts - this is our observability platform Sage
- we have standard approaches to classifying services by criticality and measuring their SLA - this is our SLAser platform, which runs SLI / SLO / SLA and is able to calculate their compliance based on data in Prometheus. We have an approach to dealing with incidents and tools for automatic establishment and linking between each other. My job is to learn about all these tools, understand how they are related, how to use them, and help teams in my area of responsibility raise their level of maturity in observability and reliability by using standard tools.
2) Capacity management We have a standard capacity management process that requires active planning on how much resources our services will require in the future. Since we have a hybrid cloud, we need to be able to plan both inhouse power and power in public clouds, which is cool. (internal developer platform) It can work both inhouse and in public cloud, thanks to Coretech. Interestingly, capacity planning is a technical management area in my department, but I need centralized guidance from my deputy to make sure everything goes according to plan. (which we discuss with leaders) If there are problems, they can be solved by my deputy.
3) Migrations and EOL We have a centralized migration process in our IT that often creates a lot of work for executives. If migration is initiated from outside the unit, it is necessary to understand how it affects us and how it will meet the target deadlines and coordinate all the teams inside. This often requires a cool engineer who understands migration and what it affects inside. In fact, my deputy will be responsible for this coordination.
4) Scalability The company has been actively growing in recent years, we have many projects in the process to improve the scalability of our systems under new loads. I have a deputy in architecture, Anton, who is responsible for this project both in my division and at the level of all companies. But for my deputy in engineering activities there is a job in this project.
In fact, there are a lot of interesting activities with which such a candidate can help me, but it is better to move on and answer the question “What happened to my predecessor?”, which arises when looking for someone in an interesting position. The answer is that my colleague in this position worked with me. 6 He worked well for years and then decided to move to a sunny place. Igor is a great man and I will miss him, but now I am looking for a new Igor.)
If you are interested in a vacancy, then we will need to get acquainted next, and then there will be technical interviews, many of which I have already told about.
General engineering issues - questions in the form of a blitz about networks, computer operation, operating systems, databases
Algorithms and data structures - solving algorithmic problems with writing code
Troubleshooting - working on an incident in a typical system (here posture about this interview)
System Design - Designing a Simple Service (here posture about this interview)
If the results are cool, then we will agree on the PP.
If the vacancy is interested, write to me in person
#Vacancy #SRE #Career