How to Apply: Interested and qualified? Go to Andishi on www.linkedin.com to apply.
Master the Legacy-to-Cloud Migration Story
This role is about untangling a messy HL7 environment and moving it to the cloud. Hiring managers will probe how you've handled legacy systems, documented chaos, and planned migrations without breaking clinical workflows.
1. Map your HL7 war stories: Be ready to walk through a specific time you audited an HL7 environment. Mention the number of channels, the mess you found, and how you prioritized cleanup. Concrete numbers stick.
2. Show Mirth mastery beyond basics: Don't just say you used Mirth. Talk about building channels with JavaScript transformers, handling ACK/NACK, and debugging routing logic. Bring a small code snippet or diagram if you can.
3. Prove you can document like a pro: This job lives on documentation. Share a sample runbook or architecture diagram you've created. Show you can turn tribal knowledge into something a new engineer can follow.
4. Speak the radiology language: Even if you're not a DICOM expert, show you understand PACS workflows and the risks of duplicate reads. Mention DCM4CHE or similar tools you've touched.
5. Prepare for the 'how do you handle ambiguity' question: You'll be dropped into an undocumented system. Have a story about how you reverse-engineered a legacy interface with no help. Highlight your investigative process.
6. Get cloud-ready: Since you'll move services to AWS or Azure, brush up on basic cloud networking, security groups, and how HL7 interfaces run on VMs or containers. Even a side project helps.
7. Practice explaining tech to non-tech: You'll talk to clinical ops. Prepare a simple analogy for HL7 message routing or PACS synchronization. Show you can translate jargon.
8. Ask smart questions: In the interview, ask about the current infrastructure, the biggest pain points, and how success is measured. It shows you're already thinking like a consultant.