We love to brag about how much our customers love our software, but it turns out that might be because our team loves to build it. Since we’re hiring, we decided to ask our engineers what makes working at Medtelligent so special.
Here’s what they had to say.
#1: We’re Not Stuck in the Past
“Our CEO John Shafaee likes to say, ‘we pay our technical debt as we go’,” says William Metcalf, senior software engineer. He says that has some pretty exciting implications. “[This means] as developers we always have the opportunity to try out the latest technologies, instead of being forced to support old legacy code.”
Nichole Baiel, user experience engineer, agrees, “I like that we’re encouraged to investigate and use new technology whenever we can. At a lot of companies, you’re often stuck supporting older, deprecated frameworks.”
CTO Huzaifa Tapal explains that it’s a relentless focus on the users and user experience that drives this philosophy. “We are not the type of company that sticks with a technology or a way of doing something just because it’s there or what we’re “used to”. We’re always looking for ways to improve the experience and if that means changing to a new technology we do it. And we don’t just apply that approach to new problems, we take the time to improve our existing features, too.”
#2: We’re Encouraged to Grow
Many of our engineering team members have “grown up” here, and developed their skills through mentoring and on-the-job training, says Tapal. Grant Overby, backend developer, says “As a junior dev coming into Medtelligent, this place is a gold mine. They really believe in putting the time and effort to grow a developer’s skills. You read about other places that just throw you at a workstation and you work on the same task over and over again with little proctoring from your senior devs, but here it couldn’t be more opposite.”
Leona Quist, quality assurance engineer, had similar comments. “This is actually my first tech job. What’s neat about Medtelligent is that they will take you at your current level and work with you to acquire new skills to be the best you can be in your role.”
In fact, Tapal explains, professional development is baked into the team’s work process. For example, “almost all of the developers on our team started out as junior developers. We teach as we go by pairing incoming developers with a senior dev. Everyone starts by fixing defects since it’s the fastest way to get to know all areas of the application. When it’s time to go deeper, we ask them to own a new feature and we support them through the process, often by pair programming. At the end, we do code reviews before it’s finalized.”
#3: We Solve Problems As Equals
“While we have separate teams for different areas of the product, and each person has a defined role, we solve problems together,” says Tapal. “We don’t have these senior engineer / junior engineer dynamics. We brainstorm together as equals; we want everyone to have a contribution and be a part of the solution.”
In the end, Tapal says, what unites the team is an openness to learning. “That’s what excites us and what we all have in common as a team. We get excited when we learn something new, whether that’s from each other or as a result of an exploration into new ways to solve the problem.” Overby proves that point, saying, “This is hands down the best place I’ve ever worked. I wake up in the morning excited to come in and learn something new.”
#4 We Have Autonomy…AND Support
It turns out that when you hire for potential, train for skills, and engage everyone as equals you end up with an exceptionally close-knit team. Metcalf says the people on the team are the number one thing that makes working at Medtelligent different. “We have a team where everyone supports each other and cares greatly about their work. While we have the autonomy to solve problems on our own, we have the support of an extremely tight-knit group, too. We really collaborate well together.”
If this sounds like a team you’d like to join, we want to hear from you! The Medtelligent engineering team is growing.