Depends on your position/project. I'd say anywhere from 40 to 60 on average.
Depends on your position/project. I'd say anywhere from 40 to 60 on average.
Most top companies do not care about working hours or time schedules as long as the work is done. Typical minimum expected is 8hours a day .However this may go up if you run into critical issues .So companies offering flexible working hours also expect employees to extend work hours when there is requirement .
At the end of the day ,the number of hours you work depends greatly on your ability to say "NO" when required ,your efficiency and time management .
Different role prefers different role and responsibilities , normal working hours for a permanent employee is 8 hours per day to log hours in Time card, but this can go to few hours more depends on assignment you have been working and customer demanding for the deliverable.
If you are eager to learn something and want to enhance your skill set then you can stretch few hours as self learning activities but this not be accountable
Depends on a number of things:
From my experience (loving what I do) I have had weeks where I work 60+ hours and very few that come to less than 40 hours. Any engineering position that is associated with projects and is not a technician position will most likely put you above 40 hours frequently since project work is extremely variable (nothing ever goes 100% according to plan) but for that same reason there will be several weeks where you wont get 40. I've heard of managers that expect 50 hour weeks and others that don't care as long as the work is done (my experience has been the latter for better or worse).
So a roundabout answer but hopefully it gives some clarity
It's depending on the project nature and how critical it's delivery on time.
In general, Engineer should work is 8-9 hours a day. which is around 40–45 hours per week.If you really interested in what the work are you doing then no matter how many hours you work, but it's give real satisfaction once you finished your task by putting some extra efforts. Although you can spend appropriate time on each task so that you can do time management well.
Once you fill interested in your own task then working hours may be very. it's again voluntary and depending upon your choice of work.
There is no alternative for hardwork and dedication.
As per my understanding, Giving as much as time in what you love to do as engineer.
Different company has different working hour policy. Genreally it is 8-9hr per day . If you are in services then you need to work 8-9 hours per day howeverif you are working as a software engineer,You ll have targets and deadlines which you have to meet. It will depend on your efficiency.
It depends of the project you are in, some days it could be 8 hours, others more or less. This is irrelevant for any career you decide to choose. You can work 18 hours or 4 hours in any work. It depends on you how much do you want to grow up professionally and what do you aspire.
It can depend on your field and your level of engineering. Engineers can have different requirements of their time. For example, if you are project based you may be required to work a regular 9-5 type day most of the time, and then when it is critical for the project additional hours may be asked of you. While you could be shift based, where you have a 6 or 8 hour shift and after that you can log out and be done for the day.
It depends on your industry and type of role and responsibilities.
First, engineers can work varying amounts during the week or even a day. But on average, statistically, engineers work more than 40 hours a week. That's AVERAGE. Again, as I started out saying, that means a lot of engineers work less and a lot work more. Now, if you're in a support role -- that is, supporting the activities of others, either co-workers or customers or other folks, you'll likely work during their average 9-5 shift. If, like me, you like to get involved in some challenging projects, possibly managing teams in other countries, you'll work when you think you need to get something done. And if you're lucky enough to get on really cool projects like I generally did, you'll be thinking about solving problems and getting new ideas all the time. And you'll love it. At one point, I was lead engineer on a large project that took up 140 hours a week. You read that right. 140 hours or even more. That left only a few hours in the week to sleep. And I loved it. But that's very, very rare, and very indicative of the fact that people involved in science or any other projects of passion get fanatical about the rush of solving problems and achieving. Getting your first patent or being asked to present your first discovery or creation is a great rush and encouragement.
As you move up the ladder, you'll have more control of your hours, but beware -- you get hooked on the "solving problems" thing, and you'll often feel compelled to work much longer. But that is voluntary.
So the classic answer is "about 40 hours a week", but compare that to a dedicated musician who only thinks about music "about 40 hours a week". Probably not going to happen. These folks will likely be thinking, eating, sleeping, listening and playing music most of every day and often much of their dreams. If your job was pumping septic tanks, you'd be working pretty hard and feeling a sense of accomplishment when you fix someone's plumbing problem. But you're probably less likely to be spending a lot of your free time doing that. Some jobs are more consuming. And hey -- that's a good thing that people can have jobs that they'd do for free anyway.
I'm required to work 40 hours a week, however it can vary a lot depending on the type of projects that you are consulting on and what the needs of the customer are. Some projects are more transactional like work where you have an engagement of lets say 200-400 hours over a six to eight week time-period. Other projects are ongoing where you continuously work with a customer for lets say over a year time-period and then hopefully they renew their contract and you continue to work with them. Projects are given an allocation of hours per task that is stated in the customer contract.
So far my experience as a Consulting Engineer there is a lot of flexibility built into my schedule. For example, I could work lets say 4 hours on a Sunday and then come in Monday and work 6 hours. Working from home is also an option for me a couple of times a week so I can save time on the commute to and from work. Most of the seasoned Consulting Engineers that I have work with that are successful work a minimum of 40 hours a week and are more likely to go over that number on a continual basis.
Working hours depend on the job profile and projects. Apart from that how fast anyone finish there work . Some companies have policies that their employees work 8 hours a day and the employees have to spend 8 hours in office . In some companies the working hours are flexible but the project completion deadlines will make you to work more hours than usual 8hours. Somedays i dont have much works so i finish my working day in 5 hours or less also but if the projects demand more time it might goes to 12-14 hours or more . Average an employee has to log 40 working hours in a week .
Hello Jose, how many hours do you want to work ? there are opportunities all along the scale and you could find yourself travelling with work and doing work that you enjoy in all different kinds of places, staying in different places and seeing lots of interesting things...
Please feel free to ask me any questions that you have
Hi , It really depends in which field you are working , generally if you are working in networking or IT field then the normal hours could be 8 hours but it can be extended to 10 hours and if you are in support profile then in some critical days it could be 10 hours.If you are fresher then you might have some other shifts like 10 hours night shift in some companies.
Hello Jose, the number of working hours for an engineer is typically 6-8 hours per day but it also depends on the field of engineering and the role you play in the company.
For example I am a networking engineer so I spend typically 6 hours per day at my job. But I believe to an extent if you like your work the hours are nothing when compared to the exposure and learning you receive from your job.
Hope you find this answer helpful. Good luck!
It may sound cliche when I say "how you work/quality of work should be your focus than hours spent to be successful in professional life. When you start working you may take long hours to do simple things but with experience you will be time efficient. Especially in IT field where you end up doing lot of repetitive work, employers look for resources who is problem solver and can help develop solution to save time and enhance accuracy of work by finding way to automate it.
Traditionally/historically network engineers were not looked as programmers (scripting, automation etc) but now with advent of time it has changed from "nice to have" to being "required" for the job. Even at entry level jobs some sort of scripting language, Linux, understanding of virtualization fundamentals is needed apart from knowing networking fundamentals or having CCNA level certifications.
We are in constantly evolving era of technology and regardless of hours spent to do your job always keep 4 to 6 hours every months to learn something new and keep yourself up to date.
It depends on the industry you are in, deadlines, company, and the specific project you are currently working on. Typical work-week for an Engineer would be 8 hours a day, 5 days a week. If you plan your schedule well, you can get around by working 8-10 hours a day. Sometimes, you will have work more than 10 hours if the schedule demands. Also if your work involves dealing with a computer most of the time, you have the flexibility of working remotely (Home, Coffee Shop, Client place, etc.). This flexibility comes in very handy.
Ani recommends the following next steps:
It depends on your company and profile. Some company/profile have a policy of completing 8 hours while in some there is no strict guide lines for time i.e it depends on the project requirement where engineer might need to put around 4hours or 10 hours to meet the project deadline.