Scribe
Backend Engineer
San Francisco (Remote)$140k–$185kfulltimemidAdded today
About this role
Scribe seeks a Backend Engineer to join the Core Engineering Team, building and optimizing backend features for document viewing, editing, and integrations in a Django monolith serving millions of daily users. You'll collaborate with cross-functional teams to ship reliable product experiences while growing your technical skills in a fast-growing, well-funded startup.
What you'll do
- Build and ship backend features in Django monolith for document workflows, viewing, editing, embeds, and exports
- Optimize database queries, endpoints, and caching layers to improve performance and reliability
- Collaborate with product managers, designers, and frontend engineers on feature delivery
- Write automated tests, code reviews, and maintain observability and performance standards
- Work on greenfield projects that expand Scribe's capabilities
- Incorporate team feedback to continuously improve engineering craft
What they're looking for
- Python
- Django
- Backend application development (3+ years)
- Database query optimization and PostgreSQL
- Automated testing
- API design and endpoint performance
- Caching and Redis
- AWS infrastructure
Benefits
- Competitive salary and equity in a unicorn startup
- Comprehensive healthcare benefits
- Flexible PTO and 401(k)
- Parental leave
- WFH stipend and commuter benefits (SF office)
- Collaborative team environment with strong teammates
Opens the official application on the employer’s site. No login required.
Scribe
Scribe builds Workflow AI solutions designed to enhance enterprise operations and revenue processes. The company is hiring AI-focused technical roles, including AI Solutions Engineers and GTM Engineers, to drive customer implementations and optimize sales and success workflows.
View all jobs at ScribeLikely interview questions
- Walk us through a time you optimized a slow database query or endpoint—what was your approach and outcome?
- How do you approach writing tests for backend features, and what testing strategies do you prioritize?