Question about Analogue Electronics

Discussion in 'The Projects Forum' started by hunterage2000, Nov 18, 2013.

  1. hunterage2000

    Thread Starter Active Member

    May 2, 2010
    400
    0
    Hi, I have seen job role descriptions for an Electronics Engineer asking for experience of designing analogue circuits.

    Can someone define an analogue circuit and give some examples of circuits and components used?

    Also if you were to produce a portfolio of work, what kind of things would you put in apart from the obvious like schematics, waveform results and photo's? i.e maybe frequency response, noise, thermal sweeps, worst-case scenario graphs.
     
  2. MaxHeadRoom

    Expert

    Jul 18, 2013
    10,500
    2,366
  3. wayneh

    Expert

    Sep 9, 2010
    12,087
    3,027
    FWIW, I think someone here has made the point that all circuits are analog circuits since they function in the real world. Only the purpose or output of a circuit can be classified as digital or not.

    Not helpful, but maybe insightful. ;)
     
  4. crutschow

    Expert

    Mar 14, 2008
    12,977
    3,221
    In analog electronics, the signal is represented by a continuous electrical wave, not discrete levels (except for the value of the electronic charge at the limit). In digital, the signal is represented by discrete levels, typically as a series of digital binary words. Thus an op amp operates in the analog domain and a microprocessor operates in the digital domain.
     
  5. ErnieM

    AAC Fanatic!

    Apr 24, 2011
    7,386
    1,605
    OK, I'll make the point: all circuitry is analog; if it wasn't you wouldn't need bypass capacitors on a flip flop.

    Analog circuitry is things like amplifiers, power supplies, radios, sensors... heck, go to Analog Devices and look at what they make.. of crap, they make micro's too!

    As far as a "portfolio of work" goes... don't bother. Your resume has between 60 and 120 seconds (!) to score all it's points, make it too long and it never gets read. A list of projects is fine (and desirable), keep it to a project name and a one sentence description.

    Remember to just give them a small hint, make them want more to give you the call for a real interview.
     
  6. GopherT

    AAC Fanatic!

    Nov 23, 2012
    5,982
    3,714
    Don't fill your résumé with,
    - I know how to use an oscilloscope
    - I know how to design PCBs
    - I know how to...

    Instead, fill it with,
    - I've built xyz
    - I've designed abc
    - I saved my company x thousand dollars by doing...
    - I solved xyz problem.


    Telling what you have done implies you used all the tools needed for success. These statements build up a nice bases for a conversation at an interview instead. If you don't have a nice conversation, you end up in an interview death spiral - a volley of yes-no questions followed by suggested questions from HR "tell me how you managed to resolve a conflict", "tell me when you had a chance to demonstrate leadership", ...

    Good luck my friend.
     
Loading...