Must-haves
- Extensive full stack experience with TypeScript/React and Python, with a track record of architectural decisions at scale
- Strong algorithmic problem-solving skills with understanding of complexity analysis, graph/tree data structures, and computational efficiency
- Ability to drive technical direction and follow through on architectural decisions across the stack
- Experience identifying technical debt, evaluating tradeoffs, and building consensus around solutions
- Self-directed work style with strong product sense and ability to unblock yourself and others
- Experience gathering requirements from stakeholders and translating them into technical solutions and system designs
- Track record of owning large, complex features from planning through production
- Ability to mentor and raise technical standards across a team through code reviews and establishing best practices
- Comfortable working with ambiguity in a startup environment
Who You Are
You're a veteran software engineer who's worked across multiple environments and knows that early-stage startups offer the best combination of impact and interesting problems to solve.
You have a nose for bottlenecks—you spot where things are getting stuck and jump in to help get features across the finish line. You're naturally curious about architecture, always tinkering to find proactive improvements that can ship quickly. You move fluidly across the codebase and the team, bringing speed without sacrificing quality.
Your algorithmic problem-solving is strong and you don't shy away from maths and logic. You're comfortable reasoning about complexity at various levels of abstraction, working with graph and tree structures, and finding elegant solutions to hard computational problems.
You're responsible with your craft. You plan, you test, you own large features end-to-end. You think about staging, reliability, and production-readiness from the start, not as an afterthought.
At a principal level, you're also a multiplier. You make the engineers around you better through thoughtful code reviews, clear technical communication, and by establishing patterns that scale beyond your own code. You know when to dive deep into implementation and when to step back and focus on architecture and direction.
You thrive when given ownership of a problem space. You're the person who asks "why are we building this?" before diving into "how should we build it?" You don't need your hand held, but you're not afraid to raise your hand when you need context or when you spot a problem with the plan.
Why JITX?
- Work on genuinely novel problems at the intersection of software and hardware
- Small team where your work has immediate, visible impact
- Help shape the future of how hardware gets designed
- Collaborate with a team that cares deeply about craft and elegant solutions