job description
The successful IO R&D driver developer candidate will work with senior software designers to learn how to write HP-UX (Unix) drivers by first learning how to write software to test existing drivers. Candidates will learn to setup and configure driver unit test environments, write specific unit tests, automate them inside the test harness, develop unit test planning and execute unit testing under direct supervision of a senior engineer. There is little expectation for the candidate to have had significant previous industry experience to perform at this level. The candidate will apply the foundation of experience gained from lab and classroom and/or previous Intern position toward solving problems of limited scope. As experience is gained and job-specific training is taken, the candidate will apply their knowledge of project planning, hardware and software configuration, operating systems, scripting and software development experience toward driver defect find and fix. This engineer will be expected to learn how to use software debugging tools and techniques, protocol analyzers, sort out driver code paths, learn how drivers manage interrupts, understand how drivers utilize kernel data structures and manage IO errors, etc. The candidate will be expected to aggressively learn and to apply some/all skills gained to continue to take on more complex defect fixing and development as an HP-UX driver developer.
This role requires the candidate to work efficiently with minimal supervision, be self-motivated and organized This person must also be comfortable working as a member of both local and remote teams, working with multiple technical leaders at any given time and to work easily with engineers in partner organizations. It is desirable for the candidate to be familiar with and have some experience developing software for either a Unix or Linux based operating system, preferably HP-UX, and have some systems development knowledge such as kernel, drivers, compilers, routers, networking stacks, system/IO utilities, databases, etc.
0 comments:
Post a Comment