drata
Jobs & hiring outlook.
Explore 33 grouped openings and the hiring signals in drata’s public postings. Compare the work, the locations, and the requirements before your next move.
Openings over time.
Daily observations of drata’s public job board. Advertised postings, rather than headcount or completed hires.
Tracking since 25 Oct 2026. The latest successful check on each UTC day replaces that day’s observation. Failed checks do not record zero openings.
View the recorded data (3 days)
Swipe the table to see all workplace counts.
| Day (UTC) | All postings | Remote | Hybrid | Onsite | Unstated |
|---|---|---|---|---|---|
| 2026-10-27 | 33 | 15 | 18 | 0 | 0 |
| 2026-10-26 | 33 | 15 | 18 | 0 | 0 |
| 2026-10-25 | 33 | 15 | 18 | 0 | 0 |
A closer look at the work.
The workplace mix and role categories in drata’s verified inventory.
Workplace mix
33 verified postings
- Remote1545%
- Hybrid1855%
- Onsite00%
- Not stated00%
Role categories
Grouped openings; title-based categories
Open jobs at drata
- remotePosted within 60 daysChecked
What the postings actually say.
These counts describe 33 verified postings. Policies may differ between roles and do not establish an individual candidate’s eligibility.
Evidence review from South Sudan
Selected sponsorship need: no. This selection does not assess citizenship or personal permission to work.
1 postings have no identified conflict; 14 conflict with the selection; 18 leave conditions unresolved.
Work authorization, citizenship & clearance breakdown
0 postings contain an explicit work authorization requirement.
Citizenship: 0 required, 0 preferred, 0 explicitly not required, 33 unstated, 0 conflicting, 0 not assessed.
Clearance: 0 required, 0 preferred, 0 explicitly not required, 33 unstated, 0 conflicting, 0 not assessed.
0 postings explicitly describe worldwide remote applicant policies. Named applicant countries: Mexico
Employer office countries, separate from remote applicant policies: Not available.
Read 6 examples from original postings
Examples below; the counts above cover all qualifying postings.
- APPLICANT LOCATIONS
Director, Enterprise Sales - East
Employer metadata: Provider location: Remote - US
Read original posting ↗ - APPLICANT LOCATIONS
Commercial Account Executive - Mid-Atlantic
Employer metadata: Provider location: Remote - US
Read original posting ↗ - APPLICANT LOCATIONS
“Provider location: Remote - APAC • Based in, or able to work hours aligned with, the APAC region.”
Read original posting ↗ - APPLICANT LOCATIONS
Employer metadata: Provider location: Remote - US
Read original posting ↗ - APPLICANT LOCATIONS
Commercial Account Executive - California/Nevada
Employer metadata: Provider location: Remote - US
Read original posting ↗ - APPLICANT LOCATIONS
Enterprise Account Executive (EMEA)
Employer metadata: Provider location: Remote - EMEA
Read original posting ↗
Dated source evidence · tracking since 25/10/2026
Most recent observations of source wording. These are separate from daily opening counts and do not reconstruct earlier employer policies.
- Staff Product Engineer, TPRM
Observed 27/10/2026, 05:28:45 UTC
Original posting ↗ - Staff Software Engineer, Evidence & Frameworks
Observed 27/10/2026, 05:28:45 UTC
Original posting ↗ - Senior Applied AI Engineer 2
Observed 27/10/2026, 05:28:45 UTC
Original posting ↗ - Senior Product Engineer 2, TPRM
Observed 27/10/2026, 05:28:45 UTC
Original posting ↗ - Sales Development Representative, Emerging
Observed 27/10/2026, 05:28:45 UTC
Original posting ↗ - Senior Product Manager, Compliance
Observed 27/10/2026, 05:28:45 UTC
Original posting ↗
Remote applicant locations
Countries included by at least one explicit country, region, or worldwide policy. Confirm authorization and sponsorship for each role.
All 153 compatible applicant countries
Observed openings. Clear boundaries.
Counts cover this tracked company board, not every vacancy across the employer. Location variants are grouped in the job list; trend charts count individual source postings. A removal does not prove a hire. Unknown dates, pay and policies stay unknown.
Read our source methodology ↗
