Mathem.

The Challenge

Mathem — Sweden's leading online grocery retailer — had just completed a major migration from a legacy monolith to a microservices architecture. The migration itself went well, but it surfaced a hard truth: the new system required skills their internal team didn't have at the scale needed.

Specifically, they needed:

• 6 senior backend engineers with Go and Kubernetes experience
• 3 data engineers for the new real-time demand forecasting pipeline
• 2 platform engineers for infrastructure automation
• 1 staff-level engineer to lead the logistics domain

The timeline was non-negotiable: the new delivery scheduling and routing platform had to be live before peak season (November 2025). That gave them 3 months to hire, onboard, and get engineers productive.

Their internal HR team estimated 6–9 months to fill these roles through standard recruitment. That wasn't acceptable.

Why They Chose Indpro

Mathem had worked with large offshore consultancies before and found the model frustrating: high overhead, poor cultural fit, and engineers who needed significant hand-holding to match their engineering standards.

What they needed was different: engineers who could work independently in their existing tools and rituals, maintain their code quality bar, and integrate into their Stockholm culture. Not a feature factory — a real extension of their team.

They reached out to Indpro after a recommendation from another Stockholm-based tech company.

What We Did

Week 1–2: Role definition and bench presentation

We worked with Mathem's VP of Engineering to understand not just the technical requirements but the team dynamics, the existing architecture, and the unspoken cultural expectations. What does "senior" mean to Mathem specifically? What oncall obligations would augmented engineers have? What's the PR review culture like?

Week 2–4: Technical interviews and offers

We then matched against our pre-vetted bench of engineers and presented 8 profiles within the first week — 4 for the backend roles and 2 each for data and platform.

All 8 presented candidates completed Mathem's technical interview process. 7 of 8 passed (one dropped out due to a competing offer). Mathem extended offers to 6 immediately, with the remaining spots filled from a second batch within 3 weeks.

Month 2–3: Onboarding and integration

Every Indpro engineer went through Mathem's standard engineering onboarding — same training, same access, same expectations. We facilitated a 2-day onsite in Stockholm for the first cohort, which proved valuable for relationship-building. After that, standard remote collaboration.

By the end of month 2, all 12 engineers were contributing to sprint deliverables. By end of month 3, the logistics domain lead had taken ownership of the routing service roadmap.

The Result

The delivery scheduling platform launched on schedule in November 2025 — one of Mathem's most successful peak seasons in revenue terms, with significantly improved on-time delivery rates.

Key outcomes:

• 12 engineers placed in 3 months (vs. 6–9 months estimated for standard recruitment)
• 7 of 12 engineers extended beyond the initial 6-month engagement
• Zero critical issues attributable to the augmented team in the first quarter post-launch
• 2 engineers took permanent roles with Mathem after 12 months

What Made It Work

Looking back, three factors drove the outcome:

Clear engagement structure: Mathem's engineers knew from day one that augmented engineers were team members, not contractors. Same Jira, same Slack, same expectations. No "them and us" dynamic.

Cultural fit as a first-class concern: We explicitly asked Mathem what kind of engineer culture they had, and screened for that alongside technical skills. Engineers who can self-direct, who ask questions rather than wait for instructions, who give honest PR reviews — these are trainable through culture, not just skills.

Pre-vetted quality: Every Indpro engineer had been technically assessed and reference-checked before we presented them. Mathem didn't spend cycles screening noise.

Mathem's VP of Engineering described the engagement as "the smoothest scaling experience we've had" — high praise from a team that had been through a lot of vendor disappointments.

— Lars Holm, VP Engineering, Mathem

Want to explore how team augmentation could work for your engineering challenges? Book a discovery call.

Frequently Asked Questions

How did Indpro help Mathem scale their engineering team?

Indpro placed 12 engineers across backend, data engineering, and platform infrastructure in 3 months — against a standard recruitment estimate of 6–9 months. The engagement used Indpro's pre-vetted bench, a structured role-definition process, and a 2-day Stockholm onsite to accelerate cultural integration. Seven of the 12 engineers extended beyond the initial 6-month engagement.

How long did the Mathem engagement take?

The initial placement phase ran over 3 months. The first batch of engineers was presented within 1 week of starting the process, technical interviews completed in weeks 2–4, and all 12 engineers contributing to sprint deliverables by end of month 2. The relationship continued beyond the initial scope — 7 engineers extended and 2 took permanent roles after 12 months.

What engineering roles did Indpro place at Mathem?

The 12-person team included 6 senior backend engineers (Go, Kubernetes), 3 data engineers for real-time demand forecasting, 2 platform engineers for infrastructure automation, and 1 staff-level engineer to lead the logistics domain. All roles required senior-level capability with the ability to self-direct within Mathem's existing engineering culture.

For more on how team augmentation works, see our services page or read how Nordic companies typically structure India partnerships.