> Markdown version of [/jobs/ext/2727948-software-engineer](https://www.wearedevelopers.com/jobs/ext/2727948-software-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Software Engineer - **Company:** Coalition Inc. - **Location:** United States (Remote available) - **Experience:** Expert - **Salary:** $115,000.0 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, JIRA, Cursor (Graphical User Interface Elements), Python (Programming Language), Operational Databases, Salesforce.Com, Software Engineering, SQL Databases, Large Language Models, Snowflake, Core Api, Git, Zendesk - **Published:** September 5, 2026 - **Apply:** https://startup.jobs/software-engineer-ai-automation-coalition-9921797 ## About the Role * AI application building (primary): Substantial hands-on experience shipping LLM-backed applications: prompting, tool use, agentic loops, and multi-step workflows. You know where these break and how to contain the damage when they do. You have shipped at least one agent that non-engineers depend on. * Agent tooling: Practical experience with MCP, skill or tool authoring, and orchestrating agents against real systems of record. * Evals: You have built eval sets and used them to make decisions, not just to make a slide look good. * Coding agents: Fluent with agentic coding tools like Cursor. You use them to move faster inside codebases you did not write. * Core development: Strong Python. Comfortable with SQL and working directly against production data models. * Business fluency: You can sit with a non-technical operator, map their process, and translate it into requirements without a PM in the room. * Comfort with ambiguity: Undocumented processes, half-broken internal tools, and unclear ownership are the normal starting conditions. You find the thread and pull it. * Shipping discipline: Git, CI, containers, and enough operational instinct to deploy your own work and keep it healthy. * Experience: At least 5+ years of hands-on software development experience. It's not the years, it's the miles., * Experience building or maintaining MCP servers. * Prior solutions engineering, professional services, internal tools, or startup founding experience. * Working knowledge of the systems we automate against: Linear, Jira, Zendesk, Salesforce, Snowflake. * Insurance, fintech, or another regulated domain where being wrong has a compliance cost. ## Description We are hiring a Software Engineer for the Automation team to use AI to solve and automate manual work across Coalition. This is a hands-on AI engineering role: authoring skills, wiring agents to our systems of record through MCP, building evals, and deploying agents that non-engineers depend on every day. You will not be starting from zero. We have early workflows live in production, more proofs of concept in the oven, and working hypotheses about how all of this should fit together. We want someone who will pressure test those hypotheses against their own experience and change our minds where we have it wrong. Deep, current, practical experience building with LLMs is the single most important qualification for this job. The other half of the role is proximity to the business. Think of this as a Forward Deployed Engineer, pointed inward: your customers are other Coalition teams. You will work directly with the teams whose work we are automating, learn how they actually operate, and turn that into a playbook. Getting from that conversation to something an agent can run reliably is the core of the work. You will also work day to day with our data team to get at the data these agents depend on. This is an individual contributor role with no direct reports. Responsibilities * Author skills: Turn a team's process, judgment, and edge cases into reusable skills that agents can invoke. Write them so the next project can reuse them instead of rebuilding them. * Build within our agent architecture: Wire agents to the systems of record through MCP servers, compose skills and tools into working workflows, and add new MCP surface area when a system we need is not covered yet. * Build evals: Define what "correct" means with the business team before you build. Build the eval set, establish a baseline, and use it to make calls about what ships. Nothing goes live on vibes. * Deploy and support agents: Take agents from prototype to production, including permissions, human-in-the-loop checkpoints, audit trails, and rollback. Tune from how they behave once real users are in front of them, and leave behind docs and an owner on the business team who can run it without you. * Partner with the data team: Work with our data engineers on the access, models, and quality of the data your agents read and write. Bring them requirements early rather than working around them., Coalition is committed to protecting your privacy and handling your personal information responsibly. We collect, use, and store personal information as necessary for the recruitment process and in compliance with applicable privacy laws and regulations in all regions where we operate. We want you to understand what personal information we collect, how we use it, and your rights regarding access, correction, and deletion of your data where applicable. Information submitted, collected, and processed as part of your application is subject to Coalition's Privacy Policy. For further details, please review our full Privacy Policy or contact us with any questions regarding how your information is handled. ## Related Videos - [The AI Agent Path to Prod: Building for Reliability](https://www.wearedevelopers.com/videos/1523-the-ai-agent-path-to-prod-building-for-reliability) - [Improving quality with Agentic AI with Rovo Dev and Xray](https://www.wearedevelopers.com/videos/2005-improving-quality-with-agentic-ai-with-rovo-dev-and-xray) - [How a Small Team Shrank a Microsoft Monorepo by 94%](https://www.wearedevelopers.com/videos/1236-how-a-small-team-shrank-a-microsoft-monorepo-by-94) - [Agentic employees in world's most downloaded FinTech app](https://www.wearedevelopers.com/videos/100123-agentic-employees-in-world-s-most-downloaded-fintech-app) - [Building a Multi-Agent Orchestration Engine That Actually Follows the Rules](https://www.wearedevelopers.com/videos/100159-building-a-multi-agent-orchestration-engine-that-actually-follows-the-rules) - [Collaboration Quantified: Lessons from Open Source Developer Networks](https://www.wearedevelopers.com/videos/1422-collaboration-quantified-lessons-from-open-source-developer-networks) ## Related Articles - [What is Agentic Programming and Why Should Developers Care?](https://www.wearedevelopers.com/magazine/625-what-is-agentic-programming-and-why-should-developers-care) - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [How to Become an AI Engineer](https://www.wearedevelopers.com/magazine/331-how-to-become-an-ai-engineer) - [Highest Paying Tech Companies for Developers](https://www.wearedevelopers.com/magazine/220-highest-paying-tech-companies-for-developers) - [Dev Digest 137 - AI'm not sure about this](https://www.wearedevelopers.com/magazine/485-dev-digest-137-ai-m-not-sure-about-this)