Perm Linux openings

[John Spencer]

I have several perm openings for Linux engineers in MA. Our clients have
come to us looking for help. Please contact me at the number or email
address below. The positions are as follows:
 
Linux Architect in northern MA. Will be responsible for architecting and
implementing the routing software in the next gen product. Must have 10+
years of embedded software development experience. Experience with Linux as
an embedded OS and C programming is required. Experience with routing
protocols is a plus.
 
Linux Architect in northern MA. Will be responsible for architecting and
implementing the routing software in the next gen product. Must have
extensive experience with kernel features such as networking, high
availability, error handling kernel modules for various devices such as
GigE, flash, etc.
 
We are also looking for a Project Lead and Sr./Prin contributing Linux
engineers for the above mentioned projects.
Please call or email for additional details.
 
Linux Engineers (5+ years) west of Boston along 495 Will be responsible for
participating in the ongoing new development efforts to keep current with
the latest versions Linux, port Linux to the latest HW platforms. Continue
to make modifications in Linux including providing for SCSI and PCI hot-plug
support (including surprise removal of devices), overall hardening of a
select set of Linux device drivers to adapt them to the environment and
making Linux work with the appropriate hardware.
Please call or email for additional details.
We get new Linux related openings on a regular basis, so even if you are not
a fit for the above mentioned openings, please do not hesitate to contact me
via phone or email so we can discuss your background and desired role(s) in
detail. 
John Spencer 
Sr. Staffing Consultant 
ProStart Inc. 
603-893-7772 ext 45 
603-893-7704 fax 
mailto:johns at prostartinc.com <mailto:johns at prostartinc.com>  
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.blu.org/pipermail/discuss/attachments/20030911/2d29cdbe/attachment.html>