openashbyhqbvp
Software Engineer, AI Enablement
Aiwyn
LocationRemote (US-based)
WorkplaceFull
EmploymentFullTime
Posted2026-05-18T14:20:59.362+00:00
Last observed2026-06-29 02:03:19.724515
Job idbvp-aiwyn:ashbyhq:4a2aacbc-0614-4161-9d79-419a1eb4b45a
WHO IS AIWYN AND WHAT DO WE DO? Aiwyn is the first complete platform for modern Accounting Firms. Backed by top-tier investors like Bessemer, KKR, and Revolution, we're one of the fastest-growing scale-up SaaS companies in the world. We build category-defining technology, and we're doing it with world-class people, processes, and products. To learn more, visit our website https://aiwyn.ai/ We work with the majority of the Top 500 firms in the country. We're modernizing the software accounting firms rely on every day, replacing decades-old systems and brittle integrations with tools they can actually trust, and we have rare product-market fit in an industry that's about to change permanently. We're hiring a Software Engineer for AI Enablement on the Productivity team. The job is to make AI the default way work happens at Aiwyn, for every team including engineering itself. THE ROLE AI only compounds when it's woven into how an organization actually works, not bolted on as another tool. We need a systems thinker who will work alongside teams across the company (sales, success, ops, finance, and engineering), see how work actually gets done, and remove the friction. The toolkit is broad and the right answer depends on the problem. You'll own the AI adoption layer that sits across the whole org, with engineering as a first-class user. Making engineers measurably faster with AI tooling is one of the highest-leverage applications of this role, and it's where you'll often start. The mandate is broad: make AI the default way work happens here, with whatever combination of tools, agents, and systems that takes. WHAT GOOD LOOKS LIKE - Our internal AI assistant is the first stop, not the last resort. People use it because it works. Information flows are mapped, gaps get followed up on, and answer quality improves week over week. - Every team has at least one custom agent that earns its keep. You've sat with the team, watched them work, and shipped something narrow that takes real toil off their plate. - Engineers feel measurably faster. Agent-augmented engineering (Claude Code, Cursor, agent code review, agent QA) is the default workflow, not an experiment. PR cycle time and time-to-first-deploy for new hires move in the right direction. - Documentation is alive. It updates when the code changes. When it's wrong, an agent flags it. When somebody asks a question the docs should have answered, the docs get better. - Adoption is visible. We can see who's using what, where the holdouts are, and what's actually moving the metric. The "I'm bought in" claim gets backed by data. - You're the person other engineers come to when they want to bring AI into a workflow. You've built the foundation that lets them do it themselves. DAY-TO-DAY - Sit with users. You'll spend hours in the workflows of sales, success, ops, finance, and engineering. Not because you have to. Because that's where the problems are. - Ship narrow agents. Tight scope, real users, fast iteration. Whatever combination of agents, integrations, and internal tools the situation calls for. - Operate our internal AI assistant as a product. Triage what's working, fill the gaps, follow up on questions that didn't get good answers, push the loop until quality is consistently high. - Raise the engineering productivity bar. Agent-driven testing, review, and verification as part of the everyday loop. Automated migration tooling that compresses weeks into hours. - Build the patterns and primitives that let other engineers do this kind of work themselves: skills, agent templates, MCP servers, eval harnesses. - Measure adoption honestly. Build the dashboards that tell us who's actually using AI, where, and what the leverage is. Use them to make the next set of bets. - Drive adoption. Some of the work is technical, some is human. You can sit with someone, watch them try a tool, figure out whether the gap is in the workflow or in the tool itself, and close it. WHAT WE'RE LOOKING FOR - Systems thin
This page is generated from the committed OpenOpps static snapshot. Use the source posting or apply link for the employer's current canonical posting state.