> Markdown version of [/jobs/ext/257159-fullstack-software-engineer-ai-native](https://www.wearedevelopers.com/jobs/ext/257159-fullstack-software-engineer-ai-native). 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). --- # Fullstack Software Engineer (AI-Native) - **Company:** Proton Partners LLC - **Location:** Cambridge, MA, United States - **Experience:** Expert - **Salary:** $150,000.0 - $200,000.0 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Airflow, Software as a Service, Databases, Cursor (Graphical User Interface Elements), Software Debugging, Programming Tools, Eclipse (Software), Python (Programming Language), PostgreSQL, SQL Databases, Systems Integration, SAP Integration Solutions, Large Language Models, Multi-Agent Systems, Indexer, Backend, Vue.js, Epicor ERP, Front End Software Development - **Published:** May 15, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=4e4e983719a34a4e ## About the Role Do you have experience in Vue.js?, * 5+ years as a software engineer with real, demonstrable fullstack delivery - production systems, real users, real ownership. Resume-level hands-on experience, not LLM-generated portfolios. * Strong fundamentals. You understand what the code is doing and why. You can read a stack trace, reason about a query plan, debug a race condition, and tell when an agent is wrong. We are explicitly not hiring "vibe coders" who depend on AI to compensate for missing fundamentals - AI amplifies seniority, it doesn't replace it. * Daily, hands-on use of agentic dev tools. Claude Code, Cursor agent mode, Codex, or equivalent - used to ship real features, not just autocomplete. You can talk concretely about how you structure prompts, manage context, parallelize agents, and verify their output. * Generalist instinct. You're comfortable jumping between Vue, Python, SQL, infra, and integrations. You don't wait for someone else to take the layer you're "not assigned to." * Database and systems chops. You design efficient schemas and queries, understand indexing and tradeoffs, and can reason about distributed-system failure modes. * Startup mindset. Pragmatic, fast, biased to ship, comfortable with ambiguity, close to users. * Strong communication. You can explain technical decisions to PMs, designers, and customers - in writing and in person., * Experience building integrations with distribution ERPs (Epicor Eclipse, P21, or similar) - ingesting orders, products, customers, pricing; reconciling messy real-world data. Bonus if you've done this in a customer-facing or implementation context. * Experience building or integrating with agentic products - MCP servers, tool-using agents, agent frameworks, evals, prompt/context engineering at the system level. * Prior experience at an early-stage SaaS startup. ## Description We're hiring a Senior Fullstack Engineer to ship products end-to-end across our CRM platform for distributors. This is a generalist role: any layer of the stack, any type of work - frontend, backend, data, integrations - wherever the user impact is. You'll work closely with PMs, designers, and other engineers to scope, build, and deploy features that distributors feel directly. Periodically, you'll work directly with customers to support onboarding, troubleshoot integrations, and help distributors get the most out of the platform. You'll be the person who can sit with a customer's IT team, understand how their ERP is configured, and translate that into something Proton can work with. Expect occasional travel to customer sites a few times a year. Two things make this role different from a standard fullstack opening: * You're an AI-native operator, not a code writer. Every engineer at Proton uses Claude Code (and other agentic dev tools) as a first-class collaborator. We expect features to be designed, built, reviewed, tested, and shipped with heavy AI leverage. You should already work this way - guiding agents, structuring context, validating output, and making judgment calls AI can't. * You're a generalist by default. We don't silo engineers into "frontend only" or "backend only." When a feature needs a Vue component, a Python handler, a Postgres migration, an Airflow DAG, and an ERP integration, you're expected to handle all of it - with AI doing the typing and you doing the thinking. ## Related Videos - [Hiring AI Native Talents](https://www.wearedevelopers.com/videos/100268-hiring-ai-native-talents) - [From Messy Queries to Scalable Systems - How Data Engineering actually works](https://www.wearedevelopers.com/videos/100203-from-messy-queries-to-scalable-systems-how-data-engineering-actually-works) - [Lessons learned from building a thriving Vue.js SaaS application](https://www.wearedevelopers.com/videos/1666-lessons-learned-from-building-a-thriving-vue-js-saas-application) - [Developing the Backend with Stefan Lingler, CTO at Shpock](https://www.wearedevelopers.com/videos/100360-developing-the-backend-with-stefan-lingler-cto-at-shpock) - [Postgres in the Age of AI (and Devin)](https://www.wearedevelopers.com/videos/1042-postgres-in-the-age-of-ai-and-devin) - [AI Model Management Life Circles: ML Ops For Generative AI Models From Research to Deployment](https://www.wearedevelopers.com/videos/1152-ai-model-management-life-circles-ml-ops-for-generative-ai-models-from-research-to-deployment) ## 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) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [The Prompt Engineer ✍️](https://www.wearedevelopers.com/magazine/216-the-prompt-engineer) - [Never delegate the understanding](https://www.wearedevelopers.com/magazine/749-never-delegate-the-understanding)