The Personal Health and Information Technology department at the Centre for Global eHealth Innovation is looking for a Hacker / Software Generalist / Researcher:
Every member of our tightly knit development team has full input into every stage of project architecture, design and implementation. We own our projects and get shit done that has real, meaningful and measurable impact on sick people’s lives.
- Have enough experience in Java to be sick of it
- Have experience with the JBOSS stack
- Have professional experience with a dynamic language such as Ruby or Python or Javascript
- Be a UNIX weenie
- Have open source contributions they can show us
- Have mobile app development experience, on any combination of the iPhone, Android and Blackberry platforms, or on Titanium, PhoneGap, or other cross platform tools
- Be comfortable working in a Scrum process
- Be fanatical about testing
Grant McInnes, who sent in the posting, adds:
we do everything from hardware development, up the stack through software development, to UX evaluation and finally randomized controlled trials on the built products
The Good
It sounds like a great cause:
We have good results. In a randomized controlled trial, our applications have been shown to significantly improve heart failure outcomes, in patients with Congestive Heart Failure. In another we’ve demonstrated a 10 point drop in blood pressure for hypertensive patients
How often do you get to look at a software job where you can contribute to saving lives?
It also sounds like they use a fair number of technologies and have pretty sound processes. There’s not a ton of detail there, but what’s there sounds good.
YMMV
Who is the Centre for Global eHealth Innovation, to which the Personal Health and Innovation department belongs, anyway?
The Centre for Global eHealth Innovation is “a joint effort of UHN and the University of Toronto and was built with funds from the Canadian government, through the Canada Foundation for Innovation, and the Ontario Innovation Trust”. Phew. And then of course the UHN is itself a bunch of different entities working together. The Canada Foundation for Innovation and the Ontario Innovation Trust are both government organizations created to foster innovation at the Federal and Provincial levels. So, basically, take a university, several hospitals, two branches of government and assorted others and put them together and you have the Centre for Global eHealth Innovation.
It sounds like the possibilities for endless meetings, paperwork and mayhem abound without even talking about how Conway’s Law fits into this. Of course, universities, governments and hospitals can be fulfilling places to work, so maybe your mileage may very a little, and you’ll find the combination appealing. It sounds a little scary to me. The posting talks about some of the upside of this arrangement:
Being in a research environment, we are able to concentrate on this goal without being distracted by short term profit motives, or keeping investors happy.
The Location
Sounds like they’re in the Toronto General Hospital, over by MaRS, Hospital Row, etc. There are restaurants and shops around, although it’s not overflowing with great eats and hip places from my limited experience in the area. It’s very transit-accessible, but it’s not ideal for go train (you’d want to take the subway, at least in winter) or driving. The location is probably neither off-putting nor exciting for most of you. On the upside, you could take in events at MaRS pretty easily.
What’s Missing
What’s the compensation like for a Researcher at the Centre for eHealth Innovation? What’s the size and composition of the team? How would you fit into it? What’s that crazy organizational structure like in practice — does it get in the way or is it something that you’re barely aware of?
Is there a particular project that you’d be starting on? What are the technologies and platforms you’d likely be working with right away and what is the mix going to be like over the long haul?
What are their development practices like? There’s a mention of Scrum, but in practice companies vary quite a bit. It’s hard to get too deep into specifics without knowing more about the technological mix but: do they do pairing? Do they use digital issue tracking or card boards (kanban, etc)? Is there a build? Continuous integration? How often are deployments/releases made? What’s the workspace like?
Maybe Grant can answer some of these here, but these are the kinds of questions you might consider asking them yourself.
In Summary
If you’re looking for a good cause with decent technology and practices, this sounds like it’s worth further investigation.