Medisas helps doctors and nurses share critical patient information during handoffs, where patients are transferred between providers. Handoffs account for 80% of serious medical errors, which kills 400,000+ people annually. Our cloud-based tools and next generation APIs integrate deeply with any EMR or other ancillary healthcare systems to improve workflow and communication in real time, when every second counts.
Each team is asked to select, explain, and rank their top 8 values in order of importance.
Team is Diverse
In medicine, caring for patients requires a multidisciplinary approach: everyone from doctors to nurses to the pharmacists, specialists, and case managers, is involved and necessary to deliver high quality care. We use the same approach as a technology company.
A variety of expertise, personalities, and backgrounds are represented at Medisas, and that’s not by accident. With about a third female engineers, our development team has a range of backgrounds from traditional computer science and engineering to economics and psychology. Our engineers bring best-in-class training from leading tech companies like Google and Apple, to world-renowned finance companies like BlackRock, to healthcare software companies, like Epic and One Medical Group. We believe the best solutions rely on the perspectives and experiences of a diverse team, and the best working environment is one of mutual respect, open-mindedness, communication, and inclusion.
You own a project but aren’t on an island.
The development and code review process allows for multiple eyes on code and multiple minds thinking about the optimal solution. You set the deadlines, you set the pace, you make decisions and own the outcome.
Committed to Personal Growth
The foundation of our team is cemented in a never-ending curiosity, a lifelong learner mindset, and the ability to give and receive feedback.
Formally and company-wide, we organize biweekly Lunch & Learns on a range of topics from Population Health Management to Lean Startup Principles to SF Recology Initiatives, and we provide a library budget upon joining to help share individual learnings with the whole team. Everyone also receives a yearly education allowance to use for training, conferences and books. Informally, we support and encourage a lot of interpersonal knowledge and feedback sharing, an obscene amount of question asking, and the pursuit of passions outside the office walls! For an inside look, our VP of Engineering Linda often speaks to how Medisas encourages her to stretch her limits and grow.
Impressive Team Members
The most impressive thing about our team members is their high emotional intelligence, their deep capacity to care, and their low ego. Those are non-negotiables to join.
Linda, our VP of Engineering, received her Bachelor’s from Cornell and Master’s from Stanford, and started her career at IBM and Google before gravitating towards smaller startups like Cardspring and Medisas. She’ll impress you with the difficulty grade of her bouldering, the amount of rice pudding she can consume in one sitting, or the number of code reviews she can complete in one night. If nothing else, she can break an apple in half with her bare hands.
We have company-wide initiatives that are driven by cross-disciplined project teams, and project teams are owned by a Directly Responsible Individual (DRI).
For a recent new product idea, we wanted to get to a demoable MVP ready in 4-6 weeks, which we had never done before. We brought together 2 product designers, 2 business team members, and 1 engineer into one war room for 6 hours a day, 5 days a week for the first 2 weeks. We invited a design partner from our of our VCs to help lead our initial design sprints, and after we had some low fidelity prototypes, we had our business team reach out to super users at our client sites to set up feedback sessions where everyone involved sat in. Through quick feedback, prioritized iterations, and close teamwork, that project team was able to prove out a market that could result in a new line of revenue for the company. Without the business team, the team would not have had the relationships with clients to get useful feedback in a short window. Without the designers, there wouldn’t have been prototypes to show or user research to build from. Without the engineer, there wouldn’t have been a demo built. At the end, the engineer noted this was his favorite project because the depth of the additional context he had from the business side allowed him to make better decisions on the development side.
We believe in soliciting and sharing information and feedback early and often through various different channels.
Whether it’s something as simple as cc’ing mailers on correspondence or something more involved like a 2-hour company-wide retrospective bi-annually, we bias towards over communication, transparency, and open-mindedness. We have quarterly surveys, weekly 1:1s and All Hands staff meetings, and daily morning syncs. We believe in talking openly in a group (e.g., our All Hands agenda is set by the team), but we also believe in written dialogue so that individuals who prefer to communicate that way can. We are honest and vocal with each other, however difficult or uncomfortable it can be, because we care about personal development and team success.
Friends Outside of Work
We exercise together. We karaoke together. We send each other Snaps, and invite each other to birthday parties and BBQs.
When you are surrounded by passionate, thoughtful, and interesting people, why not be friends?
Because our product saves lives and because every team member believes in the need for it, we all make decisions that prioritize product improvement.
We want deliver a standout user experience. We want to improve product performance. We want to build additional features that will actually help patient care. As a company, we want to do all of this so clinicians can quickly get the relevant information they need in time-sensitive moments when making critical decisions.
Our interview process consists of a tech screen (where you can expect typical algorithms/data structure/coding questions) and an onsite. During the onsite, instead of having you code on a whiteboard, we prefer to work through hands-on problems together. We hope and expect that you’ll also be interviewing us to determine if there’s a mutual fit.