job opening at MGH
Our group is looking for a new software engineer.
The open req is the usual "our recruiters want a lot of checkboxes" boilerplate. Here's the relevant summary:
* When people have surgeries, there are a lot of surveys that are done: pre-op, post-op, 3 months after, 6 months, 12, 24, 36, maybe 5 and 10 years. Depends a lot on the particular surgery, but since our group is orthopaedics, we tend to track people for a long time.
* We're trying to get all this info into a single registry so that researchers can do research-y things. Right now, the best registry is in Sweden -- all ortho surgeries are recorded there. If we could get all of, say, NY into a single registry, then we'd be producing just as much data.
* This is all very interesting because you can start asking questions like:
+ Does surgical technique matter? For a hip operation, you can have the patient lying on their back, or side, or on their front -- what matters? What are the tradeoffs of minimally invasive surgeries?
+ How are products performing? If we see a particular component is failing after 3 years, then we don't need to wait 20 years to say that it's crap.
* Our current code base is terrible. We're in the very long process of throwing it all away and replacing it. I am advocating moving to a SQL database, with something like Hibernate taking care of a lot of the persistence layer; at the top, a GWT-based GUI. We use Java.
* Thus: we're looking for people who want to do Java work. We have no (my)SQL wizards nor Hibernate wizards, so experience in either/both is a plus. Experience in GWT is a plus. Plus the usual: good people skills, self-starter, smart.
I'm guessing we're looking for more mid-level to senior-level people, as it would be difficult for us to mentor a new grad. That said, I'm mostly happy to talk to people: my only hard-and-fast rule is good people skills.
Questions, etc, drop me a line. Feel free to forward.
The open req is the usual "our recruiters want a lot of checkboxes" boilerplate. Here's the relevant summary:
* When people have surgeries, there are a lot of surveys that are done: pre-op, post-op, 3 months after, 6 months, 12, 24, 36, maybe 5 and 10 years. Depends a lot on the particular surgery, but since our group is orthopaedics, we tend to track people for a long time.
* We're trying to get all this info into a single registry so that researchers can do research-y things. Right now, the best registry is in Sweden -- all ortho surgeries are recorded there. If we could get all of, say, NY into a single registry, then we'd be producing just as much data.
* This is all very interesting because you can start asking questions like:
+ Does surgical technique matter? For a hip operation, you can have the patient lying on their back, or side, or on their front -- what matters? What are the tradeoffs of minimally invasive surgeries?
+ How are products performing? If we see a particular component is failing after 3 years, then we don't need to wait 20 years to say that it's crap.
* Our current code base is terrible. We're in the very long process of throwing it all away and replacing it. I am advocating moving to a SQL database, with something like Hibernate taking care of a lot of the persistence layer; at the top, a GWT-based GUI. We use Java.
* Thus: we're looking for people who want to do Java work. We have no (my)SQL wizards nor Hibernate wizards, so experience in either/both is a plus. Experience in GWT is a plus. Plus the usual: good people skills, self-starter, smart.
I'm guessing we're looking for more mid-level to senior-level people, as it would be difficult for us to mentor a new grad. That said, I'm mostly happy to talk to people: my only hard-and-fast rule is good people skills.
Questions, etc, drop me a line. Feel free to forward.