Software Engineers Job Description

<p>Is it true that Software Engineers don't spend most of their time writing code? They write charts, graphs, algorithms, and English to design a program and they hand that down to a programmer to actually write the code?</p>

<p>"In a large organization, such as a computer software company, computer engineers would instruct computer programmers to write the actual code that makes up the program and intercede only when the programmers have a problem. Once the program has been developed, the software engineer may test it for problems and examine it for errors in logic or data. Some programs require days to write, while others may require a year or so."
-<a href=""&gt;;/a&gt;&lt;/p>

<p>Software engineers make more money than programmers because it obviously takes more intellectuality.</p>

<p>Are there any software engineers out there who would like to describe what they do on the job?</p>


<p><a href=“[/url]”>;/a&gt;&lt;/p&gt;

<p>We don’t really make a distinction where I work. Engineers usually start out fixing bugs or dealing with test failures. After learning some of the code base and functionality (which takes quite some time), they may be given a feature to work on where they have to write the specs (functional, design, detailed design) and then do the coding. Further up the career change, engineers can still do all of this. Even the architects like to code here.</p>

<p>Many of the managers also do individual contributor work including writing specs and coding. I think that it gets harder to do as you go up the management chain as you’re spending more time doing people stuff.</p>

<p>As GT alludes, don’t get hung up with job titles. They are more or less all equivalent and each company sets up their own hierarchy. Does an ‘analyst’ rank higher than a ‘designer’ or ‘developer’ or SE or Programmer or Specialist or Systems whatever or DB Admin or Network something or…? Each company is different. In practice it is a team working together and everyone has to think about what they are doing. So a mere ‘coder’ is just as important as a ‘software architect’. If you want to understand the whole spectrum of software you ought to work in every role and not expect that a degree will put you in some caste for the rest of your life.</p>

<p>wait, what’s the difference between a software architect and software engineer? /end naivety</p>

<p>The “architect” whether it is systems, software or data is the person who more involved with the framework, overall design, direction and technical standards THAN the coding. That does NOT mean that the systems/software/data architect will NOT do coding.</p>

<p>The title and responsibilities vary from employer to employer.</p>

<p>It sounds like a Software Architect is just a Software Engineer who has moved up to a hands-on managerial position, yes?</p>



<p>Not necessarily managerial…more technical leadership.</p>