Senior Backend Engineer

As a Senior Backend Engineer on the Crawler Team, you'll build the systems our Operations team uses to own ticker coverage end-to-end for our clients. That means acquiring the right content at the right time: SEC filings, IR site content, transcripts, and press releases. The bigger job is the platform around it: the workflows, dashboards, and internal APIs that let our analysts act on that content and deliver accurate, timely models to customers. Crawling is a core capability. Tooling for the people doing the work is the point.

Responsibilities:

• Build and extend the Scrapyd-based crawler platform that pulls source documents from SEC, IR sites, and other providers into Daloopa and the ingestion infrastructure that makes those documents useful downstream.
• Design the internal tooling Operations relies on to own their tickers: company management workflows, ingestion tracking, primary report tagging, and the systems that surface what changed and why.
• Partner directly with Operations to turn workflow pain into backend infrastructure. The best changes come from sitting with analysts and watching what slows them down, not from a ticket queue.
• Own reliability, freshness, and signal quality of data flowing into the product, measured by whether Ops can do their job faster and more accurately, not just by pipeline uptime.
• Mentor peers on pragmatic backend work: clean db models, resilient scraping, observable systems, and migrations that don't break production.

Requirements:

• Strong Python backend chops. Django (or equivalent), relational data modeling, async/queued work, and services that hold up under real production load.
• Experience building internal tools for non-engineering power users. You've worked alongside an ops, content, or analyst team and figured out what they actually needed versus what they asked for.
• Hands-on with Scrapy or equivalent crawling frameworks and willing to go deep on the messy parts: auth, JS-rendered pages, rate limits, dedup, retries, and site drift.
• Track record of shipping end-to-end: schema design, migration, backfill, rollout, and monitoring. Not just one slice.
• Product sense. You treat "ticker coverage" as a workflow, not a dataset, and you design tools accordingly.
• Clear writer. PRDs, ADRs, Jira tickets, post-mortems. Your work is legible to the people downstream of it.

Bonus Points for:

• Familiarity with SEC filings (10-K, 10-Q, 8-K, proxies) or the IR content landscape.
• Experience modernizing legacy crawling or scraping systems. Adding observability, reducing flakiness, and retiring black-box components without breaking what depends on them.
• Built or materially shaped internal tooling for an operations or content team at a data company.
• Familiarity with adaptive extraction approaches (LLM-assisted parsing, self-healing scrapers, automated throttling) and clear judgment on when they're worth the complexity.