Engineering at WorkOS

WorkOS provides a single, elegant interface that abstracts dozens of enterprise integrations. This means developers can get up and running faster and can focus on building unique features for their users instead of debugging legacy protocols and fragmented IT systems.

Job Openings at WorkOS

Top Engineering Values

Each team is asked to select, explain, and rank their top 8 values in order of importance.
  • Engineering-Driven

    We are all responsible for working with a hammer-in-hand.

    As engineers at WorkOS, we lead product development, so it is our responsibility to talk to users and think critically about the product while building it. We are also involved in all other aspects of product development, from design, to marketing and telling the story of each feature.

    We ship high-quality, polished, product features often. When something looks off, we fix it. We do the small things that make the product, the website, the response to our user, the email, the tweet, or our company better. The work can be toilsome at times, but there is deep satisfaction in the final result.

    At the end of the day, we are all doers and practitioners. There is no room for someone to just stand around and supervise. Pointing out problems without doing anything to fix them is the anti-principle. We are always willing to pick up a hammer, or broom, or email, or pull request.

  • High Quality Code Base

    We keep our quality bar high and sweat the small stuff.

    As a still-small-and-nimble organization, speed is our greatest advantage over the incumbents in our industry. But, if we don't execute extremely well and deliver extremely high-quality products consistently, we won’t have any staying power. Because of that, we're obsessed with breaking large problems into small, meaningful chunks. Our quality bar is exceptionally high and we are willing to sweat the minor details.

    We are conscious of our technical debt and regularly invest time and energy into the foundations of our codebase. We design extensible, solid, foundations. We make strong use of TypeScript’s type system to prevent bugs.

    Our platform is supported by different layers of automated testing via continuous integration, such as unit testing, functional testing, integration testing, smoke testing, and thorough linting and formatting. We rely on this automated tooling to keep codebases consistent, so we can focus on the foundation and mechanics of each feature during code reviews.

  • Impressive Team Members

    At WorkOS, you’ll always have someone to learn from. Our team members are former founders, executives, and open source contributors.

    While having the most amazing resume is not what impresses us at WorkOS, it's worth mentioning that several of our team members are former founders and executives. Our current team members have started companies in the past, and many go on to start companies together after their time at WorkOS.

    We're proud to work alongside folks who came from Dropbox, OpenTable, Microsoft, DocuSign, LaunchDarkly, Airtable, Kickstarter, and Acorns. Many of them also made significant contributions to open source projects, which is something that we care about a lot.

    You’ll feel both challenged and supported by the talented programmers that are working here. When something falls below the mark, we have the courage to speak up and say, “It’s not quite there yet.” At WorkOS, good enough is not good enough.

  • Open Communication

    We believe in transparency and optimize for asynchronous communication.

    As a distributed team, we are async-first. While we’re looking for engineers who live in time zones compatible with the US, we optimize for asynchronous communication via text. We still have face-to-face time, but it's much more intentional.

    We have transparent discussions around product and engineering decisions out in the open. These range from technical RFCs to proposals for new features in the product. Since every team member can access these long-form discussions, this means that any team member can go back in time and read why certain decisions were made and what trade-offs were considered at that time. This enables every engineer to contribute.

    To us, kindness means creating a culture where everyone has a voice and speaks up. Each team member is encouraged to express what they think would be best for the product, the team, and the company. We speak to each other directly, we disagree amicably, and we remain kind and respectful in all conversations.

  • Product-Driven

    Good enough is not good enough.

    We focus on delighting users every single day and earning a reputation for excellence. Regardless of whether it’s a big new product, or the smallest interaction in our documentation, the WorkOS quality bar is exceptionally high. We strive to impress and are willing to sweat the small details.

    This goes beyond just visual design and applies to everything we do, from providing insanely great user support, to the high-integrity experience candidates have when interviewing with us. A so-so ship or a buggy release may seem small on the day-scale, but they can have ripple effects for years. We are making a first impression with new users every single day, and our goal is to stand above the noise.

  • Wears Many Hats

    We actively avoid silos.

    Engineers are involved in product development in all aspects of the life cycle, from conception, to helping with design, to launching with our marketing team. We believe the most important factor is your capacity and enthusiasm in growing and learning new skills, not your working background with a specific language or framework. We appreciate wide ranging experiences and encourage people to jump in on a variety of problems.

    Even though we do have specialists around, we encourage engineers to push the boundaries of the traditional divide between front-end and back-end. We support engineers in learning new technologies, developing their versatility, and exploring skills outside of their prior experience.

    Ultimately we are a multi-disciplinary team that is willing to solve problems with high-quality software. If you’re excited about gaining exposure to all parts of the business and codebase, we’d love to hear from you!

  • Continuous Delivery

    Engineering candidates will often ask us, “When do you deploy?” and our answer is, “Whenever we feel like it.”

    At WorkOS, we’re building a modern API platform that empowers any developer to quickly build and ship enterprise features. Everyone from early-stage startups to Fortune 500 companies rely on our platform to build enterprise-ready apps.

    We are the antithesis of a slow-moving, big, technology company. Our customers are engineers as well, which means they can speak with a level of technical precision that enables us to iterate faster. We move quickly. We deploy many times a day. We keep a tight feedback loop with our customers.

  • Work/Life Balance

    Early-stage startups are often associated with crazy working hours – that is not the case for us.

    We believe engineers do their best work with balance and consistency. We offer flexibility in when you work and make sure that everyone's workload is manageable so that you're not thinking about work once you've signed off for the day. Our on-call rotations are pretty quiet because we go the extra mile to invest in the quality of our platform.

    “I thought the startup life would demand hours of my time and folks would be pinging me on weekends and nights. It’s actually quite the opposite,” says David Liu, one of our software engineers.

    Having a healthy mind is just as important as having a healthy body. That's why we give engineers a monthly fitness allowance and a wellness allowance.


  • Engineering-Driven
  • High Quality Code Base
  • Impressive Team Members
  • Open Communication
  • Product-Driven
  • Wears Many Hats
  • Continuous Delivery
  • Work/Life Balance

Company Properties

  • B2B
  • Technical Founder(s)

Team Members

  • 20 Full-Stack Engineers
  • 4 Product Designers

Vacation Policy

20 vacation days in addition to 10 bank holidays, unlimited sick PTO

Tech Stack

Full-stack: TypeScript




Interview Process

We first have a discovery call to provide a general company overview and learn about the candidate’s background. After that, we give candidates a take-home exercise that they can finish on their own time. Finally, we have a pair programming session with candidates so both parties can see what the experience of working together would be like.