も⁠し⁠か⁠し⁠て⁠あ⁠な⁠た⁠は未⁠来⁠の⁠.⁠.⁠.  

Software Engineering Internship 2026

Early Careers

Helsinki, Finland

正⁠社⁠員

今⁠す⁠ぐ応⁠募

あ⁠り⁠が⁠とう⁠ご⁠ざ⁠い⁠ま⁠す⁠！

こ⁠の求⁠人⁠に応⁠募⁠す⁠る⁠た⁠め⁠のリ⁠マ⁠イ⁠ン⁠ダ⁠ー⁠を⁠お送⁠り⁠し⁠ま⁠し⁠た⁠。皆⁠様⁠の応⁠募⁠を心⁠よ⁠り⁠お待⁠ち⁠し⁠て⁠お⁠り⁠ま⁠す。⁠

あ⁠り⁠が⁠とう⁠ご⁠ざ⁠い⁠ま⁠す⁠！

あ⁠な⁠た⁠に適⁠し⁠た求⁠人⁠が掲⁠載⁠さ⁠れ⁠た際⁠に通⁠知⁠し⁠ま⁠す⁠。

//images.ctfassets.net/et5i6t44yqqw/6y8HiCCTXczbLsFEe7ZirP/32ae45a4dc66f272bc5eed471f6bc978/rocket-yuho-sideways-cropped.png

About Wolt

At Wolt, we create technology that brings joy, simplicity and earnings to the neighborhoods of the world. In 2014 we started with delivery of restaurant food. Now we’re building the delivery of (almost) everything and you’ll find us in over 500 cities in 30 countries around the world. In 2022 we joined forces with DoorDash and together we keep on dreaming big and expanding across the globe.

Working at Wolt isn’t always easy, but it’s definitely exciting. Here you’ll learn more, build more, and ship more than in most other companies. You’ll be challenged a lot, but also have a lot of fun on the way. So, if you’re a self-starter with drive and entrepreneurial spirit, this could be the ride of your life.

About the program

To build a bigger, better Wolt, we’re looking for Software Engineering Interns to join us for summer 2026 in Helsinki! 🤩

The program will last for up to 6 months and you can start in May.

The internship is paid (3300€/month) and you’ll be assigned to one of our 80+ engineering teams where your existing skills will find their best match in terms of mentorship and tech.

For our internships, we prioritise candidates who are able to continue full-time after the internship, as we see this as a good starting point for a long-term career at Wolt. Many of our current team members across different product teams began their journey with us as interns. Every intern will get their own mentor from the chosen team to work closely with and learn from, so there will be plenty of room for sharing knowledge and growing together.At Wolt we take ownership beyond the obvious, do common things uncommonly well, think big but stay humble, and treat all people equally kind. Curious to learn more? Check out our engineering organisation and learn all about how we build our products in our Product+ Playbook. If this sounds like a place for you, then make sure to keep on reading as we dive deeper into the program below!

Crafting the path

We offer several tracks for you to choose from: Frontend, Backend (Golang or Kotlin), and Mobile (iOS). You can apply to the track that best matches your interests and skills. Each path plays a meaningful role in shaping our products, and no matter which one you choose, you’ll have a real impact by working on production features as a member of your future team.

Together, we will craft the path for your chosen competence by getting a picture of your skills and preferred technologies during the recruitment process. As you start your journey at Wolt, you could find yourself working on a wide range of areas — from consumer-facing applications and courier, merchant, or support services, to logistics, core platform and infrastructure, fintech, or Wolt Market.

Still not sure? Hear more about the Program from the ones who walked the path already, like Jerry and Paula, whose career journey is truly inspiring. 👀

Qualifications

For Frontend development, all our teams use TypeScript and React, which is all you need to get started as a Frontend Intern at Wolt. For Backend development, we’re offering internship opportunities in teams working with Golang or Kotlin this year.  And if Mobile development is your thing,  we offer iOS internship opportunities where you’ll work on real product features.

While our engineering teams use a wide range of technologies, we’re deeply committed to providing the best possible mentorship, which is why we can only accommodate interns with a background in these technologies.

We’re excited to welcome people from diverse backgrounds who bring an open mindset and a genuine desire to build great things together. We hope you’re comfortable asking questions, making mistakes, and sharing your learnings and opinions with others 💙

Above all, we’re looking for growth potential — solid fundamentals in at least one programming language and an understanding of good development practices will give you a strong start.

As we aim to offer long-term career paths, we prioritise candidates who are able to continue with us full-time after the internship.
Ideally, you’re based in Helsinki or nearby, so you can spend a few days a week at the office and work closely with your mentor and team members. Unfortunately, we’re unable to offer relocation or visa support for internships, so you’ll need to be eligible to work in Finland for the duration of the program. If you’re offered a permanent role after the internship, we’ll of course support you with a work visa if needed.

Additional information

👀 The process is easy:

  1. Click “Apply now”, fill in the form and answer the provided questions (NOTE only answer the tech specific questions for the technology you are applying for)
  2. Prepare and add your CV, if you want to tell us more about yourself and your interests in a cover letter, feel free to include it as well.
  3. Send your application!

For the technical interview, please think of a project that you have worked on that would showcase your skills and experience. If you have not worked on something very complex - that’s ok, we’d like to hear more about how you learn and solve challenges even if it is based on the school project.

The deadline is the 1st of February, Sunday (end of day). We’ll review the applications within a few weeks and invite successful candidates for interviews, starting February. If you have any questions, you can let us know via internships@wolt.com. 

Please note that we do not accept applications via email or LinkedIn messages.

FAQ 

  1. How many intern positions are open this year?
    We have several spots for frontend, backend and mobile interns available.
  2. Do I need to be based in Helsinki? Do you offer relocation support?
    We have one of our tech hubs in Helsinki and we would need you to be able to work at least partly from the office with your future internship mentor and other team members. This means commuting to the office every now and then for working together and for events. We don’t offer relocation and visa support for this specific program so you should be already in Finland, ideally in the Capital Region, with a valid work permit.
  3. I can take care of the relocation part myself. Can I still apply?
    Unfortunately, we will not consider your application if this is the case.
  4. How should I prepare for the technical interview?
    If you’re invited to a technical interview, be prepared to walk our engineers through a project that showcases your skills. It doesn’t need to be anything overly complex - a project from university, a bootcamp, or a similar setting is absolutely fine. We’re interested in what you worked on, the challenges you faced, how you approached and solved them, and what you learned along the way.
  5. I want to apply; what happens after I send my application?
    If you are selected for the first round of interviews, you will get an invite for the next step within 3 weeks after the application deadline. We will be in touch with each and every candidate who applied regardless of the outcome. The recruitment process includes the technical interview, and a meeting with your possible team lead and mentor. We are aiming to make the decisions in the beginning of March - we do not have the exact dates as the length of the process depends on the number of applications.
  6. When is the exact deadline for the applications?
    The deadline to apply is 1st of February, Sunday (end of day) 23:59. However, to avoid additional stress during the application period, our advice is to apply ahead of the deadline.
  7. I missed the deadline; can I still apply through email?
    No, unfortunately not. Please make sure to apply through our recruiting system by 1st of February, Sunday (end of day).
  8. I'm a student/ fresh graduate. Can I apply?
    We want to provide long-term career paths so we are looking for candidates who are able to continue with us after the internship full-time. Therefore, we are especially looking for graduated candidates but if you are at the very end of your studies and feel comfortable finishing those while working with us, you are welcome to do so!
  9. I learned coding by myself / I learned coding in a coding school? Can I apply?
    Absolutely! We have many career shifters, who are either self-taught or learned coding in a coding school, landing internships at Wolt.
  10. Can I change my focus at some point and try new things at Wolt in the future?
    Definitely! We are mainly looking for backend, frontend and mobile engineers in this program, as we currently have teams and mentors available for those paths, but we are always open to internal mobility.

  11. Do I need to answer all the tech specific questions when applying?

    No need, please only answer the tech specific questions for the technology you’re applying for.

Our Commitment to Diversity and Inclusion

We’re committed to growing and empowering a more inclusive community within our company, industry, and cities. That’s why we hire and cultivate diverse teams of people from all backgrounds, experiences, and perspectives. We believe that true innovation happens when everyone has room at the table and the tools, resources, and opportunity to excel.

今⁠す⁠ぐ応⁠募

今⁠す⁠ぐ応⁠募

基⁠本⁠情⁠報

Wolt Recruitment Privacy Statement *

Please review the Wolt Recruitment Privacy Statement and acknowledge.

Are you currently based in Finland? *
Are you eligible to work full-time in Finland?  *
Are you able to start your internship sometime in May? *
Are you able to continue full-time after the internship? *

We recommend focusing on one technology only during the application.

Which one of these is the secondary technology you work with (if any)? *
Please link a software engineering project you’re most proud of. *
Please describe why you’re proud of it. 💙 *
What was the most complex thing you had to solve while working on this project? 🧐  *
Go specific question 1: What are some ways to orchestrate goroutines? Let’s say you have two goroutines doing some task simultaneously, what are some ways you could wait for both of them to finish? Walk us through: - which approach you’d choose - why you prefer it over alternatives - any gotchas you’ve encountered - how would you do error handling *

If you're not applying for this technology, please add "-" in this field instead.

Go specific question 2: Once the main goroutine starts a background goroutine, what are some ways to cancel the background task? Walk us through: - a real scenario where you needed cancellation - how you signaled the goroutine to stop - how you verified the goroutine actually exited *

If you're not applying for this technology, please add "-" in this field instead.

Go specific question 3: Let’s say a caller calls a function that returns an error. How would you differentiate between different kinds of errors and take action depending on the type? Walk us through: - the approaches available in Go - which you prefer and why - a real example where this mattered *

If you're not applying for this technology, please add "-" in this field instead.

Go specific question 4: OS threads vs goroutines - what’s the difference? Is goroutine scheduling preemptive or cooperative? Walk us through: - the key differences (memory, creation cost, scheduling) - how the Go scheduler works at a high level - any practical implications you’ve encountered *
Go specific question 5: Tell us about a time you improved test coverage or caught a bug through better test design. Walk us through: - what was undertested or what bug slipped through - how you restructured the tests (table-driven, subtests, mocking, etc.) - what edge cases you added - how this prevented future regressions - how to catch data race *
Kotlin (backend) specific question 1: Tell us about a real bug (or near-bug) you had involving Kotlin coroutines in a backend context (e.g., request handling, background jobs, async IO). Include: - what the bug looked like in production (symptoms/impact) - exact reproduction steps (or how you made it reliable) - what you found and how (logs/metrics/traces/debugging) - what you changed (scope, dispatcher, cancellation, supervisor, timeouts) and why - how you confirmed it was fixed *
Kotlin (backend) specific question 2: You see intermittent latency spikes. The service uses coroutines and also talks to a database. Describe: - what “bad” looks like (p95/p99, timeouts, queueing) - what you’d check first (metrics, thread pools, connection pool, GC) - common causes in Kotlin services (blocking calls on wrong dispatcher, connection pool exhaustion) - concrete changes you’d implement and how you’d validate improvement *
Kotlin (backend) specific question 3: Design an endpoint: POST /orders that can be safely retried by clients. Explain: request/response shape (briefly) - how you ensure idempotency - how you handle validation and error mapping (4xx vs 5xx) - how you’d version or evolve the API without breaking clients *
Kotlin (backend) specific question 4: Tell us about a time a test suite gave you false confidence or became flaky. Include: - what the failure looked like - root cause (timing, shared state, DB, concurrency, external dependencies) - what you changed (test structure, isolation, time control, fakes vs mocks) - how you kept it from coming back *
Kotlin (backend) specific question 5: Describe a bug (or expected bug) involving concurrent requests updating shared data (e.g., double creation, lost updates). Include: - how the race happens - what guarantees you need (exactly-once, at-least-once, uniqueness) - what you’d do at the DB level (constraints, transactions, isolation, upserts) - how you’d test/verify it *
Kotlin (backend) specific question 6: Pick one: (A) JWT-based auth, or (B) session-based auth. Explain: - how you’d validate requests - how you’d implement authorization checks - where secrets/keys live and how rotation works (high level) - one common security pitfall you’d watch for in backend services *
Kotlin (backend) specific question 7: You need to process up to 10 million events/day and produce per-user aggregates (counts + last-seen timestamp). Explain: - which data structure(s) you’d use and why - expected time and space complexity - one scalability bottleneck you anticipate and how you’d address it For simplicity we can assume there’s only one server instance consuming events.  *
Frontend specific question 1: Tell us about an interesting frontend detail you've noticed in any web app or website that most people might ignore. Why did it catch your attention? *
Frontend specific question 2: Walk us through a real bug or a performance issue you investigated in any project (school, hobby, or work). How did you resolve it? *
Frontend specific question 3: What are refs in React? Give an example of when using them would be beneficial. *
Frontend specific question 4: Describe a technical decision you've made in a frontend project where there wasn't an obvious "right" answer. What options did you weigh and is there anything you'd reconsider now? *
Frontend specific question 5: Briefly examine the wolt.com web ordering UI. If you were asked to improve just one small detail of the user experience, what would you change and why? *
iOS specific question 1: Tell us about a real bug caused by misunderstanding the UIViewController lifecycle or screen visibility. Include: - what the bug looked like - the exact steps to reproduce - what you found and how you found it - what lifecycle method(s) you changed and why - how you confirmed it was solved *
iOS specific question 2: Describe a time SwiftUI behaved “weirdly” due to rendering/state updates (e.g., repeated network calls, view model resetting, list cells flashing, navigation issues, animations restarting). Walk us through: - what you saw and what you thought should happen - what triggered the re-render/rebuild - what you modified (state ownership, identity, moving side effects, etc.) - how you confirmed it was fixed *
iOS specific question 3: Tell us about a time your iOS app hit a memory warning or crashed (e.g., EXC_BAD_ACCESS, OOM, or a crash). Walk us through: - what happened and how you triggered it reliably - what signals/tools you used to diagnose it - what actually caused the issue - what you changed and how you confirmed it stayed fixed If you haven’t hit this yet, describe a time you proactively prevented a memory issue and how you validated it. *
iOS specific question 4: Tell us about a performance issue you faced in a long scrolling list (UITableView/UICollectionView or SwiftUI List/Lazy stacks). Describe: - what “bad” looked like - how you measured or confirmed it (even informally) - what was actually slow/expensive - what you changed and what improved If you haven’t built a long list yet, describe a long list you’d build and the pitfalls you’d watch for. *
iOS specific question 5: Tell us about an iOS UI detail most people overlook that you started caring about (safe areas, keyboard behavior, Dynamic Type, VoiceOver, Reduce Motion, localization, etc.). - What made you notice it? - What did you change (or what would you change) to improve the experience? - How did you test/verify the improvement? *

追⁠加⁠情⁠報

Wolt - Self-Identification Survey

To ensure that our hiring practices are fair and inclusive, we’re asking the following voluntary questions of the people who apply to work at Wolt. If you don't feel comfortable answering any question, you can select “I don't want to answer.”

Your responses to these demographic questions are secure and optional. Any voluntary data you provide will not be shared with anyone connected to your recruitment or hiring process. There will be no negative consequences if you don’t want to participate, if you only answer some questions, or if you select “I don’t want to answer” for any question. Any option you choose will in no way affect your opportunity to work at Wolt.

By answering questions below, you give us your consent to process and handle your answers anonymously, and help Wolt understand the diversity of the people it attracts to apply. For additional clarity, our privacy policy below explains how we collect and process your data in accordance with applicable data protection laws.

添⁠付フ⁠ァ⁠イ⁠ル *

職⁠務⁠経⁠歴⁠書⁠と履⁠歴⁠書（⁠英⁠語⁠を必⁠要⁠とす⁠るポ⁠ジ⁠シ⁠ョ⁠ン⁠に応⁠募⁠す⁠る際⁠は英⁠文⁠のR⁠e⁠s⁠u⁠m⁠e⁠）⁠をP⁠D⁠F書⁠式⁠に⁠て⁠ご提⁠出⁠を⁠お願⁠い⁠い⁠た⁠し⁠ま⁠す⁠。