Interview: Tell me about yourself

Tell me about yourself (2 minutes)

1. About myself, I have professional and personal tracks.
2. I have been doing image and audio related research and development for the past 7 years.
3. Actual
   Experence: My most recent experience has been doing an innovative
   multi-disciplinary research that involves optics, image recognition and
   digital audio signal processing. 
4. What I gained: I've developed good R&D methodology, organized research and programming styles.
1. Research content: This work is unique; it requires to deal with a programmable white-light interferometer microscope, which involves mechanics and optics, and with millions of images that contain grooves at micrometer-to-nanometer level;
   all of them need to be recorgnized in the image domain yet eventually
   interpreted in the audio sense. This is the kind of work that needs
   both patience and imagination, which are both my strength. I gained
   interesting signal processing experience in connecting both domains.
1. My
   other strength is in R&D methodology: From various experience of
   working with new problems that involves massive data with little
   reference to resort to, I have cultivated an organized and cautious
   research behavior and programming style that works pretty well with
   exploration of ideas and constant evolution in algorithm implementation.
1. In a procedural research, I strive to do a depth-first style to try moving forward
   towards the end result in the early stage of research, and skip little
   bumps as fast as possible until a skeleton workflow is built up.
2. Then
   as the whole problem gets better understood during the course, I would
   then work on each step of the workflow or adapt the workflow according
   to any new surprises. 
3. For recorgnition problems, I would start
   with creating a meaningful and precise data
   visualization that helps me verify any change that my real work
   makes, and I use incremental tests on my extremely large datasets for
   any new idea or step in a workflow; 
4. To
   ensure any failure during long experiment running time, I have detailed
   temporary data storage and retrieval schemes, so even a power failure
   wouldn't cost me too much.
5. My coding style makes such
   evolutionary processes easier by using systematic naming conventions,
   template-functional design pattern, and I would tidy things up whenever
   new functions come into the whole system with necessary code
   refactoring. As a result, my main client routinesseldom change.
6. I respect performance optimization in coding but I use them only after I have better understanding of the problem.
5. I
   have pretty good sense of presenting ideas, work, and very considerate
   about applying various design principles to my presentation more
   comprehensible and efficient.
6. I'm strong in independent problem-solving.
7. In
   various research projects and extra-curriculum work, I've also worked
   in teams, as a member and the coordinator as well. People often find me
   an easy-going and cooperative person.
8. When having to meet dealines, I'm very flexible and adaptible in my R&D approach;
   if brute-force works better in such a situation I would just use it.
   When the automation of the microscope wasn't working well, I manually
   scanned 700 images to meet the deadline.
9. What I'm looking for now is a challeging project that's more widely applicable, using my experience, knowledge and skills, and I'd like to join a strong team and have a positive impact on the R&D process.