Fullstack Developer

Job Description:

Job Title : Fullstack Engineer 

• Building features across the stack: backend services in Java and Spring Boot, frontend work in React and Next.js.
• Designing and evolving MongoDB schemas as the product grows. We want schemas that age well, not just ones that work today.
• Working spec-first: before writing a feature, you write down what it does, how it behaves at the edges, and what done actually looks like. This is not just documentation after the fact it shapes the implementation.
• Writing REST APIs and consuming them cleanly on the frontend — thinking about the contract from both sides.
• Writing tests as part of the work — unit tests for logic, integration tests at the service boundary, and Cypress for the flows that matter most to users. Testing is not a separate phase; it is part of done.
• Contributing to code reviews and being the kind of reviewer who asks 'how do we know this works' as often as 'is this well structured'.
• On Project Swifty: thinking through service boundaries and data modelling decisions we will have to live with for years.
• Helping maintain visibility across the stack using Grafana and Graphite. When something looks off, you investigate rather than wait for someone else to notice.

MUST HAVE

• 5+ years of software engineering experience in a production environment.
• Genuinely comfortable on both sides of the stack. You have shipped real features in Java/Spring Boot and in React, not just made minor changes to each.
• You understand REST API design and have worked with NoSQL databases. MongoDB experience is a bonus.
• TypeScript experience is a plus. Comfort with Cypress or a comparable E2E tool is genuinely useful — we do not have a separate QA function, so testing falls to the people building the features.
• You ask good questions. When something does not make sense, you say so rather than guessing and moving on.
• Pragmatic about technical debt — you know the difference between something that needs to be fixed now and something that can wait.
• You can read monitoring dashboards and have a sense of what healthy metrics look like.

GOOD TO HAVE

• Next.js experience — routing, SSR, API routes.
• You have contributed to early architecture decisions on a new project.
• Familiarity with Cypress or another end-to-end testing tool.