Company · Leadership

Who leads, how they lead. And the standard we hold.

This page exists so prospective customers, partners, and team members understand how decisions get made at Safeguard — and the principles the leadership holds themselves to. It is intentionally short on vanity bios and long on operating practice. The first signal of a serious company is what it expects from its own leaders.

Founder

The person who started this.

Hritik Kumar Sharma
Founder & CEO

Hritik is the founder of Safeguard and leads product direction, strategy, and the model-family roadmap. His areas of focus are the long-term shape of the Griffin lineup, the hiring bar for senior engineers and researchers, and the key customer relationships — particularly the regulated and sovereign accounts where the platform's deployment shape gets stress-tested. He sets the bar for what shipping discipline looks like at Safeguard and writes the public material that frames how the company explains itself.

What I think about
  • The integrity of the security-only training corpus and the people who curate it.
  • Sovereign and air-gapped deployment readiness — the bar a regulated customer should expect.
  • The credibility of the partner programme — does a partner motion actually move customer outcomes.
  • The structured-trace contract — every Griffin output reads like a defender wrote it.
Leadership functions

Six functions, six owners.

The senior functions and what each one owns. We name the role and the responsibility — not the person — because the role is the contract.

AI Research leadership

Owns the model lineup, training corpus, eval harness, the research log, and the safety constitution applied at the model level. Decides what ships, what gets held, and what gets re-run.

Engineering leadership

Owns the platform end to end — the control plane, scanner fusion, model serving, surfaces in the IDE and CI. Owns deployment shapes from shared cloud to air-gapped and the performance posture across all of them.

Security leadership

Owns Safeguard's own security posture — tenant isolation, signed weights, key management, incident response, and the bug bounty programme. The internal answer to every question we ask our customers to answer about themselves.

Customer & Partner leadership

Owns customer relationships across enterprise and public-sector accounts, and the partner programme. Joint go-to-market with channel partners, named-account coverage, and the renewal motion.

Compliance & Trust leadership

Owns SOC 2 readiness, ISO 27001, FedRAMP HIGH posture, customer questionnaire automation, and regulator engagement. The function that turns the platform's controls into evidence the buyer's auditor can accept.

People & Culture leadership

Owns the hiring standard, the leadership operating manual below, and the values plus constitutions framework. The function responsible for whether the company looks like its writing six months from now.

Operating manual

How decisions get made here.

Five rules. They are the leadership operating manual. We read them out loud at the start of new-hire onboarding for senior roles.

01

Disagree explicitly

Every senior meeting has a "what are we wrong about" item. Disagreement is not a problem; uncoded disagreement is. If a senior leader leaves the room with a private objection that did not surface in the room, the meeting failed.

02

Write the memo first

Major decisions are documented in a short memo before a meeting. The meeting reviews the memo; it does not substitute for it. If the memo cannot be written, the decision is not ready and the meeting is premature.

03

Reversible vs irreversible

Small reversible decisions move at the lowest competent level. Irreversible decisions go up. Confusing the two is a leadership failure — escalating a reversible call wastes the room; lowering an irreversible one risks the company.

04

Customer and engineer voices have a seat

Every product decision packet includes the customer-evidence summary and the engineer-impact summary. A decision that did not consult those two summaries is sent back. Neither is allowed to dominate; both are required to be present.

05

Post-mortems are blameless and public (internally)

If a customer-facing incident happens, the RCA is read by everyone, not buried. Names of people are omitted; names of components are not. The intent is to make the next incident shorter, not to make the previous one quieter.

The contract — outward

What leadership owes the team.

Clear strategy

What we are building, who it is for, and how this quarter connects to the next two — written down, updated when it changes.

Honest feedback within 24 hours of asking

If a teammate asks for feedback, they get it inside a day. Not next sprint, not next review cycle.

Defending the team in public

Mistakes are owned by leadership in public and corrected with the team in private. Never the inverse.

Transparent compensation philosophy

How bands work, how equity works, how promotion works. Documented and the same for everyone at the same level.

Decision rationale shared in writing

When a non-trivial decision is made, the reasoning is recorded. People who were not in the room can still understand why.

No surprise reorgs

Structural changes are communicated to affected people first and given a runway. Engineers should never learn their manager changed from a hallway chat.

The contract — inward

What leadership expects from the team.

High judgement

We hire for judgement and then expect it to be used. A title is permission to decide, not a reason to defer.

Said-what-you-meant communication

Write clearly. Disagree directly. Hedging that protects the writer at the reader's expense is not a virtue.

Owning outcomes, not titles

The work is the deliverable, not the role. If something is broken inside your remit, it is yours to fix or yours to surface.

Technical depth in your function

Whatever function you sit in, be the person in the room who can answer the second-level question, not just the first.

Respecting the customer's time

Every call, every email, every demo — the customer is giving us time we have to earn back. Show up prepared.

Respecting each other's time

Async first, meetings sparing. If a meeting can be a document, it is a document. If a document can be a paragraph, it is a paragraph.

Comp philosophy

Promotions and compensation.

Base pay is at market for the role and the location. Equity is granted with a written explanation of the vesting shape, the strike convention, and the dilution outlook — not just a number and a date. Equity that is granted but not understood is worse than no equity at all.

Promotions require the role to exist. We do not invent titles to retain people, and we do not promote into roles whose scope has not been written down. If the work is there, the title follows; if the work is not there, the title does not exist.

Offers do not change because someone negotiates harder. The first offer is the best offer at that level — same conversation, same outcome, every time. The point is to remove the tax on people who do not enjoy the negotiation game.

Hiring bar

How we hire.

High judgement over high credential

We hire for how someone thinks, not where they last worked. The brand on the resume is information, not a decision.

Written-communication test in every loop

Every candidate writes — a short technical document or design memo — and a senior reader reviews it. Bad writing usually means muddled thinking.

Paid technical exercise for engineers

A small take-home, paid for the candidate's time, instead of a timed whiteboard. It reads like the work the role actually does.

Two-on-two senior review on every offer

Two senior reviewers, two perspectives. An offer goes out only when the case for the hire is written down and survives the second pair of eyes.

If this is the way you want to work.

Open roles are listed in careers. If you want to talk to leadership before applying — or before signing a customer agreement — the contact route is short.