Head of Engineering
Job Summary
Join Radiant Softwares as our Head of Engineering and take ownership of day-to-day technical execution across our portfolio of consumer Chrome extensions and web products. This is a hands-on, in-the-code role — not an architecture-from-the-whiteboard position.
You'll manage a small dev team, review PRs daily, ship product improvements, and keep multiple codebases moving forward while the founder focuses on product vision and growth. Our stack is straightforward — Chrome extensions, Python Flask backends, static HTML/CSS/JS frontends — and our codebases share a lot of DNA across products. We need someone who can step in, take ownership of engineering output, and compound product quality over time.
Your Role
You'll own the technical execution layer across all products. That means managing our existing developers, reviewing their code daily, unblocking them, and setting sprint priorities based on weekly syncs with the founder. You'll also be hands-on yourself — building new features, improving existing modules, and handling light frontend work as needed. Over time, you may grow the team beneath you and take on larger builds.
What You'll Do
Review PRs daily from 2 existing developers and provide clear, actionable feedback
Set weekly sprint priorities for the dev team based on syncs with the founder
Manage, unblock, and mentor developers — with the ability to hire, restructure, or scale the team
Build new product features and modules hands-on, particularly where there's no dedicated dev
Maintain and improve static frontend codebases — landing pages, dashboards, paid acquisition funnels
Ensure consistency and quality across shared codebases that power multiple products
Identify and flag technical debt, quick wins, and product improvements proactively
Ideal Candidate
- You've led or managed 2–5 developers on a remote, async team — ideally contractors across time zones
- You review PRs with a sharp eye and care about code quality without being precious about it
- You're comfortable reading and reviewing code that scrapes web pages, manipulates complex DOMs, and automates browser workflows
- You're product-minded — you notice UX issues, broken flows, and rough edges without being told
- You're an AI power user — you use Claude Code, Codex, CodeRabbit, or similar tools daily and can show how they multiply your output
- Experience with LLM APIs, prompt engineering, and building AI-powered features is a strong plus
- You're comfortable context-switching across multiple small products rather than going deep on one massive system
- You thrive in scrappy, fast-moving environments where shipping beats perfection
- You can take a loose product direction and turn it into actionable dev work without needing a detailed spec
Requirements
Experience & Background
3–7 years of hands-on development experience with at least 1–2 years managing other developers. Proven ability to ship across multiple products simultaneously. Startup or small-team experience strongly preferred over large corporate backgrounds.
Technical Skills
Strong in JavaScript (vanilla JS, HTML/CSS — Chrome extension experience is a major plus), Python (Flask), and comfortable with Git-based PR review workflows. Familiarity with Next.js is a bonus for future work but not required on day one.
Web Scraping, DOM Manipulation & Browser Automation
Our Chrome extensions live inside complex third-party web pages — reading DOM structures, injecting content scripts, handling dynamic page changes, and automating browser workflows. You'll be reviewing code that does this daily, so you need to be fluent in it. Experience with tools like Puppeteer, Playwright, or MutationObserver patterns is a strong signal.
LLM APIs & Prompt Optimization (Strong Plus)
Our Python backends power AI-driven homework solvers and content tools. Experience working with LLM APIs (OpenAI, Anthropic, etc.), understanding prompt engineering, token optimization, model selection tradeoffs, and building reliable LLM chains is a significant plus — especially for building new product modules.
Working Style
Detail-oriented, self-directed, and AI-native. You catch the small things — a misaligned element, an edge case in a flow, a shortcut in someone's PR that'll cause problems later. You don't wait to be told what to do. You use AI tools heavily in your daily workflow and can demonstrate how.
First 90 Days
- Full ownership of daily PR reviews and dev direction — founder is out of the code review loop
- Clear understanding of all product codebases and how they relate to each other
- At least one meaningful product improvement shipped hands-on
- Working sprint cadence established with the dev team
- Trust built with existing developers — they come to you first, not the founder
Recruitment Process
Intro Call
Short call with the founder to align on background, working style, and fit.
Technical Task
Review a sample PR from one of our codebases and walk us through your feedback.
Product Exercise
Look at one of our live products and share what you'd improve — we want to see how you think.
Final Interview
Align on expectations, working cadence, and team dynamics.
You Shouldn't Apply If
- You're a pure manager who hasn't written code in the last year — this role requires hands-on work
- You need detailed specs and Jira tickets to know what to do next
- You've only ever worked on one product at one company — multi-product context-switching is the job
- You see code review as a rubber stamp, not a quality gate
- You don't use AI tools in your development workflow
Ready to join?
Send your CV, a brief note on how you use AI in your workflow, and an example of a product improvement you drove.
Apply Now