We are a small startup, and each member of our team plays multiple roles.

We are still an early-stage company with less than ten employees and we’re looking for people who are excited by the breadth of work they'll get to do here. As an engineer, you'll not only work across the entire stack, but you’ll also be involved in initiatives and projects that fall outside of the traditional “software engineering” scope.

We don't yet have a dedicated Head of Growth, Head of Customer Support, or many other important roles. At our current stage, all team members are involved in all aspects of the business: we discuss growth strategies, answer support emails, and are all responsible for staying compliant. One of the most important qualifiers for working at Braid is an excitement around tackling different business and technical needs. If you’re interested in seeing a startup at the very earliest stage – because you want to broaden your skills, you enjoy working on different projects, or you’d like to create your own startup at some point, Braid would probably be a good fit. No background in finance or fintech is required.

We love generalists.

If you’re not an expert in one particular language, that is completely fine! We love engineers who are generalists and have experience with (or interest in) multiple languages and platforms. Be endlessly curious!

While there are plenty of opportunities for those interested in depth, there are many more for those looking for breadth. Instacart is a four-sided marketplace that connects consumers, shoppers, grocers, and big brands. As a result, there is so much surface area to explore the relationships between each of our end users. We have unique and interesting problems to solve here at Instacart because we focus on how consumer marketplaces, ecommerce, and enterprise products interact with one another.

We are a collaborative team and our engineers, PMs, and designers work closely with our academic team members.

To support the interests and strengths of everyone on our team, there are various roles you can try out, or grow into. This isn’t a requirement, and thus some team members choose to focus on depth instead. Below is a little more information about what each of these roles do and who may be interested in them:

Product definition

One way that breadth shows up in this role is the overlap with product management work: sometimes, we need to be comfortable taking a high-level goal and figuring out how to get there, without a detailed spec. A few examples of these projects areas are performance optimization, capacity planning, and improving product stability. Other times there are more tangible specifications that come from working with our designers, product managers, and members of the academic team, like building specific new interfaces, product features, or entirely new products.

Tech lead

For folks who have not previously been in a technical leadership position but are interested in developing those skills, we have a tech lead role per engineering pod. We see Tech Lead as a role to play for a period of time, rather than a commitment along a career track.

High-level engineering support

We believe that being in touch with the challenges that our faculty and learners are running into helps to build a healthy sense of empathy and sense of product quality. We have engineering support rotations to periodically help out our frontline support staff.

Recruiting and interviewing

We include folks from across our team in the interviewing process. Whether you are seasoned at running interviews or completely new to it, we want to offer a way for you to be included in the interviewing process. We use pairing and shadowing in interview sessions to onboard and share knowledge.

We need people who are able and excited to get their hands dirty with anything technical.

We don't believe in technical specialists at this size. Small startups change very fast and it is important that we are able to put our efforts towards the opportunities that are most critical to our success. That being said, we are eager to leverage a person’s passion or interest in a specific area. It is normal for engineers at Wove to fall in (and out) of niches. The real expectation is that everyone has a broad range of skills and *can* work on anything if needed.

“Michael McLay publicly asked, in 1994, what would happen to the Python language if Guido van Rossum were hit by a bus.”

Developers are not silos, they can have specialties but the “Bus Factor” (the ability of a company to continue performing despite employees getting hypothetically hit by a bus!), in Loylap needs to be quite high. The higher the Bus Factor, the higher the probability the company can continue to function.

Wearing many hats is important to the overall function of the company, but it also benefits individuals. If a you wear a few hats and a role becomes redundant due to a tech stack change or loss of big client, you can simply wear another hat. If we lose a person, there’s a good chance the institutional knowledge they had won't also be lost, because another member in the company has similar knowledge. While roles can become redundant, people never do.

There’s no one path to discover where your strongest passion lies.

At Wealthfront, we encourage engineers to explore and expand their interests by taking on various roles and projects they’re passionate about. While we’re a well-established company with a well-established product, there are a myriad of experiences and opportunities you won’t find in a lot of places. As software engineer Andrew Easton puts it, “The ability to learn and work on many different aspects of web code, deployment, infrastructure, and more is fantastic. But beyond even writing code, there are technical paths, area paths, management paths... and all of it is freely available to explore. It’s a great opportunity to really discover where your strongest long-term passion lies.”

Backend, frontend, public npm modules, heroku – you’ll do it all!

At this point, given our company’s size, everyone has their hands on everything. It’s not required that new hires come to ReadMe with a wide breadth of experience, but a willingness to jump in and learn different parts of our stack is important.

We also host an API conference called API Mixtape. Everyone in the company travels to San Francisco to attend and is encouraged to engage with our community. Engineers also have opportunities to speak! In the past, Marc has presented ReadMe’s new features and Dom gave a talk on best practices in API documentation. We have fun with the event and built a light display for the stage that changes color based on the current speaker’s company. The light display has been repurposed for our office wall and is editable via an API. (Ask for the web address if you want to change the lights in our office!)

We are looking for people who aren’t just comfortable wearing many hats, they prefer it.

If you haven’t worked at an early stage startup before, we hope you’ll take the time to fully understand what comes with it. There’s less structure. We don’t have a multi-month roadmap. We want you to help us drive, fill gaps, and make important decisions. You should want to create and build out Precious on your own, not because someone else is expecting you to. In addition to the many responsibilities you’ll juggle, you should also be aware of how influential our next hires will be. Whoever we next bring onto our team will define the future of our company’s culture and product. Hopefully, they’ll also care deeply about how they shape both.

We won’t limit you to one narrow set of responsibilities or role.

We try to encourage growth in our team members’ strengths, while appropriately challenging any weaknesses. We find that drawing hard lines between technical responsibilities can often hinder our ability to move quickly, so we don’t. Do you work on the front end but know how to handle that issue with the API? Go for it! Just send a pull request for the backend team to review. Are you a designer who has experience in web development? Great, our designer is also a front end developer! We fully support individuals who have broad skills. In fact, we think that’s wonderful. For those wanting to round out their skill set, we think our team is a great place to do it. Our current team members come from many different backgrounds and have varying levels of experience with many aspects of our technology stack –– everyone has something to learn and we encourage that everyone does.

We are growing quickly, so we encourage people to fill the gaps and wear as many hats as they want.

Want to learn more about operations and the business side of Flexport? Phenomenal, do it. By learning about their pain points you can have the freedom to go build products to solve them.

One great example of taking initiative and trying something new can be attributed to Kevin, who built our permission policy system. He single-handedly ran our infrastructure for over a year and flew to our Shenzhen office to improve site performance behind the Great Firewall.

Desmond Brand joined Flexport’s original engineering team as engineer #8. Six months later, as Flexport continued to grow, he became an Engineering Manager in charge of supporting half the team. He then took on the role of Engineering Director, supporting both the client-facing applications group and the frontend infrastructure team. And after three years in management, Desmond decided to return to an individual contributor role on the frontend infrastructure team, "leading from the front" once again.

We encourage you to try various roles and functions to find what fits you best!

At Apto, we lend a hand to work on any and all projects as needed.

Apto is a platform with multiple components, which means engineers have the opportunity to be involved with various functions. These include:

1. Core – the fundamental piece of transaction processing and card issuing.
2. Experience – SDKs, this is layered on top of Core, and is how we communicate with our end users (APIs, messaging, notifications, and branding).
3. Program Setup – compliance, bank program management, card manufacturers, interfacing with VISA and MasterCard.

Similarly, as we grow the company, roles will naturally evolve to meet company needs. For example, Ivan started as an iOS lead and was the only person in Barcelona. As we scaled in Barcelona and grew the team there, Ivan became both a coordinator and manager. He now spends more time coordinating between offices. He still occasionally pushes PRs, but the majority of his focus is on strategy and supporting the other engineers at Apto.

We’re a small team and none of us come from tech.

Each of our current team members have really diverse backgrounds, so we get to learn a lot from one another. For example, Mark is well versed in music and teaching which lends itself well to his articulate expression of coding problems. And Robert ran a large online community for architecture students which has translated well to customer success and helping rally support for our company.

Perhaps more uniquely, we don’t silo anyone because of their labeled skillset. Action is the great equalizer. Have an awesome idea? Mock it up and show it off, then let’s see how we can either improve it or get it into production. At Monograph an engineer can provide illustration work and a salesperson is able to give design feedback.

While we do have specialists across our entire engineering organization, we want a large part of our team to have breadth and be able to jump in on a wide variety of problems.

We want front end engineers that like to tweak APIs and update backing data models. We want back end engineers who make sure that the client SDKs are easy to use and running efficiently. We want engineers who solve problems at all levels, from the initial product conception to the maintenance and monitoring in production. We think this is important for a few reasons:

1. The less isolated engineers are in their particular disciplines, the better they will be at solving problems for our members and for other engineers.
2. We will never have enough people to do all the work we have. Being multi-disciplined (or being willing to try) means that you’ll be working on all sorts of problems.
3. The skills we need today may not be the same as the skills we need tomorrow. As we evolve, we want our engineers to evolve with us.

Curiosity and generosity are two of our core values.

We work in a cross-collaborative environment and believe that the less isolated we are in our disciplines, the more effective we can be at problem solving. We’re still refining our products and discovering the use cases and pain points our APIs can address across various industries—and everyone at Enigma has the opportunity to truly own a piece of the company’s roadmap. That’s why you’ll often see product people knee-deep in data or engineers weighing in on product vision—everyone is expected (and at the very least should be willing to try) to jump in and lend a hand.

There are endless opportunities at Enigma for people who are excited by new challenges and inspired by the chance to contribute and make an impact. Professional development opportunities—such as attending conferences or taking relevant classes—are open to all, and we even have access to a public speaking coach for anyone interested in giving talks or working on presentation skills. There are also frequent internal presentations, tutorials, and information sessions from team members eager to share their knowledge and skills with the company.

Position works on billable client work four days a week.

On Fridays, we do everything else -- and this can include invoicing, recruiting, marketing, sales, accounting, legal paperwork, planning, and much more. When important projects come up (for example, “becoming a cooperative”), we create working groups of one or two people to make sure everything gets done.

We greatly value all this non-development work. However, we also believe that we do better work when we are able to focus, and we hope to reduce the number of hats each of us wears over time.

If Position’s values sound exciting and interesting, we encourage you to check out our open positions and apply! If you’d like to know more about Position or if you have questions, you can also email us at [email protected].

Engineers at Nova are full-stack and have their hands on more than just code.

Engineers rotate to different pods and projects, most of which are cross-functional. Initially, our job postings were divided into frontend and backend roles, but given that Nova engineers often work across the stack and have varied interests, we’ve since changed our open roles to “Software Engineer.” When you join Nova, you won’t be pigeonholed and have the option to fluidly move across our stack (and even do non-engineering tasks if you want).

Because we're a small company trying to accomplish big things, we take every opportunity to "tie each other's shoes." Team members often wear multiple hats, and sometimes this means doing maintenance tasks like (un)loading the dishwasher or building desks for new hires.

For engineers interested in getting involved in other kinds of work, we also have internal initiatives and task forces that welcome new ideas and members. You can join or participate in our inclusion committee, help to plan our next offsite, sit in on BD meetings, or contribute to sourcing and recruiting efforts.

If you’re interested in learning more about our team or talking to one of us, we’d love to hear from you! You can apply to jobs here or message any one of us on Linkedin.