Get a reply from this employer
Your resume and cover letter, tailored to exactly what they’re hiring for.
My Crash Report is seeking a senior engineer to take full ownership of the technology stack, from Next.js frontend to Postgres database and the data pipeline. You will optimize performance, implement SEO infrastructure, and own lead capture, delivery, and tracking across paid media.
You will work directly with the founder and media buyers, shipping high-impact changes weekly. This is a remote role, with international reach and a focus on revenue-driven engineering.
My Crash Report publishes public car-crash records so people involved in an accident can find their report, understand what happened, and get connected to a vetted attorney. The site is live at mycrashreport.org with 4.2 million crash records from 11 state and city sources, refreshed nightly, running on AWS. It makes money by delivering qualified injury leads to law firms in Texas, California and Virginia, with more states coming.
We are a small, profitable lead-generation company with a media buying team already running Google and Meta campaigns. The founder set the vision and built the first version of the platform with AI coding tools. You will be the first and only engineer. You take over the codebase, the data pipeline, the infrastructure and the design, and you own them end to end. No product manager, no committee: you talk directly to the founder and the media buyers, decide how to build it, and ship.
This is a builder's role in a business where every page you ship, every second of load time you shave, and every tracking bug you fix shows up in revenue within weeks. If you want to see the direct effect of your engineering on a real business, and you are tired of being one of forty developers moving tickets, this is for you.
In priority order. The first four are where you spend most of your time.
1. The website. Next.js 15, React 19, TypeScript, Tailwind 4, Postgres via postgres.js, MapLibre maps. Millions of crash, location and attorney pages rendered from the database. You own performance, caching, uptime and every pixel.
2. SEO infrastructure. Sitemaps for millions of URLs, crawl budget and indexation, internal linking, schema.org structured data, Core Web Vitals, Search Console monitoring, and the page templates that decide whether we rank for "car accident [city] [date]" queries or not.
3. Lead capture and delivery. The lead form, validation, consent capture, signed webhooks into the CRM, delivery monitoring and retries. If a lead is lost or delayed, we lose money that night.
4. Paid media tracking and landing pages. Google Tag Manager, GA4, Google Ads enhanced and offline conversions, Meta Conversions API, call tracking, and the landing pages and A/B tests the media buying team asks for every week.
5. Design. We have no designer. You design the site, the landing pages and the lead flow yourself, and make them look and convert better than the competition.
6. Crash-data pipeline. Python 3.12, Postgres 16 with PostGIS, a CLI with adapters for 11 state and city data sources (Socrata, ArcGIS, state DOT downloads). You keep the nightly refresh healthy, fix sources when they change, and add new states.
7. Infrastructure. AWS ECS, RDS Postgres, CloudFront, Route 53, S3, GitHub Actions deploys. Backups, monitoring, cost control, and you are the on‑call.
8. Compliance implementation. Our attorney writes the rules (state bar advertising disclosures, consent language, data‑handling requirements). You implement them exactly and keep an audit trail.
Apply only if all of these are true. We check each one in the screening exercise and the interview.
With the founder. A 30‑minute call every morning. He brings the vision and the business priorities; you bring the plan, the trade‑offs and the shipped work. You will disagree with him sometimes, and he wants you to say so with reasons.
With the media buying team. They run Google Search and Meta campaigns and they live or die on tracking and landing pages. Expect a weekly planning session where you agree on the landing page tests and tracking changes for the week, a tracking QA pass before every new campaign goes live, and a feedback loop where lead quality in the CRM drives changes to the pages. They should never have to wonder whether a conversion fired. You build them dashboards so they stop asking.
With the attorney. He sends you compliance requirements in plain English. You implement them exactly, confirm back what changed, and keep a record.
With AI tools. You are expected to use them every day and to review everything they produce. The codebase and runbooks were written this way and are thorough; your job is to own them, not to rewrite them for comfort.
Alone. Most of your week is heads‑down building. You decide the architecture, the tooling and the order of work inside the priorities the founder sets.
By day 90 the founder should be able to go a week without opening a terminal, and the media team should trust every number in their dashboards.