Operational AI
Agents that retrieve evidence, use governed tools, advance real workflows, and know when human judgment should take over.
Sense is building AI systems for decisions with real assets, real money, and real operational consequences. We are a small team of builders working across software, data, AI, and domain expertise to make difficult work more understandable and dependable.
Explore the open roleThis is not a corporate role. You will be close to the product, the architecture, the customer problem, and the production consequences of what you ship.
Our platform spans agentic workflows, document intelligence, complex data models, financial operations, maps, security, and a growing set of focused products. The most valuable problems live between those layers. We want people who are energized by the whole system.
Agents that retrieve evidence, use governed tools, advance real workflows, and know when human judgment should take over.
Identity, lineage, documents, ownership, revenue, and operational records that must remain correct across imperfect systems.
Background jobs, event-driven automation, approvals, retries, observability, and recovery when production does something unexpected.
Asset experiences that connect maps, three-dimensional context, business records, and decisions in one operating surface.
Tenant isolation, authorization, auditability, evidence, and safe AI actions built into the product—not left to a prompt.
The components, contracts, APIs, and technical choices that let a small team ship a coherent platform quickly.
Our principles are practical. They shape how we choose problems, make technical decisions, work through disagreement, and decide when something is ready for a customer.
We learn how a decision is actually made, where the evidence lives, what can go wrong, and what a trustworthy result requires before deciding what to build.
The interesting problems cross interfaces, models, APIs, databases, queues, and customer conversations. We stay with the outcome across those boundaries.
We take difficult systems seriously without using sophistication as a substitute for judgment. The best design is the smallest one that safely carries the requirement.
A confident answer is not enough. Identity, provenance, permissions, validation, and a visible exception path are part of what we ship.
We challenge assumptions with evidence, share unfinished thinking early, and care more about reaching the right answer than protecting an idea or title.
A feature is not done when the demo works. It is done when it is understandable, observable, secure, recoverable, and useful in production.
Build across product, platform, AI, data, and infrastructure. This is a hands-on role for someone who wants unusually broad ownership and is comfortable moving from an ambiguous operational problem to production code.
The stack is context, not a checklist.
Our process is designed to find thoughtful builders with different paths into the work. Here is what to expect.
AI guidance for candidatesWe care about what you can do, not where you learned to do it. A traditional computer-science path can be excellent preparation, but it is not the only one. If you have built an ambitious product, contributed meaningful open-source work, written a thoughtful technical essay, or pursued serious independent research, put that evidence near the top of your application.
Engineers at Sense do research, and exploratory AI work becomes engineering. You may evaluate a model in the morning, tighten a data contract in the afternoon, and trace a production workflow the next day. We value people who can move between discovery and disciplined delivery without confusing a promising result for a finished system.
Depth matters, but so do clarity, curiosity, and ownership. We want builders who can explain tradeoffs, learn a complicated domain, ask for help early, disagree without ego, and care about the person who will rely on the result.
Interviews are remote-friendly, and we will coordinate timing directly with you. The process is meant to reveal how we would work together—not whether you have memorized a particular framework or interviewing trick.
We talk about what you have built, the decisions you owned, what you want to learn, and why the problems at Sense interest you. You will have plenty of time to question us too.
For technical roles, expect to work through a realistic engineering problem with us. We care about how you frame the problem, use evidence, make tradeoffs, and respond when the first idea is incomplete.
We explore a substantial project from your experience and discuss how you would approach a cross-layer Sense problem. This is a conversation, not a trivia test.
The final conversations focus on working style, expectations, and open questions on both sides. We want you to understand the opportunity as clearly as we understand your work.
We build with AI and expect candidates to use modern tools thoughtfully. You are welcome to use AI to research Sense, prepare for conversations, pressure-test ideas, or improve the clarity of your application.
Your materials still need to be accurate and genuinely represent your experience. During a live or take-home exercise, we will tell you what tools are allowed. If you use AI, be ready to explain the result, verify it, and take responsibility for every decision in it.
Hiring communication from Sense will come from an @sensesoftware.ai address. We will never ask you to pay a fee, purchase equipment from a designated seller, share a password, or send banking information before formal employment paperwork. When in doubt, return to this page and contact us directly.
We use application information to evaluate candidates, communicate about the process, and meet applicable legal obligations. Please review our privacy policy for more information about how Sense handles personal information.
We want candidates to be able to participate fully in our process. If you need a reasonable accommodation for an interview or exercise, email us with what would help. You do not need to provide detailed medical information in your first message, and accommodation requests will not affect how we evaluate your application.
Request an accommodationNo. Domain experience is useful, but strong engineering judgment and the ability to learn a complicated operating environment matter more. We will help you build the context you need.
Not necessarily. You should be interested in how modern AI systems behave in production and willing to become rigorous about their limits. Excellent software, data, and systems experience transfers well.
Lead with the strongest evidence of what you can do: a system you shipped, a difficult failure you diagnosed, open-source work, a technical essay, research, or an unusually ambitious independent project.
Apply if the work fits your strengths and the mission genuinely interests you. We care more about demonstrated ability, judgment, and learning velocity than a perfect sequence of titles.
Yes, when used thoughtfully and transparently. Your application still needs to represent your experience accurately. For exercises, we will state which tools are appropriate so expectations are clear.
A résumé is useful. Evidence of judgment, depth, and finished work is better. If the title is imperfect but the mission fits, write anyway.
Email Sensesales@sensesoftware.ai