PharmaTrust: Platform Service Developer

PharmaTrust (PCA Services Inc) is looking for a Platform Service Developer:

PharmaTrust (PCA Services Inc) is a cutting edge dynamic start-up in the field of telepharmacy, producing the MedCentre remote medication dispensary. The MedCenter provides pharmacists with the ability to remotely counsel and dispense medication using IP based audio/visual conferencing and a remotely controlled dispensary robot system.

Platform Services develops and supports the PharamTrust Platform and provides shared enterprise services to the PCA Services group of companies.

The Platform Service Developer has the responsibility for developing the PharmaTrust Platform Services, integrating other systems applications and databases (both internal and customer), and evolving the Platform Train of the MedCentre application software.

They’re also looking for a Platform Technical Support & Maintenance Specialist.

The Good
These robot dispensaries seem like a good idea to me.  The Albany Medical Clinic had one, and it was interesting.  IP-based audio/video conferencing and e-health all rolled into one project.  There’s definitely some interesting elements to this, and these dispensaries are new enough that PharmaTrust might be on a good trajectory over the long haul.

YMMV
It sounds like they’re in the middle of a technical overhaul from a .NET system to a Java/ESB system (and the support/maintenance specialist would continue to maintain the existing .NET side, looks like).   That means there’s an opportunity to really get in on the ground floor of the new architecture, as long as the architecture sounds like something that would work for you.  Personally by the time you throw ESB and BPEL together, I’m already starting to get nervous, let alone combined with WS-*, a platform shift and technical challenges like SIP.  Your mileage may vary significantly from mine, but I’d want to get a stronger sense for the architectural direction, and whether or not there’s any astronautics involved.

On the other hand, if ESB and WS-* sound like the right way to build a robust, enterprise-class, scalable system with all the -ilities you need, by all means, this might be the perfect fit for you.

What’s Missing?
Why the architectural shift from .NET to Java?  What are the driving factors behind the choices of ESB, BPEL, WS-*?  What’s the current size and composition of the technical team, and how will that change on the new platform?  What’s the compensation like for this position?  What’s the growth and outlook for MedCentre like?  (It seems promising to me, but if this is going to be your company, you might as well have more details than I do.)

I don’t really expect a company to describe the reasons for their technical decisions in a job posting, but it seems like the sort of questions you’re going to want to ask.

The Location
It’s in Hamilton, Mississauga, Oakville or Toronto?  I’m going to assume that’s a result in trying to cast a wide net for candidates in any of those locations.  Their office seems to be in an industrial park in Oakville, which means that if you’re not already in the west end of Toronto or out of town, the location will probably be too far out.  I don’t know much about the area; if that area is somewhere you consider, you probably already know more than I do.

In Summary
Looks like it’s be well-suited for someone with enterprisey leanings, health-care and some exposure to both Java and .NET, in the west end.

Advertisements

2 Responses to PharmaTrust: Platform Service Developer

  1. Eric Carroll says:

    Thanks very much for the posting.

    As you surmise we are based in Oakville right on the Mississauga border. The office is directly between the 403 north of us and the QEW immediately south. I personally come in from downtown Toronto.

    In terms of technology, we are not moving away from .Net, we are focusing on realizing our expanded solution vision with new products in the pipeline. We are also hiring .Net developers and Control Systems developers: http://www.workopolis.com/EN/job/11643666

    We have significant systems integration requirements that are more amenable to WS-* treatment using middleware (ESB). And as anyone who has done a large scale platform play knows, licensing costs can play a major consideration of the business case and must be balanced carefully. Exposure to .Net for this position is nice to have but not essential.

    I personally have spent many years doing middleware, and have significant SIP background in addition to large scale platform plays.

    Happy to answer the more detailed strategy & compensation questions one on one for anyone seriously interested.

    Eric Carroll
    CTO, PharmaTrust
    http://www.linkedin.com/in/ericcarroll

  2. It’s certainly true that when integrating with pre-existing systems, WS-* can be better-supported than the alternatives (although it varies widely by the systems with which you’re integrating).

    My personal experience with ESB was entirely unenjoyable, but I hope that’s less true for you.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: