Signal Sciences empowers security and engineering teams by providing visible and effective web application security protecting against real-world attacks. With our unique hybrid on-premise and cloud architecture, we process, protect and report on billions of requests per day for some of the most sophisticated companies in the world ranging from Adobe to Vimeo, Taser to Under Armour. Our goal is making a more secure Web, with tools that people love to use, written by people who love to make them. Join us.
- This job is part of the technology group, acting as a bridge between product design and engineering
- This is an individual contributor role (not people management)
- Located in Los Angeles
- Suitable for mid- and senior-level engineers
UX Engineers at Signal Sciences have an impact in two areas: they contribute as UI developers embedded on feature teams that build out our admin dashboard; and they also build and support Cosmo, our in-house design system, helping feature developers and product designers make high-quality products that our customers love.
To do this, we treat our react components as products using a full development lifecycle: requirements gathering, code standards, documentation, testing and deployment to production, and then monitoring. We’re working toward open sourcing many of these components and sharing Cosmo with the public. In addition to technical problems, we encounter many lifecycle issues as well:
- Since React is changing rapidly, what defines a good React component?
- How can you monitor your components live in production?
- How do you test functional components? Visual components?
- What does “maintainable” and “legible” CSS look like in a component library?
- How do we communicate component changes internally? Externally?
- What is the right balance between customization and control?
We are looking for mid- and senior-level engineers to help build out our React component library to support and to help build a product that helps security teams gain insight and take action on threats to the applications they protect.
While some experience in React is desirable, it need not be from your day job. Weekend projects count! Ideally, you can point to some existing components on GitHub, but we understand if that is not possible. Otherwise:
- Experience building and maintaining component libraries/design systems
- Interest in automation and tooling to support both developer and designer workflows
- Team-based experience and development will be useful since you’ll be interacting heavily with designers, the API/Data team and the features teams.
- Understanding of good design practices and how those translate to building UIs
- Ability to consider design compromises and communicate tradeoffs to a team
- It’s always good if you have a bit of back-end experience as well. We use Go (“golang”), but happily welcome those with Node.js, Python or Ruby backgrounds as well.
- Some basics of Linux/Bash will be useful to aid in our component build system.