Principal, Software Engineer

WHY DEPT®? We are a Growth Invention company built to help the world’s most ambitious brands grow faster. Operating at the intersection of technology and marketing, we create what is next by pioneering ideas, acting fast, and moving further because standing still just is not in our DNA. We are drawn to people who stay curious, move with intent, and never stop inventing. Our culture runs on three values: better together, relentlessly curious, and get sh*t done. It is how we work, how we grow, and how we make things that matter. At DEPT®, you will find the freedom to explore, the space to collaborate, and the trust to make a real impact for our clients, for each other, and for the world we are helping to build. What we believe in We build software for the world's most ambitious brands, and we're opinionated about how it gets made: - Code quality is a top priority. Style guides, code reviews, and best practices are how we move fast without breaking things. You'll also get your hands on a wide range of cutting-edge technology. - Great UI/UX is critical. Aesthetics, usability, and speed are all part of the product. A technically correct experience that feels bad isn't finished. - Collaboration wins projects. Great communication is the single strongest predictor of whether a project goes well. - We're pragmatic. We know what to build and what to leave alone, and we make real-world tradeoffs between cost, speed, and craft. Shipping something useful beats architecting something perfect.

- We're intellectually curious. We're constantly learning through craft show & tells, lunch & learns, workshares, and active Slack channels full of talented engineers across the globe. The role As a Principal Engineer, you are the technical anchor for your team. You invent solutions that help ambitious brands grow faster, and you take whole projects from inception to launch with minimal oversight. You're as comfortable in an architecture review as you are in a client workshop. You can explain, in detail, to non-technical users engineering tradeoffs and how to create good software with GenAI tools and help them. The work is primarily backend: distributed services, data platforms, agent and LLM-backed systems, and the integrations that hold them together. You'll own those systems end to end. You'll also need enough command of the modern frontend landscape to make architectural calls that account for it (API shape, latency budgets, rendering strategy) and to hold a credible conversation with the engineers building on top of your work. You're comfortable consulting with and presenting to product managers, engineers, marketing, sales, and finance, and working with all of them to deliver working software. You can read a room, pitch the same system at the right altitude for each audience, and turn a conversation with non-engineers into requirements a team can build against. What you'll do - Lead the architectural design of complex backend and distributed systems end to end, including deployment, monitoring, incident response, and what the team learns afterward. - Take full ownership of your workstreams. Don't get blocked: either find the answer or change the conditions that created the roadblock. - Ensure that on every project, technical scope, requirements, estimates, timelines, and risks are clearly documented, and flag scope gaps, ambiguities, and documentation debt to project leadership before they become budget problems. - Act as a technical consultant to clients: answer their questions across every part of the project, run presentations, demos, and workshops, and distill technical information for audiences from engineers to executives. - Step back and ask whether the work being proposed actually maximizes client value, and say so when it doesn't. - Mentor P1 and P2 engineers through pairing, code review, and design guidance, building a culture of collaboration and knowledge sharing.