Posted today · be early
Contract Engineer, Automotive
logcat.ai
Canada, India, United StatesremotePosted today
Skill Required
Automotive-EngineerEmbedded-Software-EngineerSystems-EngineerContract-EngineerSoftware-EngineerContract-EngineeringAutomotive-EngineeringEngineeringAUTOSARdebuggingEmbedded CAndroidDatadogLinuxandAIContract
Key highlights
- Required Experience: 10+ years of relevant engineering experience
- Position Type: Scoped, deliverable-based contract with path to full-time Member of Technical Staff
- Work Setting: Remote (at least 4 hours overlap with Pacific or IST)
- Funding: $2.55M pre-seed
Role overview
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. Modern cockpit dumps are dual-OS on one SoC, and nobody diagnoses across that boundary well. You'll change that.
Responsibilities
- Build the automotive substrate adapter.
- Parse and correlate dual-OS cockpit dumps: QNX SLOG2, DLT traces, Android IVI logs, perfetto, pcap, CAN.
- Solve cross-clock-domain correlation across DLT ECU time, QNX monotonic, kernel monotonic, and Android boottime/realtime.
- Build the automotive diagnostic path: UDS, DoIP, DTCs.
Requirements
- 10+ years of relevant engineering experience.
- Automotive embedded experience.
- AUTOSAR (Classic and/or Adaptive).
- CAN / CAN-FD and DBC-level fluency.
- UDS / DoIP diagnostics, SOME/IP, and ECU or domain/zonal architecture.
- DLT, with QNX a strong plus.
- 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.
- At least four hours of overlap with Pacific or IST.
Nice to have
- AAOS or AAOS SDV, including VHAL.
- Hypervisor-based cockpits (QNX Hypervisor).
- Functional safety (ISO 26262) literacy.
- Vector toolchain (CANoe, CANalyzer).
Benefits
- A front seat as we scale: Customer calls, the roadmap, the pipeline, how the company is actually doing.
- 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.
- A small team that's easy to work with. People here like solving hard problems and helping each other out.
Additional details
- Role type: Scoped, deliverable-based contract with a path to a full-time Member of Technical Staff role.
- Location details: Remote. 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.
- What to expect after you apply - Step 1: Screening call with Head of People & Business Operations
- What to expect after you apply - Step 2: Technical conversation with Co-founder/ Head of Engineering
- What to expect after you apply - Step 3: Technical exercise with Co-founder/ Head of Engineering
- What to expect after you apply - Step 4: Final conversation with CEO
- What to expect after you apply - Step 5: References, then offer
- Application prompt: In your application, tell us what you'd own here, and the hardest thing you've shipped in this domain.
- Originally posted on Himalayas
