I applied through a recruiter. The process took 1 week. I interviewed at autarc (Berlin) in Sep 2025
Interview
They gave me a 2-hour take-home to build a Next.js + Tailwind comment system with CRUD, nesting, persistence in IndexedDB (not localStorage), and optional cross-tab sync via BroadcastChannel. In short: display, add, delete, support replies, and keep it stored across refresh.
The challenge itself was trivial. It boils down to representing comments as a tree, and the key design decision is whether to model them as a nested tree structure or as a flat list with parent references. I chose the latter, which is the industry best practice used by Reddit, Hacker News, GitHub Discussions, and many others, precisely because it makes CRUD operations simpler and more performant.
Despite this, Autarc did not invite me to an interview or even provide proper feedback on my solution. Instead, they dismissed me with a vague remark about "database design," which I can only assume referred to the data structure choice. Since that was the entire point of the exercise, their response shows a lack of understanding of their own testing criteria.
If a company cannot recognize that the flat list model is the pragmatic and scalable way to approach this problem, then it suggests they are inept in evaluating technical trade-offs. My impression from the interviews also matched this: bright people, but lacking pragmatism, too quick to fall in love with reinventing the wheel, and too eager to chase shiny projects with fancy tech rather than building things that actually work.
Interview questions [1]
Question 1
Build a simple comment system in react with Tailwind CSS for styling and IndexedDB for persistence (not localStorage). The app should:
Display a list of comments
Add new comments via a text input
Delete comments
Support nested replies (comment on comments)
Persist comments so they survive refresh/restart
Bonus: Implement cross-tab synchronization using the BroadcastChannel API so changes appear across open tabs without refreshing
Data model:
Each comment has id, text, optional parentId, createdAt, and updatedAt.
Goal:
Deliver a clean, functional, and maintainable implementation within ~2 hours.
I applied online. The process took 2 weeks. I interviewed at autarc (Berlin) in May 2025
Interview
The interview process at Autarc was smooth, friendly, and well-structured. It consisted of four main steps: a screening call with the recruiter (Louis), a cultural fit interview with the CTO (Marius), a take-home assignment, and finally, an in-office meeting where we reviewed the solution and discussed the product in more depth. Everyone I spoke to was kind, open, and genuinely enthusiastic about their work and the company mission. The communication was clear and professional throughout the whole process.
Although I ultimately declined the offer due to personal circumstances, I left with a very positive impression of the team and the company.
Interview questions [1]
Question 1
- How do you manage conflicts in a Local-first software system?
- What frameworks or tools can help developers build Local-first apps?
- How do you debug and test Local-first features like offline sync or conflict resolution?
- etc.