Engineers build things that solve problems. And healthcare today is a problem.
Patientco is working to simplify the complex world of healthcare, and we need engineers to do that. We invest in our engineering team. Founded by a pair of Georgia Tech engineers, we understand the needs of our engineers and have built the company around them. Patientco is, at our core, a software company that understands technology, focuses on building a single product, and allows our engineers to have variety and impact in their work.
The Co-op Program
We offer a robust software engineering co-op program through Georgia Tech. From day one, co-ops are embedded directly into the development team and are considered full-fledged members of the engineering team. You’ll be challenged, and at times it will be hard. Like all of our engineers, we will ask a lot of you — but every step of the way you will be supported. You’ll learn from the best. And we promised — you’ll have fun doing it!
WE’RE BIG BELIEVERS IN AGILE — ALTHOUGH NOT DOGMATICALLY.
Over the years, we’ve adapted the best parts of agile that work for us and left the rest. We now run two flavors of agile – Scrum and Kanban. Teams pick the option that best suits their needs, but across teams we believe that all projects – no matter how big – can be broken down into small pieces and worked on iteratively. Our ticketing system (JIRA and its Agile extension) keeps us honest about scope changes and ensures there is complete visibility into the progress of each work item. We hate rotting code (code that is stuck in the process rather than in production in front of users) so we generally deploy soon after code has run through our automated test suite and has been user-tested.
Since we know engineers need to work on a Maker’s Schedule, not a Manager’s Schedule, we’ve done several things to ensure the sanctity of coding time, including optimizing the office layout, minimizing meetings, and designating an “on call” engineer to prevent unnecessary interruptions.
PEER CODE REVIEW
We invest in code from the beginning. 100% of code goes through a peer code review process.
Tests shouldn’t be a separate ticket or process — it’s a step in the core ticket. Since we handle medical and payments data, our code needs to be right — every single time. We have an extensive suite of unit tests (PHPunit), integration tests, and front-end tests (Selenium). Yet, we keep the process agile. We’re not strictly Test Driven, nor do we think 100% code coverage is the right strategy – it’s about being smart and balanced.
Once a week we join together for a Retrospective Meeting. It’s purpose is to talk about what can be improved about our development process itself. It’s how we limit the bureaucracy and keep work moving through the system smoothly. You’ll have a voice, every week.
Our work balance is split pretty evenly between major product enhancements, brand new modules, and implementation/support/maintenance. One day you’ll be building IVR telephony applications and the next, a high-availability, robust transaction engine. We’re solving new challenges every day to make our product better for our customers.
We’re a largely PHP and MySQL shop — including our backend systems. By writing all of our core software in PHP, all developers can work on any system component and be cross-trained. Our code is clean and object-oriented, built around the Colony MVC Framework. While we generally prefer open source software, we invest in commercial tools when it makes sense.