About the role:
This role is based in our Atlanta office, located at our headquarters near Hartsfield-Jackson Airport. We're intentionally building an in-person engineering team here with a minimum of 3 days per week in the office.
Being close to operations isn't incidental. You'll walk the warehouse floor, watch the systems you write run in real time, and understand what "production impact" actually means. That context makes you a better engineer faster.
What You'll DoYou won't spend your first year writing unit tests in a corner. From early on, you'll:
- Own features end-to-end from API design through UI on a core product domain
- Deploy your own work and monitor it in production
- Write tests that reflect how your code actually fails, not just how it succeeds
- Participate in code review: giving feedback and acting on it
- Build working knowledge of event-driven systems, async workflows, and distributed services
- Work alongside senior engineers and treat that proximity as a development opportunity
What We're Looking ForWe care more about how you think and learn than which languages you've used.
That said, you should bring:- Full-stack fundamentals you can build on both sides of the stack, you're comfortable with a database query, and CSS doesn't scare you
- Working knowledge of at least one backend language
- Git basics and experience working in a shared codebase
- A habit of writing tests because you've seen what happens when you don't
- Comfort using AI coding tools as a productivity multiplier while keeping your own judgment in the driver's seat
You'll stand out if you have:- Anything you've shipped , an internship project, side project, or open source contribution
- Exposure to relational databases beyond what an ORM abstracts away
- Familiarity with what a deployment pipeline does and why it exists
- Experience navigating a codebase you didn't write
What Success Looks Like30 days:You've shipped at least one thing to production. You know how your team operates and you're not waiting to be told what to do next.
90 days:You're owning features from kickoff through deployment with light oversight. Your code review feedback is useful. You've flagged at least one thing in your area that could be better.
6 months:Senior engineers trust your output. You're developing real opinions about the systems you work in - and backing them up.
