Full Stack Engineer, On-Prem Systems

Requirements

• What we're looking for
• Genuinely required:
• 3-4 years of full stack engineering experience — you've shipped both backend services and user-facing interfaces to production.
• Strong fundamentals on both ends. On the backend you understand why , not just which framework method to call — transactions, indexing, idempotency, connection pooling. On the frontend you understand how the browser actually works — rendering, state, the network layer — not just one framework's happy path.
• Stack-agnostic ability — we're not hiring for one language or framework. Your competence comes from understanding, so you can be productive in whatever stack the problem calls for, on either side.
• A real sense for UX — you build interfaces for the person using them, not just to satisfy the ticket. You care whether dense, complex data is actually understandable on screen.
• Defensive, failure-aware thinking — you instinctively ask "what happens if this fails halfway, gets called twice, or the network drops?" and design accordingly, from the API down to how the UI handles an error state.
• Systematic debugging. When something breaks — anywhere in the stack — you form a hypothesis, reproduce it, and narrow it down; you don't try random fixes. Critical when you can't google your way out live.
• Self-sufficiency and resourcefulness — you can figure things out from source code, docs, and first principles rather than needing a live internet lifeline.
• Dependency discipline — you're thoughtful about pulling in third-party libraries on both ends, knowing they may need to be vendored, audited, and left un-updated for long stretches offline. (Frontend dependency trees can get heavy fast — you keep that in check.)
• Ownership of data integrity — you treat the database as sacred, and care about migrations, backups, and consistency.
• Comfort with constraints and process — security discipline, careful data handling, and working within an air-gapped environment are part of the job, not obstacles to route around.
• Bonus (nice to have)
• Any of these are a plus — we don't expect all or even most:
• Experience with geospatial/mapping frontends (e.g. Leaflet, OpenLayers, MapLibre, deck.gl) and self-hosted tile serving.