Table of Contents
What do you know about system engineering and what are its main goals/objectives?
System engineering is the application of engineering principles and practices to perform the design, development, implementation, and operation of systems that are used in manufacturing or services. It includes work at an advanced level of abstraction that includes complex systems with large numbers of interacting components. This can include components of a systems-level engineering, but also encompasses such areas as production engineering and quality assurance. The system engineer works with and supports the application engineering teams, helping to implement the system requirements in an accurate, efficient and cost effective manner.
System engineers must understand technical process of how products are designed and built.They should have a broad understanding of engineering principles, processes, and applications that enable them to analyze problems and develop technical solutions to the full range of system engineering related problems. They must be capable of dealing with large amounts of information including economic, social and environmental criteria.
The main objectives for system Engineering are:
To design & develop systems in an efficient manner with an end goal to meet the Quality Standards.
To work in effective teams, with the correct people and help them to operate effectively.
To understand how systems are built, so that clients can operate and maintain them efficiently.
To ensure that systems at all levels within the enterprise meet their objectives in a cost effective manner with due consideration of Quality, Safety and Environmental impact.
What experience do you have in this field, and can you share a project that you worked on that was particularly successful?
I have a diploma of multimedia information systems engineering and more than 7 years of experience in various projects, mostly in the area of web development. I worked on an e-commerce website, a media library as well as an email consultation service. In all of them I participated as lead developer, which allowed me to learn new things in each project.
Now, I want to share with you an unusual situation of my career, in fact I worked on a project that had significant influence in how my professional life has developed.
I was hired at an IT company as a system engineer while working as a developer doing simple desktop applications. That is to say, I was doing the same thing as everyone else, just not very well. But that’s probably not so bad – after all: learn by doing is the best way to learn about things you did not know for years. On the other hand, to work as a developer in that company was a joke. The first time I had to implement a login procedure for the system I worked on I couldn’t believe it! There were no logical or common sense ways of doing it, or at least not obvious enough for me.
I knew exactly what I wanted to do, but everything was very unclear and unclear. The code looked perfect from the outside but from inside it was meaningless.
I was learning from trial and error and it looked good. I was working on a React project at that time and decided to use the component for my login function. The component’s logic was simple: “give me a username and password, give me a new secret part of the password.”
And my logic, which was extremely simple, looked like this:
Tell me about a time when you had to manage a difficult or challenging project.
I worked on a project that had a short deadline and required the creation of a complex e-commerce system which had to be completed in half a year. I was responsible for server administration, creating the CMS and integrating it with the different payment systems. It became a big challenge because we were not good in time management and a lot of the things that should have been done in advance, were done later. What made it more complicated was that the project manager was not always available and some of our colleagues, who were also experienced engineers, did not pay enough attention to the deadlines. I suffered from pressure when we should have been working for 20 hours a day. When I asked them what we would do if there was no money for our expenses, they said: “We can’t afford it!” The system went live on time but the work became very tedious. I still feel bad about this experience.
##
Title:Tell me about a time when you had to manage a difficult or challenging project.
(Comparison review)
How do you handle stress and pressure while working on important tasks or projects?
Being a system engineer, I have to deal with many projects at the same time and have to manage many tasks. I always try to minimize the time on a project, trying my best not to miss deadlines or deadlines. I try to focus on one task rather than multitasking because it is very hard work and takes more energy. It also allows me to fulfill each task on time and pass them on to the next stage.
One of the ways I fight stress and pressure is to look at the bigger picture. Thinking about the product as a whole allows me to set priorities and “go with the flow”. It gives me time to think about what is most important at the time and allows me to get things done.
To be able to lay out all tasks, I take note of everything that comes my way and try not to forget anything. I think it is important not to put all tasks on the same level. The deadline of a task should be more important than the deadline of a project.
