FOSSA

Remote, San Francisco
26 - 50 Employees
11 - 25 Engineers
$10M - $25M Funding
Series A

We're building infrastructure to help engineering teams understand and manage their dependencies.

FOSSA photo 1 FOSSA photo 2 FOSSA photo 3 FOSSA photo 4
Active Roles
Why join us?
  • We're building a rocketship company. Since going to market about 2 years ago, we've been crushing our revenue numbers every quarter with over 3 million dollars in ARR. Our customers include Uber, Hashicorp, Docker, Twitter, Zendesk, and more.

  • We're building infrastructure that powers a huge portion of the open source ecosystem. If you've ever used Docker, Webpack, Kubernetes, or ESLint, you've used code that relies on FOSSA. Our partners include the Linux Foundation, the JS Foundation, and the Cloud Native Computing Foundation. Their projects rely on FOSSA.

  • We care about and invest in each of our team members. Our engineering team is small and efficient. Each engineer who joins has the opportunity to take ownership and make defining technical and cultural decisions on our team.

  • We're a product company that's also solving a real and deeply technical problem in software engineering. This is not your average CRUD app. We tackle sophisticated technical challenges at scale, and build products that extract meaningful insights from a complex problem domain.


Engineering at FOSSA
Engineering team and processes

Our engineering team operates on 2-week sprints. We have the usual engineering processes you'd expect from a modern startup: CI/CD, automated testing, code review, push-to-deploy. All of us are generalists, although different people focus on what they're strongest at.

Engineers have a lot of autonomy. Many product decisions are engineering-driven. Day-to-day work generally involves resolving time-sensitive strategic customer requests, and then focusing on product and infrastructure work. Generally, interrupt-ish work (e.g. customer requests) doesn't take more than a couple hours per sprint.

Everyone on our engineering team can interact with customers if they want to. We run a weekly support/on-call rotation, backed by a documented support and operations playbook. Our customer success, support engineer, and product teams help us field requests from customers, and we cooperate closely with strategic enterprise accounts. Engineers who enjoy working with customers often jump in across the company to help close strategic deals and manage deployments for strategic accounts.

Technical Challenges

Our business domain is intrinsically complex. Customers (and engineers) often have a poor understanding of programming systems, build systems, and package managers. We build software that needs to deeply integrate with these tools, understand their behavior, and provide meaningful insights to non-technical audiences.

Modeling this domain is complex. Different programming systems treat dependencies in different (often incompatible) ways. Enterprise customers will often have their own bespoke package management systems on top of existing build tools. Building our data and domain model is a balancing act between being general enough to work with a wide range of use cases, but specific enough to be performant and intuitive.

Integrating with customer environments is complex. Most engineers don't have a deep understanding of their tools, and build complexity is often compounded by years of legacy build tool modifications, bespoke build processes, and third-party tool plugins. Our analysis software needs to be smart enough to automatically integrate with a large variety of environments, but flexible enough to work with customer-specific quirks.

We operate this software at scale with zero downtime. We live within our customers' CI and build pipelines. When we have a bug, their builds break. Performance and reliability are critical for both our analysis software and its supporting infrastructure. This infrastructure must be easily deployed, operated, maintained, and debugged on both cloud and on-premises hardware.

Projects you might work on
  • Our enterprise customers require on-premises deployments. Prioritize, design, and implement internal tooling and automated testing frameworks so that our engineers can easily test and deploy for both cloud and on-premises environments.

  • Now that they have data on what packages they're using, a strategic customer would like dashboards to understand how they use open source over time, and how they address compliance, security, and quality issues over time. Work with product and design to plan, architect, lead, and implement this feature end-to-end.

  • Enterprises often don't use package managers effectively. We need to identify open source dependencies that have been copy-pasted into their large codebases. Work with product and collaborate with strategic customers to plan, architect, lead, and implement this feature end-to-end.

  • To make integration and deployment easier, we allow users to import all of their GitHub repositories in an organization into FOSSA. In order to analyze these repositories, we need to run their builds. Build systems can execute arbitrary code. Architect, plan, and implement a subsystem to provide build system analysis capabilities.

Tech stack
Node.js
React
Kubernetes
AWS
Go
Haskell

Working at FOSSA

Our team is human. We recognize that even the best people make mistakes, and we deliberately foster a culture of psychological safety. We act in good faith, and we trust that our teammates act in good faith. We are open, transparent, and honest about all things. Internally, we talk openly about our financials, the state of our business, and our business and engineering decisions. We collaborate closely on hard engineering tasks. When we make mistakes or miss estimates, we own up to our actions and work together to become better engineers and teammates. We improve our team rather than blaming our team members.

Our team is scrappy. We don't let perfect be the enemy of done. We focus on iterating with customer feedback rather than getting everything right the first time. We prefer prototypes over speculation. We experiment with engineering and product strategies to help us build the best possible product. We experiment with our culture and processes to help us move as quickly and efficiently as we can.

Our team is deliberate. We use data and metrics to focus our engineering efforts on the areas of greatest impact. We make well thought-out trade-offs between delivery time, technical debt, and risk. We think hard about when to be customer-driven and when to follow our roadmap. We optimize for engineering impact on revenue. We build our engineering culture intentionally to help us meet these goals.

Generous Vacation

We have an unlimited PTO policy.

Free Food

We have catering 5 days a week, in addition to ad-hoc team lunches.

Beautiful Office

Our office was previously occupied by an architecture firm, and they really decked the place out.

Work from Home

Our team members WFH whenever they need to. All of our meetings have the option to video call in.

Flexible Hours

We don't have any rules about when to be in the office, and anyone can WFH whenever they need to.

Team Activities

Our office has board games and Super Smash Bros., and we do regular team off-sites. We also have open happy hours every other Friday.

Company Retreats

We do company and engineering retreats on a regular basis. Last quarter, we AirBnB'd a beautiful house in Carmel-by-the-Sea for a weekend engineering retreat.

Transportation

We're located close to the BART and CalTrain, and several of our current team members commute from out of SF.

Health Insurance

We provide full medical and dental coverage.

Pet Friendly

We have a Slack channel with all the company dogs who visit! Come meet Dough, Rollie, Huffie, Moose, and others.


Interested in this company?
Skip straight to final-round interviews by applying through Triplebyte.

Apply