Drata is on a mission to serve as the trust layer between great companies. Drata is a trust management platform that uses AI-driven automation to modernize governance, risk, and compliance, helping thousands of businesses develop a more secure, proactive, and risk-aware organization to continuously maintain trust with customers. We all recognize the importance of earning and keeping the trust of our customers when it comes to protecting their data. We know how burdensome achieving and maintaining a strong GRC posture can be with the rise in compliance regulations. It's a manual, redundant, error-prone, and unscalable process - and it only grows more complex and expensive over time.
Requirements
- 10+ years of experience as a software engineer, with a strong foundation in building and maintaining production systems.
- 3+ years of experience working with Node.js or React in production environments.
- 1+ years of experience with NestJS (preferred).
- Strong experience with authentication & authorization protocols like OAuth, SCIM, OIDC, and RBAC systems
- In depth knowledge of authentication and authorization systems from large third party providers
- JavaScript/TypeScript and object-oriented programming
- Building and consuming RESTful web services
Responsibilities
- Design and build scalable systems
- Guide architectural decisions
- Tackle complex challenges that span codebases and domains
- Shape the technical roadmap
- Ensure systems are reliable and secure
- Drive key cross-team initiatives from idea to implementation
- Review architecture and code for your team's projects to ensure quality, scalability, and security—while empowering the team to own implementation and delivery.
Other
- Mentor engineers across teams through guilds, office hours, and informal coaching.
- Bachelor's degree in Computer Science or a related technical field, or equivalent experience.
- Successfully completed the migration of a large company to a complex, third-party authentication system.
- Led groups of engineers through feature delivery, from scoping and ticket creation to implementation and release
- Owned major products or features, balancing technical tradeoffs like quality vs. speed or team autonomy vs. alignment
