Senior Software Engineer - remote

Supply Hound
Posted 3 years ago
We Work Remotely
The Opportunity

We are hiring Sr. Software Engineers to help develop SupplyHound’s ordering and logistics functionality.  This role will work closely with the CEO to interpret what the product needs, consider the tradeoffs of each approach, and then architect the solution.  Joining at this early stage will enable you to have a huge impact on the direction of the codebase as it matures and grows.

The CEO, Jim Margolis, is based out of Mill Valley, but we are a distributed team, welcoming applicants from anywhere within the U.S.

Our stack is Ruby on Rails and Typescript + React.  While it’d be great for candidates to have experience with one or more of these technologies, our priority is hiring smart, curious folks who learn quickly and are down to own complex initiatives from start to finish.  The majority of work on our near term roadmap will lean toward backend work, but our ideal candidate is game to work on either side of the BE/FE divide as needed in these early, scrappy days.

Requirements

- 3+ years of technical experience.
- Experience owning a major feature or functional area.
- Strong communication skills, including written (extra important given the distributed nature of the team).
- The ability to architect reliable, maintainable systems.
- The ability to pragmatically discuss pros and cons of different approaches, amidst shifting priorities.
- Interest in solving user problems, not just technical challenges.
- Thrive working in diverse, collaborative, team environments.

Expected impact at

One month:
- Successfully onboarded to the codebase and shipped a few small features/fixes to production.
- Begun reviewing peers’ pull requests, helping to catch issues with maintainability, reliability, and correctness.
- Become familiar with the details of SupplyHound’s strategy, vision, and roadmap.

Three months:
- Shipped a major feature to production.
- Proactively provide suggestions on how our architecture, tooling, and practices should evolve to handle changing needs.
- Contribute to discussion and decision making regarding the product vision/roadmap.

Six months:
- Have developed domain expertise within a large swath of the application, by shipping and iterating on several major features and a large variety of more minor features and fixes.
- Have taken action on earlier suggestions, making substantial improvements to the fundamental architecture/tooling/practices of the codebase/team.

Twelve months:
- Architect increasingly sophisticated functionality as the product grows, e.g. leveraging voice and/or image recognition ML systems, smoothly integrating with third party tools, etc.