As a Software Engineer at Inkitt, you will play a crucial role in shaping the future of digital publishing. This position is fundamental to the development of innovative technologies that enhance the reading and writing experience for users globally. You will be part of a dynamic team that works on products designed to make literature accessible and engaging, utilizing cutting-edge tools and methodologies to solve complex problems. Your impact extends beyond mere coding; you will collaborate closely with product managers, designers, and other engineers to develop scalable solutions that directly enhance user engagement and satisfaction. The role is exciting because it combines technical expertise with creative problem-solving in a fast-paced environment that values innovation and teamwork. As you contribute to projects that reimagine the publishing industry, you will find satisfaction in knowing that your work significantly influences how stories are shared and experienced.
Initial Screening
reportedAn initial screening with a recruiter to assess your fit for the role.
What to demonstrate
- An initial screening with a recruiter to assess your fit for the role
- Depth in React
How to prepare
- Be able to walk your CV end to end in two minutes, and say why this company specifically.
- Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.
Technical Interviews
reportedMultiple technical interviews to evaluate your technical skills and problem-solving abilities.
What to demonstrate
- Multiple technical interviews to evaluate your technical skills and problem-solving abilities
- Depth in React
How to prepare
- Answer aloud and timed: Describe how you would optimize a slow-running application.
- Answer aloud and timed: How do you approach debugging and troubleshooting in your projects?
Discussions with Hiring Managers
reportedConversations with hiring managers to assess cultural alignment and team fit.
What to demonstrate
- Conversations with hiring managers to assess cultural alignment and team fit
- Depth in React
How to prepare
- Prepare two projects you led end to end, each with the decision you owned and what it cost.
- Have three questions about the team's roadmap and how success is measured in the first six months.
Technical Assessments
reportedEngagement in technical assessments and coding challenges.
What to demonstrate
- Engagement in technical assessments and coding challenges
- Depth in React
How to prepare
- Answer aloud and timed: How would you implement a binary search algorithm?
- Answer aloud and timed: Solve this problem using a given data structure (e.g., arrays, trees).
Behavioral Interviews
reportedInterviews focusing on behavioral aspects to ensure well-rounded candidate evaluation.
What to demonstrate
- Interviews focusing on behavioral aspects to ensure well-rounded candidate evaluation
- Depth in React
How to prepare
- Prepare three examples from your own work, each with a decision you made and an outcome you can quantify.
- Re-read the description of the behavioral interviews above and write down what you would ask to confirm before it.
PracHub editorial advice for the preparation topics above.
Practice Coding
Regularly solve coding problems on platforms like LeetCode or HackerRank. This will help you build confidence in your technical skills.
Research the Company
Understand Inkitt’s products, mission, and recent developments to demonstrate your interest and alignment with their goals during interviews.
Prepare for Behavioral Questions
Reflect on past experiences and be ready to discuss them in detail, focusing on your role, contributions, and outcomes.
Ask Questions
Prepare insightful questions to ask your interviewers. This demonstrates your enthusiasm and helps you gauge if the company is a good fit for you.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Write a function to reverse a linked list.
Write a function to reverse a linked list.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
How would you implement a binary search algorithm?
How would you implement a binary search algorithm?
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Solve this problem using a given data structure (e.g., arrays, trees).
Solve this problem using a given data structure (e.g., arrays, trees).
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Can you optimize this code snippet for performance?
Can you optimize this code snippet for performance?
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Discuss the time and space complexity of your solutions.
Discuss the time and space complexity of your solutions.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Replace offset paging on the resource feed with keyset
resource holds resource_id, tenant_id, owner_user_id, title, body_ref, version, status ('draft','active','archived','deleted'), created_at, updated_at, deleted_at, with an index on (tenant_id, status, updated_at DESC, resource_id DESC). The listing endpoint returns active resources for one tenant, newest update first, 50 per page, today with LIMIT 50 OFFSET n. Tenants reach page 400 and rows are created while they read. Write the keyset query, define what the cursor carries and how it is encoded, and say which part of the index each predicate uses. Assume PostgreSQL 16.
Approach
- Name the two failures separately. OFFSET 20000 makes the server produce and discard 20,000 rows, so page cost grows with depth rather than with page size. Independently, any write that changes how many rows sort above the offset moves the window between two fetches, and the direction decides which anomaly you get: an insert lands at the head of updated_at DESC and pushes already-returned rows down past the boundary, so they are returned a second time; a delete above the offset, or a row whose updated_at is bumped above the cursor, pulls rows up and one is never returned at all. Nothing in the response reveals either.
- Write the seek: WHERE tenant_id = $1 AND status = 'active' AND (updated_at, resource_id) < ($2, $3) ORDER BY updated_at DESC, resource_id DESC LIMIT 50. The row-value comparison is one index range rather than a disjunction, and both columns are NOT NULL, which is what makes that comparison well defined.
- Map each predicate onto the index: tenant_id and status are equality on the leading columns, (updated_at, resource_id) is the range, and the ORDER BY matches the index order so no Sort node appears and the scan stops after 50 rows. The DESC in the definition only matters for mixed directions — a plain ascending btree on the same columns is read backwards for this query.
- Put both sort columns in the cursor and nothing the client can tamper with into another tenant: base64 of (updated_at, resource_id), validated server-side, with tenant_id taken from the principal.
Follow-up
- The client asks for 'jump to page 400'. What do you offer instead, and what does the honest version cost?
- Sort order becomes user-selectable across four columns. How many indexes is that, and which would you refuse to add?
Explain why the owner filter ignores the listing index
The only index on resource is (tenant_id, status, updated_at DESC, resource_id DESC). A new endpoint returns one user's resources across all statuses, newest created first: WHERE tenant_id = $1 AND owner_user_id = $2 ORDER BY created_at DESC LIMIT 20. On a tenant with 2M rows it takes 900 ms and EXPLAIN shows a sort above a large scan. Explain precisely why the existing index cannot serve it, give the index that can, and state which of these the new index still will not help: owner_user_id alone across tenants; the same query ordered by updated_at. PostgreSQL 16.
Approach
- Separate the two jobs an index does. For filtering, a composite btree is seekable only on a left prefix, so with no predicate on status the scan can at best range over tenant_id and test owner_user_id per row; PostgreSQL 16 has no btree skip scan to jump the unconstrained column.
- For ordering, the index is sorted by (status, updated_at) within a tenant and not by created_at, so the LIMIT cannot stop early: every matching row is read and then sorted. That is the 'Sort Method: top-N heapsort' line, and it is why the plan reads 2M rows to answer with 20.
- Derive the replacement from the access path — equality, equality, then the ordering column: CREATE INDEX CONCURRENTLY ON resource (tenant_id, owner_user_id, created_at DESC). The scan seeks to the (tenant, owner) range and walks 20 entries in order, so the Sort node disappears along with the row-read.
- Treat INCLUDE (title, status) as conditional, not free. An index-only scan still visits the heap for any row whose page is not marked all-visible, so on a table taking 1.2k writes/second the win depends on autovacuum keeping the visibility map current, and the wider index costs more on every insert.
Follow-up
- 90% of rows are status='active'. Would a partial index WHERE status = 'active' change your answer, and for which of the three queries?
- A dashboard runs this for 40 owners in one page load. What changes about the design?
Can you explain the architecture of a recent project you worked on?
Can you explain the architecture of a recent project you worked on?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
What are the differences between REST and GraphQL?
What are the differences between REST and GraphQL?
Approach
- Say who the caller is and what they do when the call fails halfway.
- Define the identity of a request so a retry cannot double-apply it.
- Separate accepted, pending, failed and confirmed; they are different facts.
- Design the error taxonomy before the success shape; callers branch on it.
Follow-up
- What happens if the caller retries after a timeout?
- How does a client discover it is on an old version of this contract?
Describe how you would optimize a slow-running application.
Describe how you would optimize a slow-running application.
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
What design patterns are you familiar with, and how have you applied them?
What design patterns are you familiar with, and how have you applied them?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
How would you handle a situation where a project is falling behind schedule?
How would you handle a situation where a project is falling behind schedule?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Given a user scenario, how would you propose a new feature to enhance user experience?
Given a user scenario, how would you propose a new feature to enhance user experience?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
What steps would you take to gather requirements for a new project?
What steps would you take to gather requirements for a new project?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Design a scalable system for a book recommendation engine.
Design a scalable system for a book recommendation engine.
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
How would you structure a microservices architecture for an application?
How would you structure a microservices architecture for an application?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
Discuss the trade-offs between monolithic and distributed systems.
Discuss the trade-offs between monolithic and distributed systems.
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
How do you approach debugging and troubleshooting in your projects?
How do you approach debugging and troubleshooting in your projects?
Approach
- Establish what changed and when, before forming any theory.
- Pick a bisection that eliminates candidates whichever way it turns out.
- Check the instrumentation before believing the symptom.
- Separate the trigger from the cause; the deploy is rarely the bug.
Follow-up
- What would you look at first, and what would it rule out?
- How would you tell a cause from a coincidence here?
Built from the rounds and topics Inkitt candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Inkitt loop
- Write out the reported sequence: Initial Screening, Technical Interviews, Discussions with Hiring Managers, Technical Assessments, Behavioral Interviews.
- For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.
Deliverable: A one-page map of the 5 reported rounds, with the weakest marked.
02Work React
- Spend the session on React, which Inkitt candidates report being tested on.
- Write one worked example in React and time yourself on it.
Deliverable: One timed worked example in React.
03Work JavaScript
- Spend the session on JavaScript, which Inkitt candidates report being tested on.
- Write one worked example in JavaScript and time yourself on it.
Deliverable: One timed worked example in JavaScript.
04Work Frontend Component Development
- Spend the session on Frontend Component Development, which Inkitt candidates report being tested on.
- Write one worked example in Frontend Component Development and time yourself on it.
Deliverable: One timed worked example in Frontend Component Development.
05Answer out loud: Technical / Domain Questions
- Answer aloud, timed: Can you explain the architecture of a recent project you worked on?
- Answer aloud, timed: What are the differences between REST and GraphQL?
Deliverable: Spoken answers to 2 reported Technical / Domain Questions question(s), under time.
06Answer out loud: Coding / Algorithms
- Answer aloud, timed: Write a function to reverse a linked list.
- Answer aloud, timed: How would you implement a binary search algorithm?
Deliverable: Spoken answers to 2 reported Coding / Algorithms question(s), under time.
07Answer out loud: Behavioral / Cultural Fit
- Answer aloud, timed: Describe a challenging project you worked on and how you managed it.
- Answer aloud, timed: Can you give an example of a time you had a conflict with a teammate? How did you resolve it?
Deliverable: Spoken answers to 2 reported Behavioral / Cultural Fit question(s), under time.
Expand any day for tasks and deliverables. Your progress is saved on this device.
Behavioural rounds judge the decision you made and what it cost.
Describe a challenging project you worked on and how you managed it.
Describe a challenging project you worked on and how you managed it.
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Can you give an example of a time you had a conflict with a teammate? How did you resolve it?
Can you give an example of a time you had a conflict with a teammate? How did you resolve it?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
What motivates you to work in the tech industry?
What motivates you to work in the tech industry?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
How do you prioritize tasks when faced with multiple deadlines?
How do you prioritize tasks when faced with multiple deadlines?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Why do you want to work at Inkitt specifically?
Why do you want to work at Inkitt specifically?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
- 01
Describe a challenging project you worked on and how you managed it.
- 02
Can you give an example of a time you had a conflict with a teammate? How did you resolve it?
- 03
What motivates you to work in the tech industry?
- 04
How do you prioritize tasks when faced with multiple deadlines?
How difficult are the interviews, and how much preparation time is typical?
The interviews are generally considered to be of average difficulty, with candidates reporting a mix of technical and behavioral questions. It’s advisable to spend 2-4 weeks preparing, focusing on both coding skills and cultural fit.
Inkitt Software Engineer candidate reports ↗What differentiates successful candidates?
Successful candidates typically demonstrate a strong technical foundation, effective problem-solving skills, and a clear alignment with Inkitt’s values. Communication and collaboration skills are also critical.
Inkitt Software Engineer candidate reports ↗What is the company culture like at Inkitt?
Inkitt promotes a culture of innovation, collaboration, and respect. They value diverse perspectives and encourage open communication among team members.
Inkitt Software Engineer candidate reports ↗What is the typical timeline from the initial screen to an offer?
The interview process usually spans 4-6 weeks, depending on scheduling and team availability. Candidates can expect timely feedback at each stage.
Inkitt Software Engineer candidate reports ↗Are there remote work or hybrid expectations?
Inkitt offers flexible working arrangements, including remote and hybrid options, depending on team needs and individual preferences.
Inkitt Software Engineer candidate reports ↗What should I emphasize in my interviews?
Highlight your technical skills, but also focus on your teamwork abilities, adaptability, and alignment with the company’s values and mission.
Inkitt Software Engineer candidate reports ↗How many interview rounds does Inkitt have for Software Engineer roles?
A typical Inkitt Software Engineer process includes an initial recruiter screening, followed by multiple technical interviews, discussions with hiring managers, technical assessments, and behavioral interviews.
Inkitt Software Engineer candidate reports ↗What does the Inkitt Software Engineer interview process look like step by step?
Expect a recruiter initial screening to assess role fit. After that, you will go through multiple technical interviews and technical assessments, then behavioral interviews, and conversations with hiring managers for cultural alignment and team fit.
Inkitt Software Engineer candidate reports ↗What topics do Inkitt test for Software Engineers?
Interview topics include React and JavaScript, frontend component development, and frontend framework proficiency. You should also be ready for data structures and coding interviews, including a live coding session and technical screening.
Inkitt Software Engineer candidate reports ↗What kinds of questions come up in Inkitt Software Engineer interviews?
You may see design pattern questions, for example “Apply Design Patterns.” There is also a behavior-style question like “Resolving Conflict on a Client Account.”
Inkitt Software Engineer candidate reports ↗What is the compensation for Inkitt Software Engineer roles?
The provided materials for Inkitt Software Engineer do not include any compensation figures. Because there are no base or total pay numbers in the data you shared, you should not rely on a specific salary expectation from this source.
Inkitt Software Engineer candidate reports ↗Sources & methodology 3 sources ↗
No official company page is cited. Rounds and questions come from candidate reports and PracHub editorial material; each source shows the date it was read.
- 01Inkitt Software Engineer candidate reports ↗
Company-reported rounds, questions and FAQ.
Candidate reports · Accessed 2026-09-22 - 02PracHub Software Engineer practice ↗
PracHub practice material, not company-reported.
PracHub page · Accessed 2026-09-22 - 03PracHub preparation framework ↗
PracHub preparation guidance.
PracHub page · Accessed 2026-09-22
Explore related engineering environments and compare the preparation focus.
Vercel Software Engineer Interview Guide
Debugging practice for Vercel software engineer prep built on a reproduction you trust, narrowing to the smallest failing input, and changing one variable per run so the result stays attributable.
Spotify Software Engineer Interview Guide
Timed practice for Spotify software engineer candidates who lose time to the clock: short problems taken end to end, then reviewed against a written rubric rather than a passing test run.
Shopify Software Engineer Interview Guide
Timed practice for Shopify software engineer candidates who lose time to the clock: short problems taken end to end, then reviewed against a written rubric rather than a passing test run.
Ramp Software Engineer Interview Guide
Systems practice for Ramp software engineer candidates, weighted toward payments and lending work: the load that actually arrives, the failure modes that matter there, and the invariants a partial outage must not break.