Help build security for the software AI makes easier to create.

AI is changing who can build software. Developers, founders, startups, and businesses can now turn ideas into working websites, applications, and products faster than ever. But as software becomes easier to create, the need to understand its security becomes more important. That is the problem we are building AURIX SHIELD around.

We are building a security platform that connects:

And we are looking for people who want to help solve difficult problems at the intersection of software, security, AI, and product engineering. We are not building another dashboard that simply displays scanner results. We are building a security workflow around what happens after something is detected.

A security finding needs context. A fix needs verification. A resolved issue can return. A product changes after deployment. And AI-generated software creates new opportunities—and new security questions. That makes security an ongoing engineering problem. That is what makes AURIX SHIELD interesting to build.

What We Are Building

AURIX SHIELD brings multiple security workflows into one platform. Detect security issues across websites, software, and GitHub repositories. Track security findings and how they change between scans. Connect remediation with actual scanner-based verification. Continue checking security as the product changes.

Help developers understand and investigate security findings using AI. Give users a conversational interface for working with security context. We are interested in problems such as: Security tools can produce enormous amounts of technical information. We want developers to understand what actually matters.

A changed status is not the same thing as verification. We care about connecting remediation with evidence. A scan is a snapshot. Software keeps changing. Security needs to be tracked continuously.

AI can help explain and reason about security information, but it should not hide the underlying evidence. We are interested in building that boundary correctly. We are interested in people who enjoy building difficult products rather than simply implementing specifications. That can include people with experience in:

• Security engineering
• Application security
• Web security
• Software engineering
• AI engineering
• Developer tools
• Cloud infrastructure
• Product engineering
• Developer experience
• Security research
• Product design

You do not need to fit every category. What matters is the ability to think deeply about problems, build carefully, and learn quickly. We prefer working software over impressive demos. Security products need strong boundaries between detection, findings, verification, and AI. A security product should not claim something happened when it did not.

If something can be tested, test it. If something can fail, understand how it fails. Security tooling should help users make better decisions rather than hide complexity behind unexplained automation. AI is central to the world AURIX SHIELD is being built for. But we do not believe that adding "AI" to a security product automatically makes it useful.

The important question is:

What can AI actually help a security engineer or developer understand better?

At AURIX SHIELD, AI is being used as an intelligence layer around security context. The underlying security engines still matter. Evidence still matters. Verification still matters. The AI should help make those things easier to understand and investigate.

Working on AURIX SHIELD

AURIX SHIELD is being built with a strong product-engineering mindset. That means we care about:

• Product quality
• Security correctness
• Clear UX
• Reliable backend systems
• Deterministic workflows
• Testing
• Observability
• Developer experience
• Honest product communication

We are building a security product where small implementation details can affect whether a security result can be trusted. That requires careful engineering. We are building selectively. We are not listing artificial job openings simply to make this page look like a traditional careers portal. When we open a role, it will represent a real problem we need someone to solve.

Current opportunities will be listed here when available.

What We Look For

We value people who:

• Enjoy understanding why something works, not just making it work.
• Can take ownership of a problem and move it forward. Especially when those details affect security, reliability, or user trust.
• Believe good products are often built by asking better questions.

Security, AI, and software development change quickly. Technical complexity should ultimately produce a better product experience. The software-building landscape is changing. AI is lowering the barrier to creating software. That is exciting. But software security cannot remain something that only happens after the software is built. We believe security needs to move closer to the development workflow.

That is the problem we are working on. And if that problem interests you, we would like to hear from you.