epaulson
December 2nd, 2004, 04:19 PM
I came here looking mostly for a Win32 API developer - the C++ and WinAPI forum has the perfect audience for what we're looking for this job. We have several other jobs that are more UNIX oriented open as well.
These are all full-time positions in Madison, WI at the University of Wisconsin department of Computer Sciences. We're not interested in contracts, and telecommuting is not an option. Please, no head-hunters, we can't pay anyone for referrals. It is also unlikely that we could provide any relocation expenses.
None of the jobs have "closed", please do not let the University website's application due date deter you.
Thanks,
-Erik
===================
Please pass this along to anyone you might know:
http://www.cs.wisc.edu/condor/jobs.html
We've got 7 jobs open:
1 in a Win32 development role - this person will need to know things
like all the arguments to CreateProcess on windows, how to twiddle with
permissions to the current WindowsStation, etc - low-level things. This
is not an MFC job. If you own just one book, Richter wrote it. You're
a big fan of www.sysinternals.com
1 sysadmin job - mostly managing various UNIX platforms and development
tools. Not much networking, not many real services to manage (no mail or
backups to worry about), but we do aim for "production" with the Condor
pool. Most of our machines use cfengine to keep configurations sane and
LDAP to get their passwd information from.
3 jobs doing software packaging/testing for Grid software - basically,
you can think of this as working for Redhat, but on a Grid Software
distribution instead of a Linux distribution. Some things in these
distros include Condor, an enhanced version of OpenSSH, some network
monitoring tools, an FTP client. These people will be responsible for
building (as well as integrating any patches that we may need to make)
and testing - a lot of it is building testing infrastructure so we can
have a nightly snapshot that we do regression testing with - so in some
sense you're building infrastructure like SourceForge. This person needs
to be a mix of sysadmin and programmer, with probably more sysadmin than
programmer. (Basically, all-around hacker)
1 job doing security research - so you're not watching the IDS, but you'd
better know some shortcomings in current IDSes, and have some ideas in
how you'd improve them. If you're gonna name-drop, your best bet is to
name-drop from the USENIX security conference program committee.
1 job programming, enhancing Condor-G - which is our interface to
other batch systems. This is mostly C++ and UNIX systems coding. If you
own just one book, it should be the Stevens Networking book.
These are all full-time positions in Madison, WI at the University of Wisconsin department of Computer Sciences. We're not interested in contracts, and telecommuting is not an option. Please, no head-hunters, we can't pay anyone for referrals. It is also unlikely that we could provide any relocation expenses.
None of the jobs have "closed", please do not let the University website's application due date deter you.
Thanks,
-Erik
===================
Please pass this along to anyone you might know:
http://www.cs.wisc.edu/condor/jobs.html
We've got 7 jobs open:
1 in a Win32 development role - this person will need to know things
like all the arguments to CreateProcess on windows, how to twiddle with
permissions to the current WindowsStation, etc - low-level things. This
is not an MFC job. If you own just one book, Richter wrote it. You're
a big fan of www.sysinternals.com
1 sysadmin job - mostly managing various UNIX platforms and development
tools. Not much networking, not many real services to manage (no mail or
backups to worry about), but we do aim for "production" with the Condor
pool. Most of our machines use cfengine to keep configurations sane and
LDAP to get their passwd information from.
3 jobs doing software packaging/testing for Grid software - basically,
you can think of this as working for Redhat, but on a Grid Software
distribution instead of a Linux distribution. Some things in these
distros include Condor, an enhanced version of OpenSSH, some network
monitoring tools, an FTP client. These people will be responsible for
building (as well as integrating any patches that we may need to make)
and testing - a lot of it is building testing infrastructure so we can
have a nightly snapshot that we do regression testing with - so in some
sense you're building infrastructure like SourceForge. This person needs
to be a mix of sysadmin and programmer, with probably more sysadmin than
programmer. (Basically, all-around hacker)
1 job doing security research - so you're not watching the IDS, but you'd
better know some shortcomings in current IDSes, and have some ideas in
how you'd improve them. If you're gonna name-drop, your best bet is to
name-drop from the USENIX security conference program committee.
1 job programming, enhancing Condor-G - which is our interface to
other batch systems. This is mostly C++ and UNIX systems coding. If you
own just one book, it should be the Stevens Networking book.