We are a small, fast-moving engineering team. The systems you will own sit directly inside our revenue pipeline and our customers' daily operations. There is no buffer between your work and the business outcome. We are looking for the person who, when handed a system they have never seen before in a domain they have never worked in, figures it out faster than anyone expects and ships something better than anyone asked for. Someone who does not wait to be unblocked. Someone who finds bureaucracy physically painful and replaces it with output.
The problems you will solve
- Industry integrations. Build API connections with partners and vendors that sit in the critical path of our revenue. You will own the design, the delivery, the edge cases nobody documented, and the 3am alert when something in a third-party system changes without notice. Speed and correctness are both required. Picking one is not acceptable.
- Web portal redesign. Our customer-facing portal needs a full architectural overhaul. You will make the structural decisions, own the performance outcomes, and build something that serves as the foundation for years of future work. You will be judged not just on what you ship but on whether the engineers who come after you can build on top of it.
- Production reliability. You will own the uptime of systems that real customers depend on. When something breaks, you will be in it. Not watching from a distance, not filing a ticket. You will diagnose, fix, explain what happened, and put something in place so it does not happen again.
- IoT hardware integrations. You will connect software systems to physical devices including boom gates and payment terminals. This is the kind of problem that cannot be solved by searching Stack Overflow. It requires deep curiosity, careful debugging across system boundaries, and the willingness to sit with a problem until it gives way.
What we require. Every point. No partial credit.
- 5+ years building and operating production systems with genuine consequences. Not prototypes. Not internal dashboards. Systems where downtime has a cost, where a bad query takes out a database, and where you were the person responsible for fixing it.
- PostgreSQL at the level where you can look at a slow query, understand exactly why it is slow, redesign the schema if necessary, and explain the decision to someone who will have to maintain it in two years.
- AWS in production across ECS, RDS, S3, and CloudWatch. You have made real architecture decisions, understood the cost implications, and built systems that survive unexpected load without requiring a human to intervene.
- Node.js 16+ at depth. You understand concurrency, you have resolved memory pressure in running services, and you write code that performs correctly under load and is understood immediately by other engineers.
- React 18+ with a strong enough sense of user experience that you have pushed back on a design because it would produce a worse outcome for users. You do not just implement what you are handed.
- Docker in real deployment pipelines. You have built and debugged container configurations that run in production, not just on your laptop.
- Jest coverage that you would actually stake a deployment on. Tests that catch real failure modes, not tests that exist to satisfy a coverage metric.
- The ability to enter a large, underdocumented legacy codebase, build a working mental model of it under time pressure, and make targeted changes without introducing regressions.
- Communication precise enough that when you explain a technical problem to a non-engineer, they understand the trade‑off being made and can participate in the decision.
Job Type: Full-time
Pay: From $200,000.00 per year
Work Location: Remote