Software Engineer (Web Platform)

Hinoki Security; San Francisco (CA); On-site; USD 120,000 - 160,000; Full time

Job summary

Hinoki Security is seeking a Frontend Engineer to take ownership of the product surface our customers interact with. This includes optimizing verification flows and enriching investigative features using AI. If you're passionate about React and performance, this could be a great fit.

The ideal candidate will have 3-6 years of engineering experience and demonstrate a strong understanding of best practices in frontend development, particularly with deep React expertise. Join us to shape the experience of security engineers and analysts.

Qualifications

• Three to six years of engineering experience required.
• Ability to optimize React performance and work with the latest RSC innovations.
• Experience in shipping products with attention to detail.

Responsibilities

• Own the frontend end-to-end, responsible for performance improvements.
• Implement features for analysts to verify agent work and report incidents.
• Collaborate with engineers to enhance product experience.

Skills

Deep React expertise

Performance measurement

Product sense

AI-native workflow

High agency

Taste for small changes

Tools

TypeScript

C++

Job description

The role

This is a critical engineering hire to own our frontend end-to-end. You'll be responsible for the product surface our customers interact with every day. That includes the verification flows where analysts confirm our agents' work, investigative features where security engineers confirm vulnerabilities on remote assets using AI agents, and the reporting surfaces where investigations turn into reports.

We are looking for someone who treats frontend as a specialty and pushes the boundary of frontend performance. If optimizing React and diving into the latest RSC innovations excite you, then you would find this role very fun.

What we're looking for

Three to six years of engineering experience, plus:

• Deep React expertise. You should be the person other engineers come to when they hit a wall in React. Reasoning about the rendering model and hook internals shouldn't require a trip to the docs, and you've spent enough time in DevTools to know what a bad render trace looks like at a glance. Bonus if you've been following the RSC work closely or have strong opinions on Suspense boundaries.
• A point of view on performance. Tell us what you measure and why, and walk us through a piece of performance work you're proud of.
• Product sense. Show us something you shipped where the small details actually show. Things like empty states that don't feel like an afterthought, tiny shortcuts that users naturally discover, motion that helps comprehension instead of decorating.
• AI-native workflow. Claude Code, Codex, or Cursor is in your daily loop. You can articulate where these tools help and where they don't.
• High agency. You read a plan doc and ship. You don't wait for design tickets. You fix what's broken regardless of whose code it is.
• Taste for small, reversible changes. You know when to extract a component and when to keep markup inline. You don't ship 800-line refactors when 30 lines would do.

We work in TypeScript and C++ but care more about engineering depth than specific languages. No security background required. We'll teach you the domain.