# Dan Arias

Dan Arias is a software engineer focused on security, privacy, and digital identity. Their writing explores how to secure AI systems and why experienced engineering judgment matters when using AI to build software.

- Profile: https://b2binfluencer.marketing/creators/dan-arias/
- LinkedIn: https://www.linkedin.com/in/getdanarias
- LinkedIn followers: 1,504
- Topics: artificial-intelligence, cybersecurity, ai-security
- Based on 11 dated posts, latest 2026-09-30

## Summary

A named practitioner voice on securing AI agents and human oversight.

- Best for: An AI-security platform wanting thought leadership on agent identity and human accountability.
- Not for: A campaign needing guaranteed distribution into named buyer segments.
- Check first: Confirm whether they accept sponsorships and have audience data on security buyers.

### Takeaways

- AI agents should be identified, tracked, audited, and protected.
- AI cannot replace the engineering judgment needed to build and maintain software safely.
- A few models writing everyone's code create a concentration risk.

## Main ideas

- **Engineering judgment is what AI cannot supply**: Dan Arias argues that claiming AI lets anyone build, debug and ship software is like claiming AI lets anyone practise medicine. Software engineering, in this account, is broad and deep: distributed systems, architecture, continuous delivery, accessibility, performance at scale, data management and integrity, and cybersecurity all require experience, knowledge and taste. LLMs can absorb information and return an answer wrapped in jargon convincing enough to trigger imposter syndrome, but they lack the experience to smell a bad answer. Someone still has to demand evidence, verify it and stop bloated or underdeveloped code reaching production.
- **Every AI agent should be identified, tracked, audited and protected**: Dan Arias treats security and identity as the lens for AI adoption. Writing after leaving Auth0/Okta, they say their focus has stayed on security, privacy and identity, and that they spend free time on AI engineering with a strong emphasis on security and identity governance. The stated goal is a world where every AI agent can be identified, tracked, audited and protected. AI now sits inside software build and delivery pipelines and on both the defensive and offensive sides of cybersecurity, making trust and safety especially important. Arias concludes that AI must be secure by design and that no target is too small: any weak point can be a stepping stone to a bigger one.
- **LLMs are probabilistic autocomplete; the labour model behind them is the problem**: Dan Arias calls an LLM a probabilistic autocomplete with no genuine reasoning — efficient at copying humanity's homework, but unable to do its own. The argument then turns to work: forcing employees to run their knowledge through these tools so the models absorb it is vampiristic. Arias links the prospect of models trained on every message, document, commit and review from junior to principal engineers to mass unemployment. Replacing tech recruiters with LLMs is a red flag, they say, because recruiting depends on authentic human-to-human engagement. They also criticise marketing models as human-like intelligence for harming mental health and leaders' decisions.
- **A few models writing everyone's code create a concentration risk**: A shorter argument about dependency: engineers required to use LLMs at work largely rely on the same handful of systems — GPT, Claude and Gemini — and inherit the same limitations, bugs, hallucinations and frustrations. Their code ends up with the same defects. Dan Arias finds it unsettling that a few systems write code across companies worldwide and asks what happens when one turns that accumulated know-how toward entering another company's business. Organisations are sharing more than code with the models: knowledge about security, marketing, human resources and sales goes in too.
- **Learning in public and pointing to worthwhile resources**: Alongside the criticism, Dan Arias makes continuous learning a priority and often shares what they find. They spend free time levelling up on AI engineering, focusing on security and identity governance, to help people interact safely and securely with AI. They also recommend other people's technical material when it is substantive.

## Work to read

- ["Security is part of the MVP" — and AI agents need identity too](https://www.linkedin.com/posts/activity-7428789594042740737-pwhQ)
- [Why AI does not make everyone a software engineer](https://www.linkedin.com/posts/activity-7496891084837425152-rJAe)
- [A few models writing everyone's code](https://www.linkedin.com/posts/activity-7454274556997066753-PIzP)
- [LLMs as probabilistic autocomplete, and what that costs workers](https://www.linkedin.com/posts/activity-7462043035544055809-UV24)
- [A short recommendation of IBM Technology's cybersecurity and AI series](https://www.linkedin.com/posts/activity-7380260302304518144-XDn3)

## Brand relationships

- **Auth0 / Okta** (employment)
- **IBM** (mention)

## Partnerships

No partnership or sponsorship offer appears in Dan Arias's posts. The five posts offer personal commentary on software engineering, AI, security, and identity; none announces a sponsorship policy, media kit, rate card, or business inquiry route. They take an engineering and security-practitioner perspective rather than presenting creator placements, so a brand would be starting a conversation rather than choosing from published packages. Ask directly whether they accept sponsorships and, if so, what formats and terms they offer; confirm those details before building a campaign plan around them.

## Alternatives

- Andrew Ng: Consider Andrew Ng when the vendor wants the widest association with the "future of software engineering" story rather than a security specialist. The posts argue that AI is accelerating software engineering more than any other profession, that deciding what to build is now the bottleneck rather than the building, that engineers are absorbing product work and product managers are learning to build, and that design, marketing, and legal compliance become the slow steps once coding speeds up. An AI Dev conference on April 28-29 in San Francisco is named as the venue for that discussion. For a vendor whose agent-identity message needs to sit inside a broader "how teams and work change with AI" narrative, this brings an established event platform and a team-organization argument the campaign can ride on.
- Rupinder Singh: Consider Rupinder Singh when the vendor wants to reach product managers who choose and ship AI features, using an interview or podcast format instead of written essays. The posts are built around practitioner conversations and frame AI product management as a decision problem under uncertainty — the cited point is that the hardest part is not picking a model or writing a prompt but making product decisions when the product is probabilistic and the manager is still accountable. For a vendor seeking a co-produced episode aimed at PMs evaluating AI tooling, that format matches the observed output more closely than opinion essays.
- Noah Stambovsky: Consider Noah Stambovsky when the agent message is better framed through integration and data reality than through identity and accountability — getting agents to work across many disconnected tools without consolidating first. The posts argue that with MCPs, LLMs can produce join-like reporting across a dozen separate tools, that the unresolved limit is data that actively disagrees with itself, and that teams which stayed siloed with clean data may run more smoothly than those that consolidated badly. A second post uses a 1,200-respondent HubSpot survey to press on lifecycle definitions, handoffs, and ownership inside a CRM. For a vendor selling agent tooling into messy go-to-market stacks, that is a more useful argument than agent identity on its own.

---
AI-assisted summary of public posts. Audience demographics are not available. Engagement appears only where we checked recent posts. Method: https://b2binfluencer.marketing/methodology/