
Chief Information Security Officer (CISO)
Why this role matters
Our data, our codes and the methods behind them are what customers, partners and AI systems come to us for. Protecting them is the most important part of this job. We are looking for a leader who has defended a valuable data asset against sophisticated, well-funded adversaries.
WISEcode is also AI-native. AI writes most of our code, builds our dashboards and analyses, and runs inside our products, and our customers and partners reach us through AI apps and agents. Our principle: the corpus never goes to the AI; the AI comes to the corpus, through capabilities we control, where every input and output defines exactly what can cross. Customers, partners and AI systems receive answers from WISEcode, never the corpus. Your job is to keep that true at full speed.
This is also a management job. You run the organization that builds and operates our platform (cloud infrastructure, DevOps and IT) and you are accountable for how it performs. You set the priorities, hold people to their commitments, and control what changes, who has access, and what it costs. Nothing important lives in one person's head, and nothing reaches production without review. The President and the CEO should always know where things stand without having to ask. We are looking for someone who takes real command of an organization, not someone who advises it from the side.
The role
You own the security, privacy and resilience of everything WISEcode builds and holds, with one priority above the rest: protecting the corpus, our source code and our methods from theft, leakage, scraping, tampering and attack. You report to the President and the shape of the program is yours to define.
You also lead our small cloud infrastructure, DevOps and IT team, which builds and runs our AWS platform as infrastructure as code, our deployment pipelines and our corporate IT. You manage them day to day and keep the President and the CEO fully informed.
You are a CISO first and an engineer at heart. You came up as a software engineer and still carry the depth of a principal engineer: deep in several areas, broad across all of them. You review far more code than you write, and you know good code when you see it. From time to time you step into engineering to build a feature or a security building block end to end as a model of secure practice, then step out, leaving a pattern that stays healthy after you have gone. That keeps you close to the product; security leadership always comes first.
How fast we move
Speed is the floor here, at every level. Nobody gets to be slow because they are senior. AI has collapsed the time it takes to build, not the time a decision has to stay right: build fast, decide durably.
- Security work that used to take quarters takes weeks or days here. You ship real protections in your first weeks, not a strategy deck in your first quarter.
- You save your deliberation for one-way doors; everything else you decide, ship and improve.
- You know where a shortcut is safe and where it is not, and you never trade the protection of our data for speed.
- Progress is shown, not reported: a working control, a closed path, a measured improvement.
What you will do
Protect the corpus, our code and our methods
- Know where every part of the corpus lives and every path by which it could leave: products, APIs, AI tools, dashboards, exports, backups, laptops, vendors and people. Close the paths that should not exist and instrument the ones that must.
- Protect our source code, algorithms, AI instructions (prompts) and tool designs with the same care as the data. A leaked method is as damaging as a leaked table.
- Build the means to establish where our data came from wherever it appears.
- Defend against well-funded and state-backed adversaries: economic espionage, targeted phishing, insider recruitment and supply-chain compromise, working with federal law enforcement when needed.
- Run an insider-risk program, fair to people and effective against misuse, across employees, contractors and partners.
- When a regulator, auditor or a major customer's diligence team must verify our work, leadership decides; you make it happen under contract, scoped to the minimum, time-bound, supervised inside our environment wherever practical, and fully audited.
Stop scraping and abuse
- Defend every surface we expose: the WISEcode app, our web platform, our APIs, our interactive dashboards, and the tools that partners' AI apps and agents connect to.
- Build detection that tells a hard-working customer from an extraction campaign: behavioral and volume analytics, bot and account-farming detection, anomaly alerts and graduated responses.
- Throttle the abuse, never the customer. No arbitrary quotas: safeguards have trigger points that prompt a response (an alert, a step-up check, a review), and a customer with a real need gets more under further safeguards. Never an open tap, never a dead end.
- Lead attack detection and response across the stack, with the monitoring and on-call practice that goes with it.
Secure our AI products
- Make sure our chat, AI-built dashboards, APIs and the tools outside AI apps call never leak the corpus, one customer's data to another, our instructions or credentials.
- Lead threat modeling and adversarial testing of AI-specific risks: prompt injection (including injection hidden in data, files and web content), tool misuse, data poisoning, cross-tenant leakage, exfiltration through generated output, and model or provider compromise.
- Protect the integrity of the pipelines that feed WISEcode Intelligence™, including AI agents such as SCOUT™, so that what we publish as truth has not been tampered with.
- Secure customer-facing identity: user sign-in, tenant isolation, the authorization server that issues tokens to partners' AI apps, and API keys and their abuse.
Secure how we use AI
- Champion our AI standards without hesitation. They are demanding by design, and you understand exactly why: an AI tool that can read our full database can move all of it. You explain them to anyone and hold them, at any level, when people push back.
- Lead a crawl, walk, run path from convenience toward security, where every step strengthens and none weakens, toward a defined end state: most AI work on safe paths (our own AI tools and safe development copies), a small governed share on real data.
- Partner with the Chief Data Officer on safe development data: masked, thinned and synthetic copies realistic enough to build and test against, and the standard for what makes a copy safe to hand to a person or an AI tool.
- Enforce the standards in tooling, not instructions. AI agents have deleted production databases despite being told not to; we protect what matters with permissions, approvals and the database itself, never with a request to a model. That covers coding agents and what they may run, dedicated read-only database access for AI work, credentials an agent never sees, and logging of everything it queries.
- Govern what reaches each AI provider: company accounts only, zero-data-retention terms, contract review, and watching for policy changes.
- Secure a codebase largely written by AI: code audits by hand, with AI review tools and with static analysis at the volume AI produces, secret scanning, dependency and supply-chain controls, and CI/CD hardening.
Infrastructure, secrets and spend
- Own cloud security in AWS: accounts, network, workloads, data stores, encryption, backups and logging.
- Partner with the CTO and the Chief Data Officer on data policy, API key and secrets policy, separation of concerns and cost tracking. Separate keys per environment, service and purpose, so a leaked or runaway key has a bounded reach and a known owner. No secret in code, prompts, logs or transcripts; short-lived credentials wherever possible; fast rotation when something leaks.
- Treat runaway AI and cloud spend as a security risk. A leaked AI key, or one of our own agents caught in a loop, can run up a six-figure bill in hours. Put trigger points in place (spending ceilings per key, per run and per environment, alerts, automatic stops for loops), with a governed way to raise a limit for a real need.
- Own identity and access across Google Workspace and our business systems, and secure a fully remote workforce and contractor network across countries: device standards, least privilege, onboarding and offboarding.
- Own incident response, with regular tabletop exercises, and lead serious incidents with Legal, communications and leadership, including breach notification. Own business continuity and disaster recovery, tested rather than assumed.
Lead cloud infrastructure, DevOps and IT
- Manage the team day to day: clear priorities, agreed commitments, follow-through and regular one-on-ones. You hold the team accountable so the President does not have to.
- Give the President a short, regular written picture of our infrastructure: what changed, what is planned, what is at risk, what it costs, what went wrong. No surprises.
- Keep it visible and documented: every change through reviewed infrastructure as code, and the knowledge of how the platform is built and run written down, not living in one person's head.
- Set the security requirements for our cloud architecture and review it. Platform-shaping architecture decisions stay with the CTO; you make sure they are secure, sound and carried out.
- Keep operations with the people who run them: your job is direction, review and accountability, not the on-call rotation.
- Keep yourself honest: production changes approved by someone other than their author, independent outside testing, and any risk accepted in your own area brought to the President, never decided alone.
Privacy, compliance and customer trust
- Own the privacy program for our consumer products, including WISEcoach™ and the WISEcode app, in compliance with state consumer privacy and consumer health data laws, and lead data classification, retention and minimization across our corpus, customer data and users' personal data.
- Lead WISEcode to SOC 2 Type II, and evaluate ISO 27001, ISO 27701 and ISO 42001 as the business requires.
- Support government and research partnerships with the controls they require, such as NIST 800-53, NIST 800-171 or FedRAMP readiness.
- Own security reviews for enterprise deals (questionnaires, the trust center, calls with customers' security leaders), and represent WISEcode security to customers, partners, auditors and investors alongside the President.
Strategy and leadership
- Own a risk-based security and privacy strategy, roadmap and budget matched to our stage, and the company risk register, including vendor and AI-provider risk, bringing clear risk decisions to the President.
- Report posture, material risks and investment needs to the President, and prepare the material the President brings to the executive team and the Board.
- Work as a player-coach while hiring and developing the first security team, and build a security program that uses automation and agents for detection, triage, risk assessment and compliance evidence.
- Partner with HR and Legal on training, background check standards, and our AI and acceptable use policies. Make security a shared habit, not a gate: the safe path should also be the fast one.
What success looks like
First month: spending safeguards on every AI provider key and on our own agents; the infrastructure team's priorities set and your first written update with the President; the highest-risk paths out for our data and code identified, and the first of them closed.
First 90 days: a full map of where the corpus, code and methods live and every path out; a threat model of our AI products, APIs and dashboards with the top risks in remediation; scraping and extraction detection live; a secrets and access review across cloud, code, CI/CD and Google Workspace with gaps closed; a first pass at infrastructure documentation; an incident response plan and a first tabletop with leadership.
First year: SOC 2 Type II underway or complete, with evidence collection largely automated; an anti-scraping program that stops extraction without slowing customers; AI controls enforced in tooling, with safe development copies in daily use; insider-risk and contractor controls in force; a well-run, well-documented infrastructure team fully visible to the President; a security team hired and a roadmap the executive team stands behind.
Qualifications
- An engineer first: you started as a software engineer and still read code at the level of a principal engineer. We are not looking for a security leader who learned engineering later, or never did. You audit code at volume, by hand, with AI review tools and with static analysis, and know which findings matter.
- 12+ years across software engineering and information security, with 5+ years leading a security program or security engineering organization (CISO, Head of Security or equivalent), including building one end to end at an early-stage company.
- Experience protecting a data business, a company whose product is proprietary data and the intelligence built on it, including securing public APIs and web platforms at scale against scraping, bots and abuse.
- Hands-on experience with AI risk in production (prompt injection, agent permissions, pipeline integrity, training data provenance, provider data handling), and fluency in how AI developer tools actually work: where the reasoning runs, what travels to the provider, and how to constrain an agent with permissions rather than instructions.
- Deep AWS knowledge, architecture as well as security, enough to direct and challenge a senior cloud architect; infrastructure as code and CI/CD; OAuth 2.0, OpenID Connect and SAML.
- Experience managing infrastructure, DevOps or IT engineers, senior ones and contractors included, and controlling cloud and AI spend as a security concern.
- Led a company through SOC 2 Type II or ISO 27001 with external auditors, and know US privacy law, including CCPA/CPRA and state consumer health data laws.
- Led serious security incidents with Legal, communications, executives and customers.
- The backbone to say no to anyone, at any level, when our data is at stake, and the communication skills to be thanked for it.
- A record of protections shipped in weeks, not quarters, and still sound years later; AI-native practice you can show live, not claim; urgency, pragmatism and comfort moving between strategy and hands-on work.
Nice to have
- Defending against state-backed actors or economic espionage, including work with federal law enforcement.
- Model Context Protocol (MCP) servers or other systems that let outside AI models call into a platform.
- Data provenance for a proprietary data asset, and masked or synthetic development data realistic enough to build against.
- AI security frameworks: NIST AI RMF, ISO 42001, OWASP Top 10 for LLM Applications.
- Government or research customers: NIST 800-53, NIST 800-171, FedRAMP.
- Consumer health, wellness, nutrition or food technology.
- Remote-first companies and contractor networks across countries.
- CISSP, CISM, CCSP, OSCP or CIPP/US.
How we work
Our values are Respect, Curiosity, Disruption, Honesty and Tenacity. Our leadership principles are Customer Obsession, Invent & Simplify, Ownership, Honor Transparency and Truth, GSD (get stuff done) and Deliver Results. In this role, the ones that carry the most weight are Ownership (the security of the whole company is yours, including the parts nobody assigned), GSD and Deliver Results (ambiguity becomes progress, week after week) and Honor Transparency and Truth (hard news early and plainly, including about your own area).
Compensation
Competitive base and bonus. Details shared in the hiring process.
Benefits
- Location: Fully remote
- Unlimited PTO and Paid Holidays: Unlimited time off and 10 paid holidays
- Financial Wellness: 401(k) with a 4% company match, immediately vested
- Health Benefits: Comprehensive medical, dental, vision, life, and additional ancillary coverage
- 100% coverage for employees, with 80% covered for dependents
- 100% employer paid STD, LTD, Identity Theft, and Life insurance
- FSA and HSA plans available. For our HSA:
- $200/mo contributions for Employee plans
- $400/mo contributions for Employee + Dependent plans
Why WISEcode
We are building the layer that food decisions will run on, for people and for the AI systems they increasingly ask. That is quiet, compounding work: broadening coverage, sharpening precision, and making every output repeatable and defensible. We value transparency, rigor, and respect for the person making the decision, who deserves clear information and the freedom to reach their own conclusion. Come in early enough and you help shape how this system is protected, instead of inheriting a program someone else already designed.
Research shows that some groups hesitate to apply unless they meet every qualification. If you are excited about this role but do not check every box, we encourage you to apply. At WISEcode, we value diverse experiences, transferable skills, and the unique strengths each person brings.
WISEcode is proud to be an equal opportunity workplace and is an affirmative action employer. We are committed to equal employment opportunity regardless of race, color, ancestry, religion, sex, national origin, sexual orientation, age, citizenship, marital status, disability, gender identity or Veteran status.
WISEcode is building the world's food intelligence infrastructure
Most people have no real way to know what is in their food or what it does to them. The information is scattered, inconsistent, and written to sell rather than to inform. WISEcode exists to change that: to give people a source they can actually trust, and the freedom to decide for themselves once they have it.
Getting there takes a system that turns fragmented food data into answers that hold up: consistent, explainable, and the same whether they reach a parent scanning a label, a brand seeking verification, a regulator, or an AI model answering a question about food. That system is what we are building, and it is why the work compounds instead of resetting with every new product.
At its center is our Food Intelligence Corpus: NFP+™, our foods, ingredients, nutrients, scores and codes, the algorithms behind them, our ingredient ontology, our market intelligence, and everything derived from them. It grows every day, and much of its value rests on one fact: no one else has it.
Engineering
Remote (United States)
Deel met: