Starting out, you’ll spend 80% of your week (Monday through Thursday) designing and building a product or platform for one of our clients. The other 20% of your week (Friday) will be spent contributing to our open source projects, internal products, learning, teaching, and participating in internal operations of all flavors.
Project teams are small and usually made up of one or two pairs of engineers, a designer / front-end developer, a product advisor, and the client who serves as the product owner. Most things we build are greenfield with the goal of creating a new product or service and taking it to market. We are often further engaged by our clients to continue iterating on the product once it is live. The high cost of context switching is real, so we do our best to keep teams together throughout the duration of their projects (typically 2-4 months), but have found it valuable to rotate pairing partners when it makes reasonable sense.
We are always exploring new tools, languages, and technologies - we feel strongly that it’s a good idea to use the best tool for the job and not see everything as a nail. We also try our best to standardize our technology and tooling across project teams so it’s easier to rotate and practice collective code ownership.
We believe a great team shouldn’t be restricted by geography, which is why we’re a remote-first company. Some of us work out of our offices in Chattanooga, TN. Others work remotely across the country. The choice is yours.