Senior Backend Engineer Acmecorp builds an AI customer-service platform. We have ~1,200 SMB customers and 18 engineers. This role reports to the Backend Tech Lead and is remote within US/Canada timezones. What you'd actually do: - Work on the ticket-routing service (Python, ~80k LoC, processes ~12M events/day). SPECIFICS NEEDED: what's the team's near-term roadmap for this service — a rewrite, a feature push, scaling work? - Own one or two of: Kafka-based event pipeline, billing integration (Stripe to Lago migration in flight), or notification system. - Code review for 2-3 mid-level engineers. - On-call rotation: 1 week every 6 weeks. Required: - 5+ years of backend experience, ideally with Python and one of Kafka/Pulsar/Redpanda. - Production experience with event-driven architectures. - Comfort with on-call work. Nice to have: - Experience with Lago or other billing platforms. - Distributed-systems debugging at scale (12M+ events/day or equivalent). Compensation: REQUIRED — salary band disclosure. Equity grants per standard L5 schedule. 100% medical premiums covered for employee and dependents. 20 days PTO + 12 federal holidays. 16-week parental leave for primary, 8-week for secondary. Acmecorp is an equal opportunity employer. Apply: jobs@acmecorp.com with resume and a brief note on which of the three areas (ticket routing / event pipeline / notification system) interests you most. --- Changes: - Replaced title: "Senior Backend Engineering Rockstar - Join the Future of Customer Service!" with "Senior Backend Engineer" - Replaced "About Us" with a 2-sentence company snapshot (what it does, customer count, team size, reporting, location) - Folded "About the Role" into the opener (reporting structure + remote policy) - Rewrote "What You'll Do" with specific service names, tech, scope (LoC, events/day), and concrete duties (code review for 2-3 engineers, on-call cadence) - Added a SPECIFICS NEEDED flag for near-term roadmap - Split "What We're Looking For" into required vs nice-to-have, removed "self-motivated team player," "hungry to learn," "not afraid to take ownership" - Rewrote "What We Offer" with real numbers, deleted "free snacks / beer fridge / work-life balance" - Flagged the missing salary band for pay-transparency jurisdictions - Condensed EEO statement to one sentence - Replaced "Apply now!" with a specific instruction and a focusing question Actionability verdict: - Does a candidate know what they'd do, what's required, comp, and setup? Partial - Still missing: salary band (flagged), the team's near-term roadmap on the ticket-routing service (flagged) Word count before to after: 322 to 224 AI/template signal estimate before to after: high to low