Company Description

Pango is building an agentic operating system for e-commerce logistics, unifying shipping, tracking, returns, and warehouse workflows into one platform powered by AI agents.

We're based in Stockholm and San Francisco and backed by some of the most prominent investors in the world. In less than a year, we've seen massive growth where we can't keep up with the demand and need engineers to bring the product faster to the market.

What you'll be responsible for

Enabling the broader team with primitives, tooling, and shared infrastructure that make the next feature faster to build.

Your Hard Skillset

We're looking for strong engineers, not experts in a particular language or framework.

3+ years of professional software engineering experience.
Comfortable working across the stack—from backend services and frontend applications to databases, message queues, caches, search, and infrastructure.
Experience building products at fast-moving, product-focused startups.
Strong engineering fundamentals. Learning a new language or framework shouldn't be the hard part.
You identify bottlenecks, automate repetitive work, and improve the systems around you—not just the features you're assigned.

Bonus Points

You've taken a product from 0 to 1 and watched real users depend on it.
You've shipped LLM-powered features or agentic workflows to production—not just demos.
You've built internal tools or automation that made other engineers more productive.

We're hiring for engineering ability, curiosity, and judgment—not experience with a particular tech stack.

Engineering Excellence

Our systems have significant cross-system complexity: multiple independent services interacting with each other, each capable of failing in different ways. We're looking for engineers who can design and build systems that actively contain complexity instead of adding to it.

When you design a system, you're not just thinking about the happy path. You're thinking about observability, failure modes, and how someone, possibly you, will debug it at 11 p.m. Metrics and logs are part of the design, not an afterthought.

We expect you to use AI, but not as a substitute for engineering judgment. No vibe coding. You're not generating slop and moving on. You care about the code you ship. You simplify, polish, and iterate until the solution is as simple as it can be. Every line of code should reduce complexity or create value, not just increase the entropy of the codebase.

We also expect a high level of craftsmanship when collaborating with others. You respect your teammates' time. Before opening a pull request, you make sure you understand the problem, the implementation is readable, and the changes are easy to review. Complex work deserves concise, high signal-to-noise documentation that explains the intent, the design, and the trade-offs—not just the implementation.

Engineering excellence isn't just about writing code that works. It's about building systems that are understandable, operable, and maintainable long after they've been deployed.

If, on the other hand, these principles feel unnecessary, overly opinionated, or don't seem worth the effort, this probably isn't the right team for you, and that's okay. We'd rather be explicit about the bar than discover later that we value different ways of building software.

Your soft skillset

Comfortable being uncomfortable, making calls with incomplete data, and changing your mind when the data changes.
Empathetic and curious. You build for the merchant, not for the benchmark.
Highly collaborative across product, engineering, and go-to-market. No lone wolves.
Detail-oriented but pragmatic. You know when accuracy matters and when to ship.
You own your work and welcome the accountability that comes with it.

Growth and levels

We operate on a transparent leveling framework. Each level reflects increasing ownership, impact, and scope, with real jumps in salary and equity. Promotions are based on output, not tenure.

This isn't a comfy engineering role. It's fast, focused, and merchant-obsessed. You will launch fast. You will learn fast. You will own what you ship.

The process

Intro call with the founders (30 minutes).
Technical walkthrough and async take-home task (approximately 60 minutes).
Final round with the team (half day, on-site if possible).

By the end, you'll be wanting access to the stack before your first day, because you'll see exactly what kind of company we're building, and exactly how fast your career can move inside it.

Founding Engineer