Should you work at Protege?
Yes, if you want fully remote work with frontier AI labs as customers. Protege is remote on all 21 of its open roles, raised a $30M Series A, puts technical staff directly in front of customers including researchers at frontier AI labs, and sets explicit 30/60/90-day expectations so the ask is stated before you apply. Ambiguity is a requirement in every posting rather than an occasional condition, at least one role expects work outside standard hours when deals are active, internal processes are described as immature, and we hold no verified employee reviews.
Read from 21 live roles, 21 full job descriptions and 3 funding rounds. No employee reviews, no ratings.
Good fit if
- Roles are scoped as end-to-end ownership rather than narrow slices, across engineering, product, and delivery.
- Several postings offer 0-to-1 scope where the hire defines the direction rather than executing a set plan.
- Technical staff work directly with customers, including researchers at frontier AI labs, rather than through intermediaries.
- Research work is tied to deployment and product decisions, not isolated from them.
Think twice if
- Ambiguity is a stated requirement in every posting, not an occasional condition. Candidates who want defined problems are explicitly discouraged.
- At least one role states that work outside standard hours is expected when deals are active.
- Existing internal processes are described as immature in places; the hire is expected to fix them.
- Some roles combine functions that are often separate elsewhere — customer relationship management, delivery, and architecture simultaneously.
We can't tell you
- What managers are actually like day to day
- Attrition, tenure or promotion rates
- Whether the pace is sustainable
- Equity terms — no posting states them
What it pays
No active roles publish a salary range.
0 of 21 roles post a range
No role here publishes a salary range.
Where you'd sit
Of 21 roles that specify a setup.
Who they're hiring
21 live roles across 8 teams.
What the job descriptions ask of you
A reading of how 21 postings are worded — not a score, and not comparable between companies.
Pace Fast
Urgency is stated across postings as a defining condition of the work.
“The pace is fast, the ambiguity is real”
Autonomy Self-directed
Postings ask for people who can run searches, engagements, and roadmaps with limited oversight.
“Comfortable owning multiple searches independently and operating with minimal direction”
Structure Ambiguous
Processes are described as incomplete, and hires are often asked to establish them.
“Introduce standardized processes for experiment tracking, documentation, and reproducibility.”
Ownership End-to-end
End-to-end responsibility is the repeated framing, from scoping through delivery and follow-up.
“Own healthcare customer engagements end-to-end... from initial scoping through implementation, delivery, and post-delivery support”
Collaboration Cross-functional
Most roles name specific cross-functional partners as a standing part of the job.
“Partner closely with Product, Engineering, and GTM teams to identify high-value research opportunities”
The upside
Stated by Protege in its own postings.
Roles are scoped as end-to-end ownership rather than narrow slices, across engineering, product, and delivery.
“hands-on, backend- and data-heavy role with end-to-end ownership of the pipelines that move and process data at volume”
Several postings offer 0-to-1 scope where the hire defines the direction rather than executing a set plan.
“own a high-impact, 0-to-1 product value stream at Protege... responsible for the vision, roadmap, and execution”
Technical staff work directly with customers, including researchers at frontier AI labs, rather than through intermediaries.
“the primary technical and research link to the customer — not a technical resource brought in for credibility”
Research work is tied to deployment and product decisions, not isolated from them.
“applied research is tightly connected to real-world deployment. Researchers work directly with large-scale datasets, production systems”
Postings set out explicit 30/60/90-day expectations, so what is being asked for is stated up front.
“30 DAYS: RAMP... 60 DAYS: TAKE OWNERSHIP... 90 DAYS: OPERATE INDEPENDENTLY”
Engineers are asked to convert repeated one-off work into reusable tooling, which the postings treat as part of the job.
“Turn repeated one-off data handling work into reusable processing patterns, internal tooling, and platform capabilities”
The trade-offs
Also from the postings — not complaints from employees.
Ambiguity is a stated requirement in every posting, not an occasional condition. Candidates who want defined problems are explicitly discouraged.
“We are not looking for someone who needs the problem fully defined before they can start.”
At least one role states that work outside standard hours is expected when deals are active.
“when deals are live, availability outside standard hours is part of the job”
Existing internal processes are described as immature in places; the hire is expected to fix them.
“Right now, that process is manual, inconsistently applied, and a source of delivery risk. Your job is to change that.”
Some roles combine functions that are often separate elsewhere — customer relationship management, delivery, and architecture simultaneously.
“managing customer relationships, technical delivery, and architecture decisions at the same time, across multiple deals at a time”
Research roles carry customer-facing and commercial obligations alongside the research work.
“This is fast-iterating, customer-facing research on a customer's timeline.”
Speed is emphasised repeatedly and paired with quality expectations, meaning both are asked for at once.
“Attention to detail without losing speed, and a bias to action”
Employee sentiment
No data yetWe hold no verified employee reviews for this company. Sentiment appears here only when it comes from verified employees — never from product or customer ratings, which measure something else.