Senior Software Engineer

Some software roles give you a backlog, but this one gives you real ownership.

We’re partnering with a growing technology company building sophisticated systems that have to perform reliably in demanding real-world environments.

The engineering team is intentionally small and highly technical. Senior engineers here aren’t limited to narrowly defined tickets or one isolated piece of the stack. They’re expected to understand the system, challenge assumptions, influence architecture, and become the technical owner of meaningful parts of what gets built.

If you want your fingerprints on the architecture, not just the implementation, this is worth a conversation.

What You’ll Do

• Own software from concept through production , including architecture, development, testing, deployment, and continuous improvement.
• Build complex production systems where performance, reliability, and sound engineering decisions matter.
• Design scalable backend and data infrastructure capable of efficiently processing and managing significant volumes of information.
• Work across engineering disciplines to solve technical problems that extend beyond traditional application development.
• Own meaningful portions of the architecture , identifying bottlenecks, making design decisions, and helping determine how the system evolves.

What We’re Looking For

• 4+ years of software engineering experience building complex, production-grade systems.
• Strong fundamentals in algorithms, data structures, software design, and systems architecture .
• Professional experience developing software with C++ and/or Rust .
• Experience building backend, systems-level, distributed, or data-intensive software .
• Strong technical judgment, curiosity, and an ownership mentality with the ability to operate effectively on a small, high-performing engineering team.

Why This Role Is Different

You won’t be joining an organization where every major technical decision has already been made.

You’ll work closely with highly technical leadership and engineers who are still deeply involved in how the technology gets built.

As you develop context, you’ll move beyond contributing code and become the person trusted to make technical decisions, shape the architecture, and build the solution.

Interview Process

No seven-round interview marathon.

You’ll have an initial technical conversation followed by an opportunity to meet the team, learn what they’re building, and dig much deeper into the engineering challenges.

The goal is simple: move quickly, respect your time, and give both sides enough information to make a confident decision.

Interested?

You don’t need to come from one specific industry or have followed one specific career path.

What matters is whether you can demonstrate strong fundamentals, technical depth, sound judgment, and the ability to take ownership of difficult software problems.

If you want to build sophisticated systems, work alongside highly technical people, and have meaningful influence over what gets built, we should talk.