Solutions Engineer, PocketHealth

• 5-10 years in a customer-facing technical role: solutions engineering, sales engineering, solutions architecture, technical account management, or implementation consulting
• Experience working in an early stage, high-growth environment, where speed and flexibility are paramount
• A working understanding of enterprise architecture(hybrid and public cloud), systems, and infrastructure, and the confidence to discuss it credibly with hospital IT teams, executive leadership, and security
• Understanding of best practices and proper use cases for healthcare protocols, identity and access management, public cloud services, and data handling
• A genuine interest in information security. You do not need to arrive as a security analyst and we will ramp you, but the curiosity has to be there, because a meaningful share of this role is security review work and understanding how to safely deploy technology
• Strong written communication. Much of your output is documentation another party will make a purchasing decision against
• Comfort operating across both strategic and routine work. Some of this job is high-stakes solutioning on complex deals; some of it is disciplined, careful documentation, and both matter
• Based in the GTA, with the ability to work from our downtown office twice per week
• You can do amazing things at PocketHealth. You can positively impact the healthcare journey for millions of people, while building your career and developing your skills
• It doesn’t have to be one or the other. It has been a part of our mission since our founding to empower patients & make healthcare accessible to all, and we know this can only be achieved with a team of diverse perspectives that is representative of the Patient & Provider communities we serve

Desirable

• PocketHealth is scaling its sales engineering function as demand for our products has outgrown our capacity
• This role will sit alongside the Sales team to operate as a technical subject matter expert on customer/prospect calls, and to create and review the technical documentation required to keep deals moving quickly, across our full product suite
• You will own the technical work that keeps deals moving day to day: customer calls, security reviews, RFP responses, statements of work and scoping documentation
• The goal is that our most complex enterprise opportunities have a technical resource assigned from the early stages. You will be mentored directly by our Enterprise Architect and will grow into full ownership of a segment of the business
• This is a customer-facing role from day one. Working in tandem with Account Executives, you will be introduced to prospects and current clients as our Solutions Engineer, and will own the technical relationship and deliverables with hospital IT leaders, security teams, and radiology operations stakeholders
• Join sales calls as the technical authority on behalf of PocketHealth, particularly where the prospect/customer includes a technical stakeholder
• Answer architecture, integration, and infrastructure questions with credibility and in the moment. Know where the boundaries of the product are
• Demonstrate critical thinking and business acumen to answer questions accurately while aligning technical capabilities to product value
• Use technical calls to broaden our footprint in an account, bringing additional stakeholders into the conversation
• Work with external stakeholders, as well as internal Legal and Compliance to complete security reviews (questionnaires, spreadsheets, and vendor portals)
• Draw from and help maintain our centralized repository of reviewed security answers, working alongside the compliance function in Legal, and apply judgment to every answer
• Turn call outcomes into finished deliverables such as follow-up answers, scoping notes and integration write-ups, on the tight timelines deals actually run on, so that momentum is never lost waiting for documentation
• Build statements of work for product implementations that reflect the real implementation effort, including integration method, data access, and dependencies
• Flag complexity triggers that change the cost or price of a deal: unusual technology stacks, non-web-based applications, protocol-heavy workflows, or requirements that need internal subject matter expertise. Raise them before a contract is signed
• Validate integration assumptions early
• Translate customer technical requirements into internal feature or build requests, exhausting existing product capability and completing a preliminary technical evaluation, engaging Engineering strategically
• Partner with deployments and forward-deployed engineering so that what was sold is what gets deployed
• Coach account executives on the technical questions worth asking, raising the quality of qualification across the team