Lead Software Engineer – Full Stack
Posted 48mins ago
Employment Information
Report this job
Job expired or something wrong with this job?
Job Description
Join SignalWire as a technical lead for full-stack engineering. Focus on developer experience and product capabilities in programmable communications and AI.
Responsibilities:
- SignalWire is looking for an experienced full-stack engineer with strong product instincts to join as a technical lead on one of our product teams.
- You'll think holistically about the developer and end-user experience across our APIs, SDKs, AI Agent platform, Call Fabric, SWML, and carry the end-to-end ownership.
- You'll partner with engineering leadership, product, and our developer community to understand emerging capabilities in real-time AI and communications, and translate them into products developers actually want to use.
- We'll look to you to have a product-oriented mindset, own technical quality across the stack (performance, reliability, latency, and developer experience), and carry genuine excitement about what programmable communications and embedded AI make possible.
- The right person for this role moves fluidly across those domains, picks up unfamiliar systems quickly, and optimizes for customer impact.
Requirements:
- Have 6+ years of practical engineering experience with demonstrated ability to operate as a technical leader.
- Are a strong developer with demonstrable technical depth: You've built backend services, worked on frontend interfaces, debugged infrastructure issues, and made meaningful product decisions along the way.
- Leverage experimental data to drive decisions and remain agile enough to pivot based on empirical findings.
- Have a track record of raising the bar around you, whether that's through mentorship, code review, improving tooling, or simply setting a standard that makes the whole team better.
- Take a product-focused approach to engineering: You think about who is using what you build, why they're using it, whether it's actually working for them and what the next iteration of the product will entail.
- Care deeply about the developer experience, such as the pain of bad APIs, poor docs, and confusing error messages enough to be driven to build better.


















