> Markdown version of [/jobs/ext/2708980-software-engineer-3](https://www.wearedevelopers.com/jobs/ext/2708980-software-engineer-3). 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 3 - **Company:** The Farmers Dog - **Location:** New York, NY, United States - **Experience:** Expert - **Salary:** $165,000.0 - $180,000.0 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Amazon Web Services, Code Review, Software Debugging, PostgreSQL, Pair Programming, Software Engineering, TypeScript, Technical Debt, Backend, Data Analytics, Graphql, Front End Software Development - **Published:** September 4, 2026 - **Apply:** https://startup.jobs/software-engineer-3-the-farmers-dog-9005810 ## About the Role * You're a strong full-stack engineer with 5+ years of experience building and shipping production software, and you're comfortable working across backend and frontend systems. * You care deeply about quality. You build accurate mental models of how systems work, think critically about the details, and look for opportunities to improve the codebase as you build. * You've gone deep on at least one technology or domain, enough that teammates come to you for help, and you're naturally curious and eager to keep learning. * You're an owner and a proactive self-starter. You can make progress in ambiguous environments, prioritize effectively across competing work, and have the judgment to know when to push through a problem, change your approach, or pull someone else in. * You're resourceful and action-oriented. You find the information you need, surface risks early, and look for practical ways to move complex work forward. * You're a skilled communicator who can absorb complexity and distill it into clear decisions and tradeoffs. You collaborate well across functions, seek out perspectives that challenge your assumptions, and give meaningful, actionable feedback. * You look for ways to improve the systems, tools, and practices around you, and you're comfortable questioning conventions and suggesting better ways of working. * You use good judgment about when new technologies and tools, including AI, can improve the work and when they add unnecessary complexity. * You love dogs. Office Guidelines We are an in-office culture, made of in-office people who thrive on the collaboration and magnetism of working in a shared space. We are seeking individuals who excel in this type of environment, where being present fosters deeper connections and engagement. We ask all team members to be in office 4 - 5 days a week to build a collaborative and invested environment to foster our unique in-person culture we are proud to have. This office policy is subject to change at company discretion. ## Description As a Software Engineer 3 on the Business Logic pod, you'll work on the systems at the core of how The Farmer's Dog operates: subscriptions, pricing, billing, and order generation. Everything depends on these systems, and we're reshaping them for the next phase of growth. You'll design and implement significant features across these systems, making technical decisions that improve them and reduce complexity over time. You'll also develop deep expertise in parts of our technology and become someone your teammates can rely on. You'll partner closely with other engineering pods, Product, Design, Data Analytics, and Lifecycle Comms. We care deeply about building reliable, scalable systems and about working well together, regularly whiteboarding, pair programming, and reviewing architecture with peers who set a high bar. If you want to make an outsized impact on technology, on customers, and on the lives of dogs everywhere, this is the right place for you. One Team: We don't think of ourselves as "Acquisition Marketers", "Engineers", "Data Analysts", or "Product Managers". Beyond denoting skill sets and areas of expertise, we don't think departments matter. We'd rather align ourselves to the goals we're working to achieve and make sure we have necessary subject matter expertise to drive meaningful impact. We strive to orient ourselves around customer problems TOGETHER - getting the right people, with the right context, in the right rooms/Zooms to solve problems holistically. We are skeptical about everything and precious about nothing: Ideas can and should come from anywhere, and we aren't tied to our own. We proactively source input. We talk to our customers and leads regularly and are quick to change course if we know there's a better or more impactful way to solve problems. We consider the customer journey in all of our decisions: We know that no interaction exists in a silo and therefore understand how important every single one is. We ensure our strategy sets prospective and new customers up for success and drives long-term retention. We answer questions and address problems early and proactively. We understand the value of different channels, initiatives, and messages and know how to articulate impact and advocate for prioritization holistically. We Execute For Impact: We don't subscribe to "best practices" or "industry KPIs". We're uninterested in how we compare to "benchmarks"; instead we orient ourselves around being the best we can possibly be. Similarly, we don't subscribe to rigid or classical expectations of roles - i.e. acquisition is hyper-focused on improving customer retention and experience., * Design and ship medium-to-large features end to end. Take defined problems from design through production, making sound technical decisions and following your work through after it ships. * Turn problems into shippable work. Break larger efforts into increments that can ship continuously, weigh in on sequencing and dependencies, and surface blockers and unexpected complexity early. * Improve the systems you work in. Reduce technical debt as you build, design data models and contracts that hold up as we iterate, and make decisions that keep the next change cheap. * Debug systematically and build with quality in mind. Diagnose root causes using the data available to you, and consider reliability, performance, and security in the code you write and review. * Partner across engineering, Product, Design, Data Analytics, and other teams. Bring the right people into the work early, communicate decisions and tradeoffs clearly, and solve problems collaboratively. * Become a go-to person and share what you know. Build deep expertise in a technology or part of the domain, help teammates succeed, and provide meaningful, actionable feedback in code reviews and technical discussions. * Keep learning and challenge how we work. Take initiative to learn new technologies, question processes and practices that are not serving the team, and use tools like AI thoughtfully to improve how you build software. Our stack includes TypeScript, GraphQL, Temporal, Postgres, and AWS. ## Related Videos - [Developing the Backend with Stefan Lingler, CTO at Shpock](https://www.wearedevelopers.com/videos/100360-developing-the-backend-with-stefan-lingler-cto-at-shpock) - [Putting the Graph In GraphQL With The Neo4j GraphQL Library](https://www.wearedevelopers.com/videos/257-putting-the-graph-in-graphql-with-the-neo4j-graphql-library) - [Optimizing Discovery: PostgreSQL's Role in Transforming GetYourGuide's Search](https://www.wearedevelopers.com/videos/1647-optimizing-discovery-postgresql-s-role-in-transforming-getyourguide-s-search) - [Developer Experience in the Age of AI](https://www.wearedevelopers.com/videos/1118-developer-experience-in-the-age-of-ai) - [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) - [Nest.js - TypeScript in the backend can also be clean](https://www.wearedevelopers.com/videos/1033-nest-js-typescript-in-the-backend-can-also-be-clean) ## Related Articles - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [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 150 - The shift to AI generated code, fingerprinting and OKRs vs. doing your job](https://www.wearedevelopers.com/magazine/533-dev-digest-150-the-shift-to-ai-generated-code-fingerprinting-and-okrs-vs-doing-your-job) - [Dev Digest 137 - AI'm not sure about this](https://www.wearedevelopers.com/magazine/485-dev-digest-137-ai-m-not-sure-about-this) - [Dev Digest 118 - not a total recall](https://www.wearedevelopers.com/magazine/452-dev-digest-118-not-a-total-recall)