Software Engineer

Who We Are Looking For

We are looking for a Software Engineer who operates with clear ownership. You’re not just filling a seat. You’re setting the standard. You believe great execution brings strategy to life.

How You Operate

You bring mission-driven grit to every challenge, running toward hard problems rather than away from them. You prioritize customer outcomes over internal processes. You choose truth and clarity over performative politeness. We look for builders with a bias for action – people who own the fix when things break, share credit with the team, and possess the intellectual humility to care more about getting to the right answer than being right.

How are you using AI today in your current role? What specific tools are you using? If applicable, show us your last AI experiment.

What You Will Own

• Own the Outcome: Build and ship features across the full stack of the Praetorian Guard platform, from the Go serverless backend to a React frontend used by security teams daily. You own it from design through production operations.
• Take Accountability: Owning the outcome means taking accountability to overcome the challenges in developing and operating the Praetorian Guard platform.
• Raise the Bar: Write code that is clear, tested, and built to last. Push the team’s engineering standards forward through code review, technical proposals, and leading by example.
• Drive Impact: Work directly with offensive security engineers to translate real-world vulnerability findings into platform capabilities. Your code doesn’t just run, it scales the impact of every security engineer on the team.
• Scale the Platform: Design systems that handle the complexity of attack surface management at scale: graph databases modeling millions of asset relationships, queue-based architectures processing continuous security scans, and real-time interfaces that make complex data actionable.

What You Bring

• The Foundation: A Bachelor’s degree in Computer Science, Engineering, Mathematics, or Physics, backed by 0–5 years of experience in cybersecurity, startups, or tech companies.
• Backend Fluency: You write Go that is idiomatic, testable, and production-ready. You understand serverless architectures, API design, and working with databases under real load.
• Systems Thinking: You reason about distributed systems, concurrency, failure modes, and data flow. You don’t just write the function—you think about what happens when it’s called ten thousand times a second.
• Frontend Ability: You apply software engineering principles to guide AI agents to build responsive, performant UI in maintainable code. You care deeply about the final user experience and do not stop iterating until it is right.
• Builder’s Instinct: You have side projects, open-source contributions, or technical writing that shows you build because you want to, not because someone told you to. You’ve shipped something real outside of a classroom.

If This Position Is Wildly Successful, In One Year You Will Have:

• Shipped major features across the Guard platform that security teams rely on daily
• Built infrastructure that scales, such as queue-based scanning pipelines, graph query optimization, and AWS serverless architecture.
• Written code that your teammates trust: clean and well-tested. Your pull requests raise the bar and your reviews make the people around you sharper
• Integrated AI tooling into your development workflow, moving fast in complex systems without sacrificing quality or understanding
• Honed your product skills by turning high-level requests into practical features that real customers rely on and generate delights.
• Demonstrated ownership across the full stack, from CloudFormation templates and Lambda handlers to React components and Playwright tests, not because you were told to, but because the problem demanded it
• Closed the gap between field findings and platform capabilities by partnering with offensive security engineers to translate recurring vulnerability patterns into automated detections that multiply the team’s impact
• Contributed to Praetorian’s engineering culture through technical blog posts, internal knowledge sharing, or open-source contributions that reflect the depth of what we’re building
• Mentored junior engineers and contributed to a culture of continuous learning, raising the technical floor across the team through your example and your investment in the people around you