What are the responsibilities and job description for the Senior Software Engineer position at Xenia?
Who we need
We need engineers who can ship code to production.
We're looking for people to achieve significant business impact via code shipped to production in a low-overhead/high-ownership environment.
Who we don't need
Architects, managers, bikeshedding of in-code abstractions, "backend" or "frontend" engineers, engs who need long ramp-up times, infra engineers, "AI" engineers, ORM users.
Company description
Xenia is a unified frontline operations platform designed to empower managers and deskless workers with modern, user-friendly software. The platform integrates daily task execution, maintenance management, and safety & compliance into a single application. With features such as inspections, work orders, checklists, logs, chats, and reports, Xenia helps standardize and streamline operations across all departments, assets, and locations.
Our engineering philosophy
Xenia Engineering biases for simple, direct, and done over "robust", "extensible", and other heavily-architected solutions.
Our backend is slowly evolving from a JS mess to a single Go binary on a single EC2 instance; we want to spend our engineering cycles on shipping, not architecting, and we let the hardware scale for us.
We are increasingly leaning on sum types, strict data validation at construction time, memory-backed KV-based storage of in-golang data structures.
Consider: how would you design an integration with a 3rd party SaaS?
- If you suggest building services, "engines", adapters, queues, layers, etc., this is the wrong role for you.
- If you start with "let me curl their API", and then you drop that directly into Go's `http.NewRequest("POST", endpoint, bytes.NewReader(body))` and hook that up to one of our stateless worker goroutines, this is the right role for you.
Logistics
This is a full-time hybrid role based in Boston, MA, in-person time at least twice per week (M/W) in our office on Newbury Street, flexing up as needed for critical work periods. Direct reporting up to ex-Stripe CTO and ex-Hubspot founding engineer.
Qualifications
- You ship to production >10 times per day.
- Demos, not memos.
- Consensus is bad.
- You are open to occasional weekend work and on-call periods, especially to support incident response, sales team demos, etc.
- You want in on the ground floor of a Series A startup on an exciting growth curve.
- You feel that your personal technical delivery velocity has been 10x'd through your effective piloting of your agent harness of choice.
- You want to actually solve concrete customer problems, and closely collaborate with our QA, Customer Service, and Product functions.