Junior Software Engineer

The first few years of your engineering career shape how you think for the rest of it. We want juniors who are curious, who pick things up fast, and who take that early learning seriously. You'll join a squad working on real production code from day one, with senior engineers around you whose job includes growing you. AI is reshaping how all of us write software, and you'll learn that on the job, alongside the fundamentals.

This is an IC role with a clear path forward, and we invest in that path.

What you'll do

• Build foundational skills on real production work. Well-defined tasks with senior engineers supervising. The work is small in scope but real, and your code ships and serves customers.
• Learn the craft deliberately. Code review feedback, pairing, documentation, tests. These are the fundamentals that compound, and we protect time for them.
• Use the tools well. Source control, your dev environment, CI, observability, and AI tooling, which we treat as part of the workflow. Try things and bring back what you find.
• Communicate clearly. Tell your team what you're working on, why, how it's going, and where you're stuck. Asking for help is part of the job.
• Improve the docs. Whenever something tripped you up, write the explanation that would have helped. The codebase improves, and so do you.

The shape we're hiring for

For juniors, we hire for shape more than experience.

• Curiosity. You're interested in how systems work, why decisions were made, and what you don't yet understand.
• Learning velocity. You pick things up fast from pairing, code review, docs, AI tools, and conversations. You don't wait for someone to teach you.
• Emerging ownership. You complete what you start, ask when stuck, and take responsibility for your share of the work.
• Clear communication. You say what's going well, what isn't, and what you need.
• Change disposition. You enjoy that the work is changing fast. That's part of the appeal.

You'll be a strong fit if

• You're at the start of your career: an internship, bootcamp, computer science degree, self-taught with a portfolio, or early in your first role.
• You can write code in at least one mainstream language (Python, TypeScript, Java, Go). Not yet expertly, but clearly enough to do the job.
• You've used Git, written tests, and shipped something: a personal project, course work, or an internship.
• You're comfortable using AI tooling in your workflow, and you treat it as a way to learn faster rather than a shortcut to think less.
• You enjoy explaining what you've learned, even imperfectly, because that's how it sticks.

You might be a less good fit if

• You're looking for a place that hands you fully-specified tasks and expects nothing else.
• You'd rather not have feedback on your work, or you find pair programming uncomfortable on principle.
• You'd prefer to work alone with code and not interact much with people.
• You'd rather not use AI tooling, or you treat it as a workaround for learning the fundamentals rather than a way to learn them faster.
• You're looking for a fast track to management. This role is about technical growth.