Engineering at CarLabs

I’m Sam, the CTO of CarLabs. As a first post, I’d like to give a high level view of what the engineering team does at CarLabs, and what it’s like to be part of.

For context, we work on Conversational User Interfaces. We believe that natural language is the correct interface for

So, we “build conversational experiences in the automotive vertical.” What does this mean?

[marketing/sales joke here]

It means we are taking advances in Natural Language Processing and building them into a platform with more traditional elements of content management. We use this platform to make products for car manufacturers, dealers, and portals — products like marketing bots, support automation, and more.

As an engineer, what this means is: we use cool tech to build interesting products. We have, in production: Docker, Elixir, Node.js, React, Python, and PHP7. We’re a small team powering a lot of functionality, and that means we have to leverage the right tools. To do this, we have to learn. A lot. We pair program frequently. We have Lunch and Learns. We go to conferences (with company support). Most importantly, we share information frequently (on Slack, or on the whiteboard).

Ecto lessons with @barakyo

If this sounds interesting to you, get in touch!