Member of Technical Staff, Linux Kernel
Free to start · No card · 5 credits the moment you sign up
Job description
logcat.ai is the AI engineering layer for the operating-system stack. We build agentic systems for Linux and Android devices: we ingest the diagnostic artifacts a device emits (bugreports, logcat, dmesg, modem traces, ramdumps, perfetto, pcap, CAN) and help device makers diagnose, remediate, test, and author features across their OS stack, grounded in their own BSP. Think Datadog and Cursor combined for the OS layer. A VC-backed startup with a small, senior team — you work directly with the founders.
We recently raised a $2.55M pre-seed. The product is scaling and the customer list is growing. The team is still small, so you'll own what you build.
Deepen kernel-level diagnosis and remediation. This is the foundational, cross-substrate seat: the platform's fixes are only as good as its kernel reasoning.
Note: this seat opens later. We're listing it now so the right person can introduce themselves early.
A note on location
Remote, with at least four hours of overlap with Pacific or IST. We don't track hours. We ask for the overlap because a lot of this work is debugging together in real time, and that doesn't work across a twelve-hour gap. If you're in Seattle or Bengaluru, we'd like to meet in person now and then. It isn't a requirement.
The bar
- 10+ years of relevant engineering experience.
- Deep Linux kernel internals.
- Crash and ramdump forensics, live and post-mortem.
- Kernel tracing and profiling: ftrace, perf, eBPF.
- Driver and BSP experience.
- Strong C.
- Proficient in day-to-day work with CLI-based AI coding tools like Claude Code (or an equivalent). It's how the team operates, not a nice-to-have.
What you'll do
- Build ramdump and crash forensics: drgn, vmcoreinfo, ramdump parsing, post-mortem analysis under customer deadlines.
- Reason across scheduler, memory management, and driver internals.
- Ground remediations in kernel source.
Bonus
- Android kernel.
- ARM64 internals.
- Embedded / hardware bringup.
- drgn and crash tooling.
- Upstream contributions (patches accepted on LKML).
- Yocto distro bring-up.
What we offer you
- A front seat as we scale. Customer calls, the roadmap, the pipeline, how the company is actually doing.
- Top-of-market salary and founding equity. You'll own a piece of what you build.
- The AI tools you need. We use AI across writing code, reviewing it, research, ops, and internal tooling. If something would help you work better, we'll get it.
- Early ownership, and full visibility. We move fast, and you'll help decide where.
- Comprehensive medical insurance for you and your family.
- Start-up perks and flexible time off, the kind people actually take.
- A small team that's easy to work with. People here like solving hard problems and helping each other out.
What to expect after you apply
- Screening call with Head of People & Business Operations
- Technical conversation with Co-founder/CEO
- Technical exercise with Co-founder/ Head of Engineering
- Final conversation with Co-founder/CEO
- References, then offer
In your application, tell us what you'd own here, and the hardest thing you've shipped in this domain.
Originally posted on Himalayas
Prepare your application
Use the description above to assess your fit for logcat.ai. This checklist is guidance from Resumize, rather than additional requirements from the employer. Imported listings can be shortened or change after collection, so confirm the complete description and current availability before sending an application.
Match requirements to evidence
Identify the responsibilities and skills the employer explicitly names. For each important requirement, choose one example from your work, education, training, or projects. Explain what you did, how you did it, and what changed as a result. Include a measurable outcome when you can support it. If you lack a requirement, describe related experience accurately instead of adding an unfamiliar skill to your resume.
Put the most relevant examples near the top of your resume. Keep job titles, dates, qualifications, and contact details consistent across your application materials. Use the employer’s terminology when it describes your experience accurately; a copied list of keywords does not explain your contribution. A short, specific bullet is easier to review than a paragraph that mixes several unrelated duties.
Check the working arrangement
Confirm the location, schedule, employment type, and any eligibility requirements on the employer’s site. A remote label does not establish worldwide eligibility or flexible hours. If compensation, benefits, equipment, travel, or contract duration are missing from this listing, write down your questions for the recruiter. Do not assume details from another opening at the same company apply to this role.
Review before submitting
Follow the employer’s requested file format and application instructions. Open your exported resume and check that its text is selectable, its sections read in order, and its links work. Proofread names, dates, and contact information. Share confidential work samples only when you have permission, and use an anonymized example when necessary.
Submit through a trusted employer or recruiting destination. If the original listing has disappeared, search the employer’s careers page for the title rather than assuming the vacancy remains open. Save the application date, job reference, and the version of your resume you sent. Those details help you prepare for a later conversation and avoid submitting conflicting information through several job boards.
Review your resume for writing and readability feedback, or browse other openings if this opportunity is unavailable.