Assuming that your predecessor acted in a professional manner, then I would probably contact the individual after I'd had a chance to take a look at how everything had been laid out.<p>Non-profits may not have a lot of money for technology, and the recent economic disruptions have really hit them hard due to the drop in funds they get from corporate/other giving.<p>I would expect to run into a lot of older equipment all duct-taped together in a non-logical fashion. This isn't something that you should blame the predecessor for, sometimes we have to make non-optimal choices given the constraints we work under.<p>As an aside about working in the non-profit sector, I've been employed as the only IT person for a smaller nonprofit (~30 users or so) for almost 4 years. You may have heard the phrase "the smaller the stakes the more fierce the fight" from academia, it also holds true in the non-profit world. (and I suspect in any human organization, but my experience has been mostly in the academic/non-profit sector thus far.) Expect to run into budget issues, and nasty personalities.<p>Fortunately, on the budget front organizations exist for IT software/hardware giving that can really help out.<p>One that I've used: TechSoup.org<p>Many major software vendors offer discounts for non-profits if you look around.<p>Plus you can always use linux/freebsd/openbsd/etc on commodity hardware to help keep costs down. At the cost of time depending on your skill set.<p>I expect you may have already heard a lot or all of the above, so feel free to ignore it!<p>Oh, and if you get the job, Congratulations!