Founding Backend Engineer at Neon Health | Torre

Founding Backend Engineer

Emma highlights
This highlight was written by Emma’s AI. Ask Emma to edit it.
Full-time

Legal agreement: Employment

Base compensation
USD170k - 225k/year

+ Equity (up to 0.86% of the company)

+ Health insurance

Non-negotiable
location_on
Hybrid (Brannan Street, San Francisco, CA, USA)
Posted 12 months ago

Responsibilities


Skills Required Technical skills: * Proficiency with Node, Typescript, and Python. * Good understanding of system design concepts, including distributed systems and reliability/performance tradeoffs. * Experience in API design, implementation, and documentation. * Experience using AI coding tools (Cursor, Github Copilot, Claude, etc.). * Experience working with CI/CD systems; good DevOps skills are a nice to have. * Excellent documentation and testing habits. * Proficiency with version control (Git). Soft skills: * 10x mindset – you’ll be among the first engineering hires. * You are a fun human. * Good time management and planning skills. Experience: * 4–7 years of experience (or equivalent) as a software engineer. * We’re leveling this role to Pave’s “P4” level. * Leads project teams, provides direction, and keeps stakeholders informed. * Determines key milestones and provides updates and check-ins to relevant teams and partners. You are able to work with the rest of the team to: * Define priorities. * Suggest good solutions. * Excel at implementation. * Pick up concepts quickly and pattern match on past problems. * Be obsessed with speed and quality, and help embed that quality into the rest of the team. * Be self-directed and capable of organizing and prioritizing your time without supervision. Specific project experience: * Nice if you have worked on distributed architectures in the past, but not a strict requirement. * You must have experience working on projects touching many parts of a large codebase. Personas – Who should apply? * Project lead at a scaling startup: You’ve worked at a scaling startup, leading projects that required you to define requirements, effectively self-direct, set priorities, and touch many areas of a large code base. * Generalist: You don’t need to be an expert in any one area of software engineering, but you do need to have experience across many areas of engineering. You must know enough to be dangerous in many areas (e.g., self-deployed K8s clusters, micro-services, etc.). * Self-directed: You’ve led engineering projects from start to finish. This could be a large open-source project or building a feature in a past role. * Ambitious & effective: We are a team of ambitious builders who are out to win against our competitors. We want to make a big dent in the universe. To do that, we need to sprint to capture the market before us. * Ownership mentality: You want to feel a sense of ownership for your work. You want to have a meaningful chunk of equity because you know that you can make an outsized contribution toward increasing the value of that equity.