Most Developers Build Features. We’re Looking for One Who Builds Systems.

There are plenty of developers who can pick up a ticket, write the code, and push a PR. That’s not what we’re hiring for.

We’re looking for the developer who reads the ticket and immediately starts thinking about the architecture it doesn’t mention. The one who asks: “What happens when this needs to handle 100x the load? What breaks first? What’s the failure mode nobody thought about?”

If your instinct when you see a problem is to reach for the simplest, most elegant solution NOT the most quickest one; keep reading.

Who We Are

Headline is an Amazon advertising agency that runs on data, automation, and systems thinking. We build internal tools, analytics platforms, and AI-powered infrastructure that give our team and our clients an unfair advantage. Our engineering work isn’t a support function; it’s the engine that powers everything we do.

Our stack is modern, our architecture is microservices-based, and we use AI-assisted development tools like Claude Code as a daily part of our workflow. You won’t be maintaining a legacy monolith. You’ll be building products that directly shape how the business operates and grows.

Who You Are

You don’t just write code. You think in code.

When you encounter a problem in your daily life; a slow process, a repetitive task, a broken workflow; your first thought is “I could build something to fix that.” That reflex isn’t something you learned. It’s how you’re wired.

• You’re an architect, not a bricklayer. Before you write a single line of code, you’ve already mapped the system in your head. You think about data flow, failure modes, edge cases, and how today’s shortcut becomes next month’s tech debt. You design first, then build.

• Debugging is your flow state. Where other developers get frustrated, you get curious. A bug isn’t an annoyance; it’s a mystery. You chase it down the stack with the persistence of a detective who won’t close the case until the root cause is found. Not the symptom. The root cause.

• You’re allergic to doing things twice. If you find yourself repeating a task, your brain immediately starts writing the script to automate it. You believe the best developers are productively lazy; you’d rather spend four hours building a tool that saves 20 minutes a day forever than just keep doing the 20-minute task.

• You have strong opinions about code quality and the humility to revise them. You care about clean abstractions, proper naming, meaningful tests, and architecture that communicates intent. But you also know when to ship and when to polish. Pragmatism over perfectionism.

• You own it end to end. “That’s not my responsibility” is not in your vocabulary. From the database schema to the deploy pipeline to the monitoring dashboard; if it’s part of the system, it’s your concern. You don’t throw code over the wall and hope someone else handles the rest.

• You see AI tooling as a force multiplier, not a crutch. You’re already using tools like Claude Code, Copilot, or similar in your workflow; not to avoid thinking, but to think faster. You understand that AI makes good developers great, but doesn’t make bad developers good.

• You build things outside of work because you can’t help it. Side projects, open source contributions, random scripts that automate your life; you don’t write code because you’re paid to. You write code because that’s just what you do. The paycheck is a bonus.

Before You Apply: The Non-Negotiables

We respect your time. If any of the following don’t apply to you, please do not submit an application. You will be rejected. No hard feelings; we just know exactly who we need.

1. Fluent English: Mandatory

You will work alongside a global team and communicate daily with stakeholders across North America and Europe. Code reviews, architecture discussions, async communication in Slack; all in English. If you’re not highly comfortable reading, writing, and discussing technical concepts in English, this role is not a fit.

2. 3–6 Years of Real Full Stack Experience

Not tutorials. Not bootcamp projects. We need someone who has shipped real products used by real users. You’ve dealt with production incidents at 2am, debugged race conditions in async code, and made architectural decisions you later regretted and learned from. That kind of experience can’t be faked.

3. Proficiency in Our Stack: Not Familiarity, Proficiency

React and Next.js on the frontend. FastAPI with Python on the backend. MongoDB for data. Docker and Kubernetes for infrastructure. You need to be productive in this stack from week one; not learning it for the first time. If you’ve only touched these in side projects, we need more than that.

4. Builder’s Mentality Over Employee Mentality

We don’t micromanage. We give you a problem and expect you to own the solution. If you need someone to tell you what to do every morning, you’ll struggle here. If you thrive with autonomy, ambiguity, and the freedom to make real engineering decisions; this is where you belong.

What You’ll Actually Build

You won’t be maintaining someone else’s spaghetti code. You’ll be architecting and building systems that the entire business runs on.

•     Scalable full stack web applications; React/Next.js frontends backed by FastAPI microservices and MongoDB.

•     REST APIs and backend services designed for performance, reliability, and clean separation of concerns.

•     Microservices architecture that scales; containerized with Docker, orchestrated with Kubernetes.

•     Database schemas and queries optimized for real-world data patterns, not textbook examples.

•     Automated testing, CI/CD pipelines, and monitoring that means you sleep well at night.

•     AI-augmented development workflows using tools like Claude Code; not as a novelty, but as a core part of how you ship faster without sacrificing quality.

The Stack

Frontend: React, Next.js

Backend: Python, FastAPI

Database: MongoDB

Infrastructure: Docker, Kubernetes, AWS/GCP

AI Tooling: Claude Code, AI-assisted development workflows

Bonus Points: CI/CD pipelines, event-driven architectures, distributed systems, scalable SaaS design

What’s In It For You

We won’t insult you with ping pong tables and free snacks.

Here’s what actually matters:

• Real ownership. You’ll make architectural decisions that ship to production. No bureaucracy, no committee approvals for every PR.

• A modern stack with no legacy baggage. You’re building new systems, not patching old ones.

• AI-first development culture. We don’t just talk about AI; we use it daily as core tooling. You’ll be at the bleeding edge of how software gets built.

• Fully remote, flexible hours. We care about what you ship, not when you’re online.

• Direct impact. This isn’t a 500-person engineering org where your work disappears into the machine. What you build will be visible, measurable, and meaningful.

• Growth that matches your ambition. We’re building the engineering function from the ground up. Early hires shape the culture, the processes, and the architecture. This is a founding-team opportunity disguised as a job listing.

Still Here? Good. One Last Thing.

We’ve intentionally written this ad to filter. Most developers will read this and move on. That’s by design.

The ones who are still here are the ones who recognized themselves in every paragraph. The builder who can’t stop building. The debugger who can’t leave a mystery unsolved. The architect who thinks about system design in the shower.

If that’s you; don’t just send us a CV. Show us something you’ve built. A repo. A system. A problem you solved that you’re proud of. That tells us more about you than any list of technologies ever will.

Ready to build something that matters?

Apply and show us what you’ve got.