Principal, Software Engineer

DEPT®•New York, NY

4h•$122,000 - $165,000•Remote

About The Position

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.

Requirements

7+ years writing software used by lots of people in the real world.
3+ years developing in Python, with deep expertise across multiple technical stacks.
Expert-level knowledge of backend architecture, API design, and system design patterns, including microservices and serverless.
Familiarity with agent development, plus working knowledge of LLM concepts and the ability to make sound tradeoffs between cost, relevancy, and speed.
Proven experience using GenAI productivity tools (Gemini CLI, Claude Code, Codex) in real development workflows, and willingness to push the boundaries of what they can do.
Proven experience integrating APIs and other systems in to end-user facing applications.
Excellent understanding of database platforms, both SQL and NoSQL.
A working command of modern web frameworks (Preferably Angular), enough to make architectural decisions that account for the frontend and to guide the engineers building against your services.
Experience with one or more major cloud providers. Google Cloud preferred, AWS and Azure also fine.
Hands-on comfort with Docker: you know how to containerize services cleanly, keep local development environments consistent, and troubleshoot without getting stuck.
Proficiency in version control (git, mercurial), Agile processes, and CI/CD tooling.
A natural problem-solver who takes initiative and drives things forward with minimal guidance, with a track record of "getting sht done" in a fast-paced environment.
Enjoyment of client conversations, and skill at distilling technical information for a variety of roles within a business.
Strong leadership skills and the ability to influence technical and non-technical stakeholders alike.
Commitment to DEPT®'s B Corp values and purpose-driven work.

Nice To Haves

Experience with an agent development framework, especially Google's Agent Development Kit (ADK).
Angular experience.
Prior experience in a digital agency or high-growth environment leading cross-functional teams.
People management experience.
Hands-on experience architecting microservices and distributed systems

Responsibilities

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.
Lead smaller project teams (2 to 5 ICs) as needed, and partner effectively with Project Managers, designers, and other crafts.