GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The terms engineer, analyst, consultant etc are bandied about far too easily these days. People are called consultants and engineers that, to me, are really only technicians. You will, by and large, be unable to judge what someone can do by their job title.
The terms engineer, analyst, consultant etc are bandied about far too easily these days. People are called consultants and engineers that, to me, are really only technicians. You will, by and large, be unable to judge what someone can do by their job title.
Ok, that's the practice but dont you know any classification with the tasks that a person who works around computing could do?
No, because the job titles have no defined meaning. I personally define a technician as someone who is competent at a fixed list of tasks without necessarily understands the full details of what they are doing. When they are faced with a task they have not been trained for they come unstuck. An engineer on the other hand has a much deeper understanding of his subject and when faced with a new problem simply starts from fundamentals and works it out from scratch.
I agree with what's said - job titles are no real guide to what's required. However, here's a link to a UK graduate careers advice site, which gives examples of the sorts of duties, and requirements of a range of IT roles. Indicative only, but you may find it helpful.
It may also be useful to look at actual job adverts, particularly where there are detailed job descriptions and person specs provided.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.