Sefism is free for learners. We are here to help you grow, one step at a time.Join for free
Sefism.
Logistics & mobilityProduct company

Bolt

Runs a mobility app for ride hailing, food and grocery delivery, car rental and scooter and e-bike sharing.

Not known6 stage process documentedFounded 2013
Headquarters

Tallinn, Estonia

Headcount

1,000 to 5,000

1,000 to 4,999 people
Work model

Not known

Hiring

Not known

Not enough signal to say. Check the careers page directly.
Where to apply

Ask for a referral to Bolt

A referral only means something if the person giving it can actually speak to your work. I will refer you where I know someone on the inside and your profile genuinely fits the role, and I will tell you plainly when I cannot. Either way you get an answer, and a straight one.

  • I read every request. A reply takes a few days, sometimes longer.
  • I will not refer someone for a role their profile does not fit. It wastes your time and costs me the contact.
  • Where I cannot refer you, I will say why, and point you at the way in that does work.
  • Nothing you send here is shared with anyone without you agreeing to it first.

If you found the opening, paste it. It tells me which team you mean.

A Drive, Dropbox or personal-site link is fine. Make sure it opens without a request for access, or I cannot read it.

At least a short paragraph. This is what I would be putting my name behind, so specifics beat adjectives.

Comma separated, up to six. Things you would be happy to be tested on.

How they hire

The code review round is for backend candidates and system design is mainly for backend and platform roles, so frontend and other tracks may see a different mix.

  1. 1

    Recruiter screening

    Official
    Recruiter screen

    A chat about your background, motivations and CV to pick the right interview track (such as Backend, Data or Commerce). No coding is tested here.

  2. 2

    Optional HackerRank task

    Official
    Online test

    Some candidates get a short HackerRank coding challenge covering core coding concepts and problem solving.

  3. 3

    Live coding interview

    Official
    Live coding

    A session with a Bolt engineer on problem solving, clean code and fundamentals such as data structures, algorithms and sometimes security basics.

    data structuresalgorithms
  4. 4

    Code review and refactoring (backend)

    Official
    Technical interview

    You review your own code or a provided sample and improve it, which can include questions on database access patterns or API design.

  5. 5

    System design interview

    Official
    System design

    Mainly for backend and platform roles: design a system or API live and explain your reasoning, trade-offs and priorities.

  6. 6

    Team fit interview

    Official
    Culture fit

    Real examples of handling ambiguity, trade-offs, conflict and collaboration, followed by an offer if it all fits.

What comes up

Recurring themes from candidate accounts, not a question bank. Nobody is served by leaked question lists, least of all you in the interview.

  • Coding and algorithms

    Official

    Sample questions include reversing a linked list and finding the first non-repeating character in a string, with attention to edge cases and complexity.

  • Large-scale system design

    Official

    Examples include a ride-matching system, a multi-channel notification service and real-time surge pricing, focusing on scalability, caching, consistency and operations.

  • Backend fundamentals

    Official

    What happens when a client calls a REST API, and how you would diagnose and speed up a slow SQL query in production.

  • Collaboration and ownership

    Official

    Stories about working across teams and driving ideas to impact, ideally structured with the STAR method.

Worth reading before you apply

From the Sefism resource library, matched to the rounds above.

Course
Grokking Data Structures & Algorithms for Coding Interviews

A foundations course that builds eleven core data structures from the ground up (arrays, matrices, stacks, queues, linked lists, trees and BSTs, hash tables, hash sets, heaps, graphs and tries), then covers sorting, searching, greedy and divide and conquer. Every chapter has practice problems, flashcards and an assessment. It suits students and career switchers whose foundations came from tutorials and who find pattern courses move too fast.

  • Job search
  • DSA
  • CS fundamentals
Design Gurus · Interview Prep · 4 to 6 weeks · Beginner
SubscriptionDetails
Platform
Design Gurus Problem Set

A browsable practice library of coding problems that can be filtered by pattern, data structure, difficulty and company, so you can drill exactly the weakness you found this week. Patterns include two pointers, sliding window, hash maps, stacks, backtracking and greedy algorithms, with company filters for Google, Meta, Microsoft, Amazon, Oracle and LinkedIn. Free to browse, with an in-browser editor and solutions.

  • Job search
  • DSA
Design Gurus · Interview Prep · Ongoing
Course
Advanced System Design Interview, Volume II

The second volume of Grokking the System Design Interview, aimed at senior and staff (L5/L6) design rounds. It works through harder case studies such as a payment system, flash sale, notification service, unique ID generator, Gmail, Reddit, Google Calendar and a code judging system, then goes beneath them with patterns like quorum, write-ahead logs and vector clocks and deep dives into Dynamo, Cassandra, Kafka, Chubby, HDFS, GFS and BigTable.

  • System design
  • Backend
  • Job search
Design Gurus · System Design · About 36 hours · Advanced
SubscriptionDetails
Course
Grokking Database Fundamentals for Tech Interviews

A text-based course on how databases work underneath: storage and page layout, indexing, transactions and ACID, concurrency control, partitioning and sharding, replication and consistency, consensus and leader election, recovery, and the main NoSQL families. It ends with case studies designing the databases behind Quora, TikTok, Airbnb and Snapchat. It suits engineers who want their database choices in system design answers to be defensible rather than hand-waved.

  • System design
  • Databases
  • Backend
  • Job search
Design Gurus · System Design · 2 weeks · Beginner
SubscriptionDetails
Guide
GeeksforGeeks

A very large site of articles on data structures, algorithms and core CS subjects such as operating systems, DBMS, computer networks and OOP, usually with code in several languages, plus practice problems and paid courses. It is handy for revising a university topic or finding a worked example of a specific algorithm. Quality varies because much is community written, so cross-check anything surprising against a textbook or official documentation.

  • DSA
  • CS fundamentals
  • Databases
GeeksforGeeks · Other · Ongoing reference
Roadmap
Sefism CS Core Subjects Roadmap

An eight-stage roadmap through the core CS subjects: how a computer runs a program, OOP and design, operating systems, computer networks, database theory and internals, software engineering and theory, finished with a systems project such as a shell, an HTTP server or a tiny database. It suits CS students and self-taught developers filling the same gaps, and favours understanding shown in working code over memorised answers.

  • DSA
  • CS fundamentals
  • Databases
Sefism · Other · About 216 hours, 22 to 46 weeks · Beginner
Browse the whole library

What it pays

Nothing collected for this company yet, and nothing worth guessing at. A made-up range is worse than no range because people negotiate against it.

Add to the Bolt page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.


Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

Universities they recruit from

No sourced university links yet. A campus drive, a career fair appearance or an internship partnership is what puts a university here.

Add to the Bolt page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.


Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

How to actually get seen

Show impact-driven projects and your backend stack on your CV, and a short note on why Bolt appeals can help. In design rounds, clarify requirements first, think out loud and cover how you would run the system in production.

Sources

Whole profile last checked 2026-09-22.

Interviewed at Bolt? Fill in what changed.

Processes change, rounds get added, tests get replaced. If what you went through was different from what is on this page, tell me and I will update it.

Want me to refer you here?

Send me the role, your CV and a few honest paragraphs on why you fit it. Where I know someone inside and your profile matches, I will make the introduction. Where I cannot, I will tell you why and point you at the route that does work. You get an answer either way.

Ask for a referral to Bolt

A referral only means something if the person giving it can actually speak to your work. I will refer you where I know someone on the inside and your profile genuinely fits the role, and I will tell you plainly when I cannot. Either way you get an answer, and a straight one.

  • I read every request. A reply takes a few days, sometimes longer.
  • I will not refer someone for a role their profile does not fit. It wastes your time and costs me the contact.
  • Where I cannot refer you, I will say why, and point you at the way in that does work.
  • Nothing you send here is shared with anyone without you agreeing to it first.

If you found the opening, paste it. It tells me which team you mean.

A Drive, Dropbox or personal-site link is fine. Make sure it opens without a request for access, or I cannot read it.

At least a short paragraph. This is what I would be putting my name behind, so specifics beat adjectives.

Comma separated, up to six. Things you would be happy to be tested on.

Add to the Bolt page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.


Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

Work with me

Stuck on something specific?

Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.