> Markdown version of [/jobs/ext/1780070-software-engineer-backend](https://www.wearedevelopers.com/jobs/ext/1780070-software-engineer-backend). 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 (Backend) - **Company:** VibeIQ Inc. - **Location:** Boston, MA, United States - **Experience:** Experienced - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Amazon Web Services, Amazon S3, Cloud Computing, Software Quality, Code Review, System Configuration, Continuous Integration, Distributed Systems, Amazon DynamoDB, Node.Js, Software Engineering, TypeScript, Datadog, Data Ingestion, AWS Lambda, Backend, Event Driven Architecture, Api Gateway, Amazon Simple Queue Service (SQS), Network Server - **Published:** July 31, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=d73e2fa00a7a87d1 ## About the Role * Roughly 4+ years of backend or full-stack engineering experience, preferably in cloud-based environments (AWS or similar). * Familiarity with modern backend/cloud technologies such as AWS Lambda, API Gateway, DynamoDB, and S3. * Proven ability to architect scalable, maintainable backend systems (ideally using Node.js or TypeScript). * Strong problem-solving skills across distributed systems. You can effectively research problems, weigh approaches, and design complex solutions. * A demonstrated pattern of rapidly ramping in unfamiliar technical domains. * Excellent written communication and collaboration skills across engineering, product, and external stakeholders. * Using agentic coding tools as a core part of how you build and ship software., * Building products integrated with AI agents (MCP servers, agent-driven workflows). * Building tools for other developers, such as internal platforms, CLIs, SDKs, or extension systems. * Exposure to event-driven architectures: DynamoDB streams, SQS/Lambda patterns. * Exposure to observability tooling and practices: OpenTelemetry * Small-team or early-stage experience where scope was broad and ownership was real. ## Description We are seeking a backend engineer to join the Implementation Engine team. We are a small, focused team that owns the systems powering how customers get onboarded and implemented on our platform. The team's surface area is broad: we own the developer ecosystem (CLI, app extensions, event-driven functions), system configuration (data models, permissions, rules), and system understanding (usage analytics, data health). Our first initiative is building new tooling that dramatically reduces the cost and time of implementing a customer through rapid, iterative product engineering. We're a small team with a big scope. What we offer is a close working environment - pairing on real problems, substantive design and code review, and direct exposure to every layer of the system. This role starts in high-velocity product building and grows into core platform ownership. Over time we expect you to be co-owning some of our hardest infrastructure problems, such as multi-tenant event orchestration and highly durable and scalable data ingestion. You'll collaborate closely with product managers, core platform engineers, as well as internal and external stakeholders to help shape a robust and intuitive implementation experience. This is a unique opportunity to work closely with critical functions at the company, and become a meaningful contributor to scaling our business., * Design, build, and ship tooling that make customer implementation faster and cheaper. * Work in tight iteration loops with the Product Manager, taking loosely specified problems from idea to shipped software quickly. * Drive quality, reliability, and scalability improvements across our infrastructure. * Own features end-to-end, from technical design through deployment and monitoring. * Uphold and evolve our software engineering standards, including code quality, testing, CI/CD, and security practices. * Collaborate with teams across VibeIQ to improve our product, architecture, and engineering practices. ## Related Videos - [10 commandments for vibe coding](https://www.wearedevelopers.com/videos/1453-10-commandments-for-vibe-coding) - [Developing the Backend with Stefan Lingler, CTO at Shpock](https://www.wearedevelopers.com/videos/100360-developing-the-backend-with-stefan-lingler-cto-at-shpock) - [Debugging in the Dark](https://www.wearedevelopers.com/videos/1658-debugging-in-the-dark) - [Stop using Node.js like in 2020! What changed and what you can do today with Node.js](https://www.wearedevelopers.com/videos/100011-stop-using-node-js-like-in-2020-what-changed-and-what-you-can-do-today-with-node-js) - [Meet Your New BFF: Backend to Frontend without the Duct Tape](https://www.wearedevelopers.com/videos/682-meet-your-new-bff-backend-to-frontend-without-the-duct-tape) - [Stop Using Node.js Like It’s 2020! - Alfonso Graziano](https://www.wearedevelopers.com/videos/1863-stop-using-node-js-like-it-s-2020-alfonso-graziano) ## Related Articles - [Lessons for Vibe Coders and Developers](https://www.wearedevelopers.com/magazine/614-lessons-for-vibe-coders-and-developers) - [Highest Paying Tech Companies for Developers](https://www.wearedevelopers.com/magazine/220-highest-paying-tech-companies-for-developers) - [Security Basics for Vibe Coders](https://www.wearedevelopers.com/magazine/598-security-basics-for-vibe-coders) - [Dev Digest 193: Vibe Coding Honeymoon, NaN and the End of Interviews](https://www.wearedevelopers.com/magazine/652-dev-digest-193-vibe-coding-honeymoon-nan-and-the-end-of-interviews) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers)