Role Summary: Software Engineer, Internal AI Products
A Software Engineer who builds the tools this company runs on. You build agent loops, and the loops build the solutions. You work towards a Company Brain that anyone here can ask.3–5 years’ experience · Reports to the CFO ·
THE KEY SKILL
You build the agent loops that build the solutions. You will not write every automation by hand. You build the loops that
write them. Ship a prototype every week. You ship something every day.
You’ll be building a Company Brain with access control. One system that holds what the company knows about finance,delivery and people. Anyone can ask it a question. Each person sees only what they are cleared to see.
One hard filter. If you cannot write and debug production code, and have not done it before, please do not apply.
CORE RESPONSIBILITIES
• Work the backlog: You pick items off a live, ranked backlog. You learn each function by building inside it. There is no discovery phase. What you learn goes back into the backlog and changes what comes next.
• Build the product: You design, build and ship tools that people use every day. Reconciliation, MIS, the deal desk,quote to cash, or whatever the real bottleneck turns out to be. You choose the tools and frameworks.
• Wire the data: Connect the systems each team already uses, so that the same number means the same thing everywhere.
• Make it visible: You build live dashboards and alerts that leaders read on their own, instead of asking someone for a report.
• Keep it running: You own uptime and accuracy for everything you build. Anything that touches money or people needs a person in the loop.
THE STACK
• Build with: Python and TypeScript. You write production code. Frontier model APIs from Anthropic, OpenAI or Google, with tool calling and structured output. At least one agent framework. MCP to connect agents to internal systems.Postgres and pgvector, or something similar, for retrieval. You deploy on GCP, and you debug your own work.
• Work in agents daily: Claude Code, Cursor or something like them, as the way you write code every day. You should have a clear view on how to run the loop, and on when a person has to step in.
• Connect to: The systems we already run on for accounting, CRM, hiring and IT support, along with Google Workspace.Most of the work is getting them to agree with each other.
• Check what you ship: Anything that produces a number needs a way to catch it going quietly wrong. Test sets, regression checks, and alerts on the output as well as on the job.
WHAT GOOD LOOKS LIKE
• Something you built is running by week two, and someone is using it.
• By day 90, time spent on reconciliation or reporting is down by a number you can defend to the CFO.
• Every tool you ship has a named owner who is still using it 60 days later. That is the measure that counts.
• Leaders stop asking for numbers, because they can already see them.
• By the end of your first year, a first version of the Company Brain answers real questions about Finance, and each
person who asks sees only what they are cleared to see.
WHO THIS IS FOR
• You have built products: 3 to 5 years at a software product company, on a product with real users at scale. That means 100k+ monthly active users, or heavy daily use by a large enterprise customer base. You have owned code in production, in front of real users, long after it shipped.
• You ship alone: You are comfortable as the only engineer in the room, and the only person on call for what you built.
• You work out new ground fast: A domain you do not know is interesting to you. You start without waiting for a spec or an expert.
• You are fluent with agents: One person cannot cover a whole company by hand. You use agent loops heavily and youare good at it.
• You write and speak clearly: Half this job is pulling a process out of a finance or delivery lead and giving it back to them correctly. You work remotely, so this matters a great deal.
HOW WE WILL ASSESS
• A design problem: Live. We give you a function of the B2B company, and you design the system for it. We watch how you break down a domain you do not know, how you size it, and what you leave out on purpose.
• A build exercise: Live and screen-shared, on your own setup, with your own agents. You build the way you normally build. We watch how you run the loop, when you step in, and what you decide to skip.
• Your work and your questions: We talk about what you have shipped before. You ask us whatever you want.
Communication is not a separate round. All three sessions are live, and how clearly you explain your thinking is part of how we judge you.
WHERE IT LEADS
You report to the CEO and CFO from your first day. Your charter covers the whole company. Nothing sits between you and production. Very few engineering jobs offer all three at once, and that is why this one exists.
In 18 months you will know how this company really runs: the data, the money, and the gaps between teams. The rolethen changes shape to fit whatever the biggest open problem is by then.