Engineering Team at Routific

Routific is a smart logistics platform that optimizes routes for last-mile delivery fleets, saving businesses up to 40% on time and fuel. Today, the power and efficiency of our proprietary algorithm combined with a stellar user experience makes Routific the best routing solution on the market and the leading route optimization API.

Job Openings at Routific

Top Engineering Values

Each team is asked to select, explain, and rank their top 8 values in order of importance.
  • Open Communication

    Transparency is something everyone on our team values. In fact, our team members have selected it as one of the most important core values at Routific.

    Being transparent means not running the business like it’s a black box. As an example, we share the company’s finances with the entire team. Everyone on the team knows exactly how much money we have in the bank, how many months we have left before we run out of money, what our go-to-market plans and targets are, and how close we are to achieving those targets.

    Transparency means being open and vulnerable with one another. We encourage our team members to come into the office, put their ‘work’ face away, and be themselves. It doesn’t happen overnight, but we are always working on it together as a team. Recently, every team member completed the Myers-Briggs personality test which gave us phenomenal and actionable insights into the different personalities on our team. It changed the way we perceive one another, talk to one another, and how we interact as a team.

  • Heavily Team Oriented

    We celebrate team successes.

    It’s a reflection of how humble we are and what motivates us day-to-day. Team members will go out of their way to help each other, even if it means that their personal tasks will fall behind, so long as it is in the interest of the greater good.

    We emphasize this by aligning the entire team around a common team goal and being fully transparent on how we progress towards that goal. And when we meet those goals, we celebrate as a team! Recently we took the entire team on a 3-day retreat to Whistler and went white water rafting. We have monthly social events where significant others are always welcome.

    Another example is how we do our year-end bonuses, which are tied transparently to team objectives, rather than individual ones. In that way, either the entire team wins or the entire team loses!

  • Committed to Personal Growth

    We believe in leading healthy lifestyles, and finding a good balance between time spent in front of a computer screen and time away from it.

    At Routific, our team members have a lot of flexibility with their schedules. While we try to all be at the office between 10 a.m and 6 p.m. on weekdays, team members take the opportunity to work remotely when it suits them and we have a “Work From Home” tradition every Wednesday. We provide stipends for courses, conferences, or workshops that our employees wish to attend.

    At a recent all-hands, we shared stories about personal growth. One of our full-time engineers, Jonathan, talked about how he first started out as an intern at Routific: “I was just a co-op intern, but I was trusted to work on the core algorithms,” Jonathan said. “The founders flew the entire team, including me, to Chicago to participate in the Techstars program.”

    We also commit to personal growth and development in a very public way, in line with our core value of transparency:

    At a recent company-wide feedback session, each team member wrote down a few lines of feedback for every other team member: one thing they should keep doing, and one thing they can improve upon. We went around the room and shared this feedback – publicly – with one another. The person receiving the feedback was encouraged to say ‘thank you’ out loud because receiving feedback is like receiving a gift. It is also important not to become defensive and start explaining. Just listen, acknowledge, and be thankful.

    After we received this feedback, every team member wrote down what he or she wanted to actively improve upon, starting the sentence with: “I commit to…” We collected everyone’s commitments in a document, printed it, and stuck it on our kitchen wall. Our commitments are public, and our team members give each other permission to help them and to hold them accountable.

  • Fosters Psychological Safety

    Psychological safety is key to productive conflict.

    One of the best frameworks we’ve encountered for fostering psychological safety comes from Patrick Lencioni’s Five Dysfunctions of a Team: vulnerability-based trust as the foundation of a healthy organization.

    We build trust every day by being transparent and open with one another. We have frequent 1on1s; a great venue for advice and meaningful conversation. We make it a point to be vulnerable with one another by admitting our mistakes. All this, so that we can engage in productive conflict.

    Productive conflict can be in the shape of a brainstorm meeting, a (passionate) debate, providing peer-to-peer feedback, challenging assumptions, holding each other accountable. These activities require a great deal of trust, and it really helps to agree upon a number of conflict norms. Conflict norms are ground rules that the team should come up with together. Here are Routific’s conflict norms:

    • Assume positive intent
    • Be mindful of differences
    • Ensure clarity & closure
    • See something, say something
    • Silence = dissent

    The last one deserves expounding: how often have you been in a meeting where you actually didn’t fully agree with the final decision, but you didn’t speak up? Meanwhile the person running the meeting concludes with: “Alright, so the conclusion is that we do X. Any questions? No? Great! Let’s ship it!” And we leave the room unaligned. The common misconception is that silence equals consent. At Routific we will assume that silence equals dissent. So we will go around the room and get explicit, verbal buy in. i.e. one-by-one, everyone in the room says ‘yes’ or ‘no’. This gives individuals a chance to speak up, and allows the team to “mine for conflict” — if there seems to be a slight hesitation, we will dig it out. All cards need to be on the table to make the optimal decision, and create the strongest buy-in.

  • High Quality Code Base

    We pride ourselves on maintaining a quality code base.

    We refactor frequently whenever we encounter technical debt, and like to be on the bleeding edge of technologies and coding practices. It makes our engineers happier and allows us to ship faster!

    Our stack consists of Koa.js, MongoDB, and Angular – because they were the hottest things a few years ago. These days, we’re playing with React, React Native, Flow.js, and Postgres – because Postgres is cool again :)

    That said, we don’t just follow trends; we adopt new technologies only if it can significantly increase the quality of our code base. So while we adopt a micro-service architecture, we don’t overdo it and use our best judgement and apply the 80/20 rule to balance perfect with scrappy. Fun fact: our core algorithm is written in Common Lisp!

    All code gets peer-reviewed before it goes into production. We strive for 99% test coverage on all the code we ship. This makes refactoring easier too!

  • Product-Driven

    The team is united by a common love for great products.

    We believe teams that prioritize product quality (vs. sales strategies) will become market leaders in their space. Our product is driven by user-centric design, guided by our customers, and built by product-minded engineers.

    Highly sceptical of our own ideas, we will discuss alternatives at great length just to make sure that we make the optimal decision. We are also very data-driven: we capture every piece of feedback through all our customer interactions – be it through email and live chat support, during sales or customer success calls, or even on-site visits with customers. Everything gets processed through Productboard (a phenomenal product of itself!).

    Productboard allows us to prioritize and focus on the features that will have the biggest impact. It keeps us honest and focused, while avoiding the traps of tending to the squeakiest wheel and trying to please everyone :)

  • Friends Outside of Work

    At Routific, we get personal. We’ve created a culture where our relationships extend beyond the office walls.

    We hang out on weekends and holidays, and we get to know one another as friends would. In fact, there’s a question we ask the team before we decide to hire someone: “Does he or she pass the Sunday test?”

    In other words, would you come into the office on a Sunday to hack and hang out together? If the answer is ‘no’, then it’s a pass. If the answer is ‘maybe’, that’s still a pass. It’s gotta be one resounding ‘YES!’ These personal connections help us with building trust, being vulnerable, and ultimately achieving what we hope for as a team.

  • Promotes from Within

    We believe our best leaders grow, flourish, and emerge from within the team.

    These individuals have the most relevant experience, and frankly deserve to advance if they want. This philosophy is in-line with our other value of being “Committed to personal growth.”

    We hire team members with tremendous potential for growth, and present them with the opportunity to advance their careers without any speed limits. It doesn’t make sense that you have to wait 4 years to be considered “senior”. If you can achieve the same level of expertise and experience in 2 years, even more reason why you deserve to take on responsibilities of a senior engineer.


  • Open Communication
  • Heavily Team Oriented
  • Committed to Personal Growth
  • Fosters Psychological Safety
  • High Quality Code Base
  • Product-Driven
  • Friends Outside of Work
  • Promotes from Within

Company Properties

  • B2B
  • Technical Founder(s)

Team Members

  • 3 Backend and Algorithm Engineers
  • 6 Full-Stack Engineers
  • 4 Sales and Marketing
  • 1 UX UI Designer

Tech Stack

Our stack consists of Koa.js, MongoDB, and Angular – because they were the hottest things a few years ago. Now we’re playing with React, React Native, Flow.js, and Postgres – because Postgres is cool again :)

Interview Process

We start with a short survey to learn more about the candidate’s personal core values, followed by a casual chat over coffee. Next, we advance to a technical screen, a homework assignment, and finally a half-day hack session and lunch with the team.