Large banking and card institutions like Chase and Wells Fargo are slow-moving, which gives us an advantage as a small team to iterate and ship new products much faster. For example, while debit cards typically take 12 months to go live, we can do it in 3.5 months. Our agility as a small startup allows us to push code to production several times a day and make decisions without bureaucracy and red tape.
During this time, we’ve grown from being a single corporate credit card product for startups to providing fully fledged card and cash management products with robust spend management features to customers across multiple industries. Many of our core financial products are complex and require time to get right, but that doesn’t stop us from moving fast.
Even as a (much) larger organization, we continue to innovate and innovate quickly. One of the best examples is Brexploration, a program that allows existing team members to devote an entire quarter to building a loved product as “founders.” Teams apply to the program and then spend three months working like early entrepreneurs and skipping existing company processes. Successful projects are then transitioned back to operating like a scaling product. Many of our most customer-loved products and features came from Brexploration, like Expense Management and Bill Pay.
As another example, engineering focuses on enabling Product Teams to execute as quickly as possible. Our Infrastructure Empowerment team, for instance, builds our infrastructure on top of cutting-edge technologies, tools, and best practices (Kubernetes, GitOps, Istio, etc.). They have adopted a microservices-oriented architecture, and are continuously releasing new software which enables fast iteration of our product.
25 Open Positions
We are all about getting shit done and making an impact, but that doesn’t mean we sacrifice long-term investments and quality – we of all people know, everything is about balance, but we err on the side of working quickly and making sure we deliver on the promise we made to our teammates and community. What is that promise? Our founder and CEO, Alyssa, put it best:
“I want people to remember they’re part of nature. I want to fundamentally shift our relationship with the natural world and start to respect the animals and the plants and the water and the soil, and to see ourselves as part of that whole. I want people to stop being so afraid of climate change. I want people to stop being depressed and sad and overwhelmed and anxious. I want people to get curious and excited about what they can do and start to see themselves as the solution and not the problem.”
Developer-friendly APIs to automate trusted decisions about every business
New York, NY or Remote
Even as we continue to grow, we can’t afford to move slowly or make “safe” calls. We’re focused on building the APIs to power the next generation of intelligent applications. It’s an ambitious goal, so regular adjustments are expected as our products continue to mature. The roadmap isn’t always a straight path.
Being able to adjust and switch directions quickly is more important than hitting every KPI so we intentionally set aggressive timelines in order to make mistakes early and often, ensuring we’re constantly learning from our users, optimizing over time, and building for the long term. Our squad model enables this flexibility, allowing cross-functional teams to work independently to get things done. Engineers are even encouraged to move between squads, ensuring constant expansion of product knowledge and creating collective understanding around what’s being built across the organization.
We push to production every day. We shift priorities every day or week based on customer needs. We’re a fast-growing company where our growth is ahead of our team size. This may seem chaotic, but it’s by design and helps us avoid the sunk cost fallacy. We’re not afraid to change priorities after gaining new insights or gathering new information. This, overall, helps us move faster as a company.
Our product roadmap and priorities are determined by customer needs every month and prioritized by our founders who own the product responsibilities at NexHealth. We have a north star we follow. We have a 6-month, 1-year, 5-year, 10-years, and 20-year long timeline of what we want to achieve. However, we don’t plan roadmaps beyond 1 month. This allows us to adapt and execute quickly as new information comes in while never losing sight of our north star: we are always working in the same direction of our mission and overall vision for NexHealth.
18 Open Positions
You join a startup because you want to make an impact without the red tape. We are biased toward action and know that the fastest way to learn is by doing (rather than just sitting around and talking about it). And we love doing.
We generally err on the side of speed over perfection, and love to ship early, then iterate. We deploy multiple times a day, and often rollout changes internally to our team first, and then after QAing, externally soon after. We have a pager system, but not a formal rotation. Currently, everyone jumps in when needed. We lean on straightforward engineering over intricate, or idealistic solutions.
We’re well aware of how much change Cameo will undergo in the coming months, so we’re being careful to protect our culture of shipping early and often while also introducing necessary processes to keep things organized and efficient. We know we're biased, but we think it's objectively an exciting time to join Cameo. If you want to learn more about us, contact us!
We will always prioritize time-to-market and always challenge ourselves to execute faster. While it’s common to hear that you will release code on your first day, we really mean it. Engineers on our team release to production multiple times per day and we tend to work on multiple projects within a single sprint. Sure, there's work that may take a whole sprint to complete, but we’re typically multi-tasking and keeping multiple plates spinning. Not only do we have many workstreams, but we’re also keen on not siloing anyone on a single project. To help stay focused, we regularly use single-week sprints as well.
At present, everyone on our team is a full-stack developer. While most people have front- or back-end preferences and different strengths, we encourage everyone to work across the entire stack.
We’re a small team, so we can quickly change focus and get behind a new problem on short notice and deliver in quick order. Our process supports a maker’s schedule, which we honor every day. To help facilitate speed, we also use CI/CD and have designed our technical infrastructure to bias toward frequent and fast deployments.
1 Open Positions
Data is in demand right now. In this high-growth market, we like to make decisions fast and learn along the way. As a result, we've created a fast-moving team that thinks about how to reduce time on feedback loops and delivery.
To that end, our deployment pipeline moves quickly. We practice continuous deployment to our pre-production environment, work according to agile development principles, and promote the latest stable code to production at least once a day. To decouple deploys from releases, we make heavy use of feature flags.
That said, a fast-paced environment doesn’t require burnout. On the contrary, we can only ship as fast as we need to with a well-rested, energetic, and happy team. Mode’s leadership team sees value in people maintaining their lives and interests beyond the office.
19 Open Positions
Leading Software-Powered Freight Forwarder
San Francisco, Bellevue, Amsterdam, and Shenzhen
In the past year, Flexport opened offices in Seattle and Philadelphia, bringing us to 12 locations and counting! The volume we’re shipping has increased so rapidly that we’ve purchased warehouses in Hong Kong, Los Angeles, and Shenzhen, and we’ve even leased our own Boeing 747!
We achieved this growth thanks to 150 engineers across four cities and three countries, something we attribute to a carefully designed product cycle that syncs strategically with the business. To keep up with the growing demand, engineers move fast.
When you join Flexport, you will ship code on your first day. You’ll build our product and design flexible, high-quality solutions. To help you understand the broad scope of our mission, you’ll participate in a week-long crash course on the fundamentals of global trade. Your onboarding class will be flying in from offices around the world and consist of people from operations, sales, marketing, product, design, and more. It’s a great opportunity to tap into the cross-functional knowledge of your starting cohort!
33 Open Positions
Generally speaking – across all of the different pillars and teams at Amplitude – we try not to tie ourselves to arbitrary deadlines. Instead, we build, continuously release, gather feedback early and often, pivot when needed, and retire work when it’s stable. When we’re getting close to a deadline, we’re not afraid to push it back. While we are in favor of building quickly, we don’t want it to be stupidly quick!
In 2019, our team started tracking a company-wide metric: number of features shipped. We got pushback from various teams, created a working group, and two weeks later pushed out a new iteration of that metric: number of bets taken. Not only is this an accurate demonstration of how quickly we iterate, but it also captures our mentality and how we orient ourselves at Amplitude. It encourages us to create learning opportunities as quickly and as often as possible, and removes any expectation to ship things perfectly the first time around.
30 Open Positions
Career network for college students and recent grads
San Francisco, Denver, or Remote (US)
This is a core value at Handshake since we’re a rapidly growing startup and constantly evolving. We’ve doubled the size of our company in the past year and we continue to grow quickly. That’s why we place a huge emphasis on moving quickly without rushing. At the engineering level, this translates to building features in a timely manner. When there’s a high priority incident that needs to be dealt with, the team has to be able to act swiftly to make sure it’s resolved as soon as possible.
Our CI/CD system enables us to iterate and deploy quickly, but we always make sure that all features and bugs merged into production have accompanied tests to ensure high quality. What’s more, we stay up to date with technologies and openly discuss the tradeoffs between speed and perfection with each iteration. For example, managers adhere to the “60/20/20 rule” – our time should be split by 60% product development, 20% technical innovation, and 20% technical maintenance. So while we want to move quickly to develop features to enable our important mission, we also set aside time to address technical debt and innovate on our technologies.
As a company, we have grown very quickly. We just raised a $40M Series C and we’re considered the fastest growing education technology company in the Bay Area. Just over the past year, about 50% of our engineering team will only have been at the company for less than a year. Because of this fast-paced growth, engineering leadership is constantly iterating on and improving processes and methodologies to keep every team organized and high-functioning. For example, the manager of the Employer Engineering team received several points of feedback from the team’s bi-weekly retro meeting that the growing number of people was making our Scrum meetings run very slowly. Within a week, the manager worked with the PM, designers, and technical leads to reorganize the team into two separate Scrum teams, resulting in more highly efficient meetings and clearer delineation of responsibilities among engineers.
Financial and software products for a new generation of business owners
San Francisco, CA or Remote (US)
We practice this thoughtful agility at Hatch on a daily basis. We move extremely quickly to ship every day, but make sure to respect our QA, code review, and blue/green deployment process to ensure our products maintain a very high standard of resiliency. We also run a weekly sprint process to map out features and bug fixes that we’re going to work on, which helps us stay aligned internally. We feel especially motivated to help our customers through what is undoubtedly a difficult time for all early businesses, and we feel that urgency every day. Our shared commitment to make sure our small business owners are able to access credit to run their business during this global pandemic has instilled a sense of purpose in everything we do, and we are working as quickly as we can!
We try to push the boundaries of what customers expect a background check to be while remaining compliant and accurate. For example, we offer a white label applicant portal, allow other products to use our API via OAuth, and are using machine learning to predict how long a background check will take. We work closely with customers and applicants to identify real problems they face in their workflows, opportunities to increase their data quality, and ways to help them stay compliant. By taking smart risks, we are leveraging technology in ways that the industry has never seen before.
10 Open Positions
On the engineering side, we get weekly requests from clients which need to be addressed quickly, with thoughtful strategy and implementation. We use Trello extensively and go out of our way to get the engineers’ feedback before starting a project. It doesn't feel frantic but busy with a sense of urgency. We get feature requests and bug fixes. Mostly feature requests. We usually say yes to feature requests with an estimated timeline. The big differentiator with our company is that we are users of our own product on the agency side, so we build ahead of clients. Almost 95% of the feature requests coming in are projects already in progress as we have internally asked for them, so we speak with credibility and sound cadence.
1 Open Positions
Our team members have had previous experiences working at or founding startups, so we’re well aware that “fast-paced environment” has become a euphemism for “it’s crazy." Yes, the excitement and energy that make startup culture so special is certainly alive and well at Alto, but what we really mean by “fast-paced” is that you will be expected to contribute a lot and very quickly. We’ve built different products in a very short time with very few people, and we’re constantly pushing to ship new things. Alto thinks on the order of weeks, not months. As we grow our team, we’re looking for people who are energized by a sense of scrappiness and urgency.
Alto started in a storage closet in 2015. Today, we serve tens of thousands of patients across multiple cities and multiple specialties, all made possible by this incredible team of over 400 and the technology platform we’ve built. We’ve come a long way since the beginning, but we also believe we are only just getting started.
Continuous integration and delivery platform
Distributed across the US, Canada, Ireland, UK, Germany, Japan
As a result, we’ve created fast-moving teams with a high degree of information flow that innovate around how to reduce time on feedback loops and delivery. Our development process focuses on a very short cycle where small changes are iterated on incrementally and delivered quickly. There’s very low lead time to make changes and we follow a dual-track agile development process, where experimentation and discovery are equally important.
We build, continuously release, gather feedback early and often, and aren’t afraid to course correct when needed. While there’s a high rate of change (from a DevOps culture sense), a fast-paced environment doesn’t require burnout. As Lena Reinhard, our VP of Product Engineering, puts it: we avoid burnout by keeping the bigger picture in mind and focusing on clear communication, expectations, and trust.
In 2020, we had 100% YoY credit growth and raised $215.5M in venture capital, and we have no intention of slowing down. Not only will we grow in number (we doubled our product and engineering organization in 2020 compared to 2019), but we’ll also accelerate our productivity. We shipped 100+ features and bug fixes last year (compared to 40 the year before) and we hope you’ll help us set a new record this year.
19 Open Positions
We’re in multiple states and continue to scale quickly. But our growth can’t come at the expense of quality. Our clients and their families come to us in a time of need, and we need to provide them with the highest possible quality of care and communication. Despite our scale, we’ll always retain the software development tenets that we started with: iterative, fast-paced, and data-driven.
We were founded in 2014 in San Francisco. Below we proudly celebrate the opening of our new Austin office with an official ribbon cutting ceremony endorsed by Austin’s Chamber of Commerce!
26 Open Positions
For us, fast-paced describes our deployment processes and how we like to “always be shipping” versus how quickly we change strategies. This is another aspect of ActZero that makes us different from your average startup: while we adapt to new information, our strategy is generally unwavering. We already have product-market fit and work quickly out of excitement. Everyone operates with a strong sense of ownership, which translates into urgency. The feeling is not panicked, but rather a calm assurance and eagerness to deliver immense value to our customers and change how security services are managed.
We employ continuous delivery such that every code change can make it to production in a matter of minutes. We measure and optimize the number of builds per day and the amount of time to deploy. We care deeply about eliminating the amount of time it takes for a developer to be productive. Our desire for automation and ML doesn’t end with the Security Operations Center, we also use these techniques to reduce wasted effort in building and operating our software.
We judge our pace through measurement. Urgency is reinforced through our Kanban development process. Each task should take <1 day to complete and we are vigilant about this fact. If a task takes less than a day to complete, every engineer should be able to ship one thing per day. Everyone therefore gets the opportunity to demonstrate concrete progress, day after day.
1 Open Positions
We want to build a best-in-class P2P payments experience while making sure to keep our users’ personal and financial data secure. Because consumer payments is a heavily regulated industry, it tends to move slowly. That is changing thanks to a handful of new financial infrastructure companies (Plaid, Alloy and VGS, for example) that streamline data security and compliance in new and exciting ways. We can leverage these new infrastructure offerings to our advantage, to help us move faster on the product side while still maintaining incredibly high standards for data security and compliance.
1 Open Positions
As an early stage startup, we need to be able to adapt and switch courses quickly. Our philosophy is best described by this Eisenhower quote: “Plans are worthless, but planning is everything.” We value the process of planning, but don’t consider any of our plans to be carved in stone. We don't want chaos and disorder, but we also don't want to be rigid and inflexible. Striking this balance is something we actively and consciously work towards every day.
One of the biggest frustrations people have about working at early stage startups is how often things change. People need consistency and certainty, and change creates anxiety and fear, which, in turn, are shown to decrease productivity and creativity. So how do we reconcile these two seemingly contradictory facts?
The answer is that not all change is created equal. It’d be crazy if you needed four levels of approval to change what snacks you have in your office kitchen. Conversely, it’s going to be really jarring if you are suddenly told to drop all your work because a product line has been axed, without any explanation or foreshadowing.
The trick, is to allow for some types of changes to be fast and fluid, while requiring others to be slower and more deliberate. Some changes should require nothing more than a quick chat, while others need a stakeholder meeting, and others need an all-hands company meeting. At Range, we make sure team members are informed and involved in decision making, which means we can tune plans dynamically and quickly without people feeling like they are being jerked back and forth. Dan, our CEO, goes into detail about how we approach change at Range in his post, Shades of Change.
1 Open Positions
Before building anything, we figure out – as a team – if it’s the highest priority work we can do. If it is, we come up with the “minimum remarkable product,” a concentrated, testable version of the idea that can be built in a week. Unlike most other iOS companies, we ship a major new app version every week. (In fact we shipped 39 big releases in 2018). If what we’ve built works, we iterate on it. Each MRP is a building block towards the next evolution of our product.
Our grid interface is a good example of this. When we first launched, sites didn’t scroll. They were fixed 3x5 grids with text, photos, and links. Now you can make a site with as many pages as you’d like, 13 different blocks, and infinite grid sizes.
We have a really big vision: to democratize the web. While it’s important to keep that in mind, we know that the only way to get there is day by day, week by week. We don’t have 6-month roadmaps. Instead, we learn quickly and use that knowledge to figure out the best way to accomplish our goals.
This kind of work environment isn’t for everyone, but for people who want to move fast, learn quickly, and increment towards perfection, it’s addictive.
We test things with our users (teachers and students) and we would always prefer pushing something in half the time over perfection since we know that most things we decide to build will be wrong. We can change strategy when needed, and there are no barriers to good ideas and confident ambitions.
1 Open Positions
We build our product with a sense of urgency; we want to provide value to our members as quickly as possible. We are not able to confirm or reject our hypotheses and improve upon them until they are live and we want to do so as quickly as possible. Sometimes this means reducing the scope of a solution, but it never means compromising our standards for engineering or product excellence. We may start to build a feature only to realize that the experience is not good enough. In this case we would likely cut a secondary feature and ensure that the core experience is intuitive, snappy, and delightful.
In order to help us release early and often, we’ve built a strong foundation of comprehensive test coverage, regularly updated dependencies, and a constant effort toward minimizing technical debt. We release code to production many times a day and engineers are empowered to deliver their code when they see fit. Engineers are expected to do what it takes (test coverage, code reviews, manual testing, etc.) to have high confidence in the code they are releasing and are expected to own (and learn from!) any regressions, which are an inevitable part of software development.
We strive to be adaptable. We adjust quickly to new problems and make changes to the roadmap when we find projects that we think will have a big impact in meeting our goals. We’ve also switched to a continuous deployment workflow which enables us to push code every day. One thing’s for sure: we’re focused on removing barriers and inefficiencies to increase everyone’s velocity and productivity. The competitive spirit is alive and well at SportsRecruits.
1 Open Positions
Want to List Your Company?
Submit a team profile!
Select 8 Values
Contact me (Lynne 👋)
Qualify Your Values
Reach Thousands of Devs
Find Value-Aligned Candidates
Have Meaningful Initial Conversations
Don't Fill Roles, Hire Teammates
You can post as many job openings as you want.