<p>How do you know you;ll make a good Systems Engineer?</p>
<ul>
<li>you have an account on DOORS</li>
<li>you actually remember your DOORS password</li>
<li>you know all the hardware and software engineers, QA people, and all the good restaurants since you travel so much</li>
<li>You like meetings and schedules</li>
<li>you know how to pull code off GIT, do a build, flash the product, and test it</li>
<li>you have enough courage to take the product to the customer for ‘feedback’</li>
<li>you can describe failures better than the QA summer students (“Duh, Sir, It dids not worked”)</li>
<li>you can talk ‘Supplier-ese’ and ‘Customer-ese’.</li>
<li>you know all lab technicians by name and title</li>
<li>you have a secret supply of parts, connectors, cables, etc. only for close friends</li>
</ul>
<p>All of us software drones play integrator to some extent, but in a complex product you need someone who understands both the software and hardware side. and the customer side. Usually our Systems Engineers are EE’s or ECE’s. </p>