r/uwaterloo•
a2xia

2A ECE: What jobs to aim for, for 2nd co-op

Going into 2A ECE for Fall 2017, wondering what type of co-op jobs would be viable to apply to with the following erm... "qualifications".

  • First Coop: A hardware position, worked on printed-circuit board (PCB) design, embedded processor programming (in C)

  • Side "projects": Nothing exciting, a few rudimentary Python scripts (such as a ESRI shapefile-to-XML converter, Facebook friend sorter), a (rather poorly made, unreleased) Android game

  • Would Prefer: Something better than QA and IT support, preferably. Would prefer another embedded/hardware job if possible, I hate coding but would not mind a developer position if it were at all possible. No location preference, no salary preference, no company-name preference.

Additional Question: My first co-op was located in China, which maybe has a bad reputation(?) (Although I am very much Canadian in culture, birth, and citizenship). Would this affect prospective employers? (E.g. would they "look down" on internships in China due to say, the hypothetical unreliability of quality?). If yes, if there a way to remove the co-op location on the WaterlooWorks work history part of the application?

Posted Jul 24, 2017, 8:17 AM UTC

010
Frozen-Placenta3b half-asleep rambling•

With a decently formatted resume, you should not have have much issues getting interviews for hardware positions. I don't know if you are in CE or EE but you can try exploring different but related fields to hardware, such as FPGA or digital signal processing if you are in CE or try to maybe break into RF if you are in EE. While you may be missing the educational background, simply having experience with hardware will put you ahead of most of your classmates and many upper years.

3
a2xiaOPthe program with depressed people•

Thanks for the advice. I'm in CE.

On a side note... despite the memes I honestly think Geomatics is the right program for me... oh well.

1
[deleted]•

[deleted]

1
thatvulcanfuckerECE•

Im kind of on the fence here, if during your co-op you felt like you gained real hardware design/embedded systems experience then I would urge you to stick with that (if you enjoy that kind of work) because its harder to get a hardware / embedded systems job than a software dev one, and you have relevant work experience that most 2nd year ECEs wont have since you havent taken any real hardware design courses yet. The reason I'm on the fence is because your co-op is in China, I dont know if you actually knew the low-level mechanics of what you were coding into the micro-processor, or if you were just coding in C and testing if shit works or not. Although I suppose any experience is good experience since its only your 1st coop, so I would still urge you to stick w/ embedded or hardware and ride that wave into some dank placements during your upper year coop terms.

2
a2xiaOPthe program with depressed people•

So my work involved programming microprocessors and using their peripheral capabilities for various things using various methods... depends on what you feel is "low level mechanics"?

hmm this is hard to put in words. A few examples of what I did coding-related: master-slave communication using I2C (both with on-chip preset I2C channels and by bit-banging I2C), things like Digital-to-Analog Conversion (again with on-chip preset channels and by using PWM manipulation), bit-level Math, using external timers, watchdogs, using various chip functions (eg GPIO, USART, etc)

Thanks for the feedback. I'm definitely more interested with embedded/hardware stuff compared to uh, "pure coding", so I'll keep that in mind.

2
thatvulcanfuckerECE•

This is great experience! I was talking about the actual affect the C code has on the micro-processor and how optimized it is in terms of memory allocation, run time, testing using RTL simulation etc, and less so the actual applications of what you were doing. I think even if you dont understand all that quite yet you will be taught it in 2A/2B. You're a big leap ahead of most CEs heading into 2A, use that to your advantage! An example would be actually learning how D2A converters (and A2D converters) work at the circuit level, instead of supplying them commands so that you know the capabilities of your converter and how to use it optimally. In hardware design you learn to optimize bit-level algebra in order to minimize area on the FPGA (and in the real world, in the PCB), how to maximize clock frequency, etc. Its super interesting stuff, and I think you'll enjoy the next few semesters as CE begins to specialize in it.

2
ooosssosososCS 1B•

isnt that just like arduino but with c & another microcontroller platform? (aka "I hate coding" doesnt really go hand in hand with that)

How is that hardware?

But I digress, If you're interested in actual circuit design idk if that field is going very well since most traditionally circuit design tasks have been replaced by microprocessors since they're so cheap and are easily equivalent to many logic circuits.

for circuit design high frequency applications seem to be pretty interesting and seems to have pretty good job prospects.

1
a2xiaOPthe program with depressed people•

Ah, I was only elaborating on the programming side of my work in reply to that particular comment. Another portion of my coop tasks included circuit schematic drawings and verification processes (not really advanced stuff, of course). I don't expect to completely pursue a career without programming, I think that's hard to do in the current climate, but I do enjoy mixing in some physical component in addition to coding processors. Essentially, to say, I prefer low level coding and none of that crazy algorithm-API-machine-learning-insert-buzzword-of-the-day stuff that all the CS/SE kids talk about.

Sorry if I've offended with my "I hate coding" remarks... lots of my CS friends don't seem to sit well with that.

1
ooosssosososCS 1B•

oh no, not offended at all xD sorry if I came off as offended

possibly cuz I\m also interested in low level programming

good luck your your job search :)

1
thatvulcanfuckerECE•

Its definitely not hardware design, but it is embedded systems programming (so is arduino). I think there still use-cases out there that make ASICs relevant like in sensors, cases where you wouldnt want to bog the system down w/ a micro processor especially if you dont need to do any processing.

1
QuoteMaker_CS•

CEO of Jane Street is a pretty good goal tbh

1