Jump to content

CLAD's and CLA's Positions in Michigan


Recommended Posts

Senior Labview Developer (CLA or CLAD)

 

Company is seeking a Senior Labview Developer with strong Hardware/Senior Hardware Engineer or Software/Senior Software Engineer experience.  The candidate should also have experience with automotive automated test systems architecture and design. Company is a provider of electrical engineering design and consulting services to the automotive OEMs and Tier Suppliers.  Our experience and expertise allows us to assist our partners with integrating their products into the OEM vehicle.        

 

Position Requirements:

  • Coordination and management of all Tester Group related projects
  • Supports Program Managers with tester development issues and customer negotiations
  • Supports quote preparation/resource determination for a specific project
  • Hands on experience in implementing automated test systems for electronic control modules
  • Experienced in defining and validating component and system requirements for test equipment
  • Ability to define project effort and task share and experienced in requirements management
  • Strong programming skills in LabView
  • Well familiar automotive software programming standards and processes such as CMMI and ISO 26262
  • Strong knowledge in communication networks such as CAN, LIN, FlexRay etc.
  • Ability to understand and interpret strategy development criteria and application needs
  • Strong vehicle electronic system background
  • Professional communication skills to be able to present and interact with clients
  • Organized project management skills
  • Ability to mentor and coach other team members

Qualifications:

  • BSEE is required; MSEE is a plus
  • 5 years of experience related to this position is required; 10 years of experience is a plus.
  • In-depth knowledge of electronic control units and electro-mechanical control systems is required
  • Practical experience using NI equipment and software packages (LabView, testStand, etc.) is required
  • Effective project management, organizational, and teamwork skills are required
  • In-depth knowledge of Microsoft Office Suite and MS Project is required
  • Excellent verbal and written communication skills are required
  • Highly motivated individuals with effective organizational skills and team working abilities are required

Pay is commensurate with skills and qualifications of the applicant.  We offer generous compensation packages including a 401k with profit sharing and a generous health plan.

 

If you are interested you can email me at Arisi@techrg.com or call me at 248-546-6900 ext.15.

Link to post
Share on other sites
  • Similar Content

    • By javier_r
      VIPM.io now allows you to post LabVIEW Resources, Ideas, and Tools. For example, you could post a link to a video tutorial or blog article about a package. You can also post ideas, like feature requests or new tools. Best of all, package developers are notified when you post your ideas and resources, and you can comment and discuss posts with the community. Take a look at this video to learn more: https://www.vipm.io/posts/664960df-f111-4e13-989a-24be8207182d/

    • By Shuvankar Das
      I want to connect My ccd camera with labview. The details of my system is given bellow. I cannot connect it please help   OS:  WINDOWS 7, 64bit   LabView Run-Time 2013(64-bit) NI-IMAQ 4.8 NI-IMAQdx 4.3   Camera: QICAM Monochrome Cooled (QIC-F-M-12-C) Model QICAM Resolution 1392 x 1040 Sensor 1/2" Sony ICX205 progressive-scan interline CCD Pixel Size 4.65 x 4.65µm Cooling Type Peltier thermoelectric cooling to 25˚C below ambient Digital Output 12 bit Video Output FireWire (IEEE 1394b) Max. Frame Rate 10 fps full resolution @ 12 bits Pixel Scan 20, 10, 5, 2.5MHz Mount Type C-mount optical format  
       
    • By Bryan
      TestStand Version(s) Used: 2010 thru 2016
      Windows (7 & 10)
      Database: MS SQL Server (v?)
      Note: The database connection I'm referring to is what's configured in "Configure > Result Processing", (or equivalent location in older versions).
      Based on some issues we've been having with nearly all of our TestStand-based production testers, I'm assuming that TestStand opens the configured database connection when the sequence is run, and maintains that same connection for all subsequent UUTs tested until the sequence is stopped/terminated/aborted.  However, I'm not sure of this and would like someone to either confirm or correct this assumption. 
      The problem we're having is that: Nearly all of our TestStand-based production testers have intermittently been losing their database connections - returning an error (usually after the PASS/FAIL banner).  I'm not sure if it's a TestStand issue or an issue with the database itself. The operator - Seeing and only caring about whether it passed or failed, often ignores the error message and soldiers on, mostly ignoring every error message that pops up.  Testers at the next higher assembly that look for a passed record of the sub assemblies' serial number in the database will now fail their test because they can't find a passed record of the serial number. 
      We've tried communicating with the operators to either let us know when the error occurs, re-test the UUT, or restart TestStand (usually the option that works), but it's often forgotten or ignored.
      The operators do not stop the test sequence when they go home for the evening/weekend/etc. so, TestStand is normally left waiting for them to enter the next serial number of the device to test.  I'm assuming that their connection to the database is still opened during this time.  If so, it's almost as though MS SQL has been configured to terminate idle connections to it, or if something happens with the SQL Server - the connection hasn't been properly closed or re-established, etc. 
      Our LabVIEW based testers don't appear to have this problem unless there really is an issue with the database server.  The majority of these testers I believe open > write > close their database connections at the completion of a unit test. 
      I'm currently looking into writing my own routine to be called in the "Log to Database" callback which will open > write > close the database connection.  But, I wanted to check if anyone more knowledgeable had any insight before I spend time doing something that may have an easy fix.
      Thanks all!
    • By javier_r
      Hello everybody!
      Wondering how many people have tried the new vipm.io site. We have added a ton of features to make it easy to Discover LabVIEW Tools and there are some cool ones coming soon.
      Check it out and let me know what you think 😀
       
      Javier

    • By DigDoug
      CLA_ATM_QMH_PRACTICE.zipHi Folks,
       
      I'm taking the CLA exam in a few weeks and would like some feedback on the solution I put together (attached). A few specific questions:
      Can I dump tags in the VI Documentation of the VI like I did in Error Handler - Console Error.vi and get credit since there are instructions for developers to complete this work? This would be my strategy if I run out of time. 
      Does this seem like a passing solution? Why/why not?
      Where do you think I would lose the most points in this solution?
      Any other feedback on this exam or general strategy tips are greatly appreciated!
       
      Best Regards,
      Aaron
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.