Our team
The architect who designed GritDB and the founding members still write engine code themselves, and they meet customers in person. Whether it is engine development or a customer project, we write things down before we start.
How we work
These are the four principles Datagrit works by. We also use them in interviews when we ask about your past experience.
Hardcore and Kind
We are strict about the work and kind to people. Hardcore does not mean working long hours. It means we do not lower the standard of our work. Criticism goes to the work, never to the person.
In reviews, we point out problems clearly and work out how to fix them together.
Grit
We do not let go of a hard problem until we find the cause. When we get stuck, we change the approach and keep the goal.
Even when a problem takes weeks, we rule out possibilities one by one and see it through.
Deep Work
We focus deeply on one problem at a time. We read the original sources ourselves instead of summaries, and we check what we understand with experiments and numbers.
Even when we use a single number, we check the source and the conditions behind it ourselves.
Contribution
We judge the value of our work by what it leaves for the product, our colleagues and our customers. We are clear about which work is ours and which is a colleague's.
When we finish a piece of work, we leave a record so the next person can pick it up right away.
Open positions
When we open positions for forward deployed engineers (FDE) and sales, we will post them on this page.
GritDB engine research engineer (junior)
At least 3 years of experience · Closes 2026-11-14 · 128 Beobwon-ro, Songpa-gu, Seoul (SKV1, Munjeong Station)
What you will do
- Research and implement assigned features of the GritDB engine and ship them in the product
- For each bug, write a reproduction test first, document the root cause, then fix it
- Add end-to-end and unit tests, and solve problems that benchmarks such as TPC-H reveal
Show who we are looking for · nice to have · hiring processHide
Who we are looking for
- You have developed or done research in C++ or C for 3 years or more (systems research in a master's or PhD program counts)
- You have solid fundamentals in operating systems, concurrency, data structures and algorithms
- You have debugged multithreaded code with tools such as gdb and perf
- You design experiments and write up the results
Nice to have
- Experience contributing patches or reviews to the engine internals of an open-source RDBMS such as PostgreSQL
- Experience researching or developing engine internals of a commercial RDBMS, such as storage, execution, transactions and recovery
Hiring process
- Application: a resume and the story of the problem you worked on the longest
- Interview: two 45-minute one-on-one sessions at a whiteboard
- Assignment: a 48-hour C++ project (we choose the topic from an area where your experience overlaps with GritDB)
- Conversation: one-on-one with the founder
- Offer discussion
Pay and benefits
- Salary is negotiated based on your experience and skills
- We provide Korea's four major social insurance programs, lunch, equipment with the specs you want, and books
- Workplace: 128 Beobwon-ro, Songpa-gu, Seoul (SKV1, Munjeong Station)
- The hiring process differs by position, but every process includes a direct conversation with the founder and finishes within 2 weeks
How to apply
Apply through the Wanted posting (in Korean), or use our application page. You can also email your resume to careers@datagrit.co. Instead of a resume, the story of one piece of work you did yourself is fine too. Please leave out anything you cannot share, such as customer names or amounts.
Personal information in applications
- What we collect
- Name · contact details · your resume and anything else you send
- What we do not ask for
- Resident registration number · photo · height · weight · marital status · family information
- Use
- Only for the hiring process
- Legal basis
- Processed to enter into an employment contract (Article 15(1)(4) of the Personal Information Protection Act of Korea)
- Retention
- We keep it for 180 days from the day the hiring process ends, then destroy it
Details are in our privacy policy.
