Senior Full-Stack Engineer

Some Tech; Wiesbaden; Hybrid; EUR 19,000 - 32,000; Full time

Job summary

Some Tech is seeking a frontend engineer who will own features from the architecture call to the production deploy. You will work with Next.js, React, TypeScript and Supabase to ship in slices that survive production with rollback-ready migrations and robust monitoring.

You will read the codebase and data model before kickoff to present a single voice from scope through handover, ensuring client-visible outcomes align with business goals. Remote India engagement with agreed overlap is expected.

Qualifications

• Several years shipping React and TypeScript in production.
• Comfort owning Next.js App Router, server actions or API routes, and the performance story (Core Web Vitals, caching, images).
• Supabase or equivalent Postgres-backed BaaS: RLS, migrations, auth flows you can explain to a non-engineer.
• Written English strong enough to run async decisions: trade-offs, risks, and "here is what I recommend" in one screen.
• Overlap for standing calls, releases, and incidents, agreed in the contract before the work starts.

Responsibilities

• Own features from architecture call to production deploy.
• Read the codebase and data model before kickoff; communicate a single voice from scope through handover.
• Ship in slices that survive production with feature flags and robust rollback plans.
• Own the gap between merged and actually done: monitoring, handover notes, and handling incidents.

Skills

React

TypeScript

Next.js

Supabase

PostgreSQL

Performance

Code review

Tools

Next.js App Router

API Routes

Migrations

Job description

You take a feature from the first call to production. No ticket relay, no mystery owner. If the deploy fails at 6pm, your name is on the rollback plan.

Next.js, React, TypeScript, and Supabase. You own features from the architecture call to the production deploy. We read the codebase before kickoff; you should too.

Read the repo before you pitch the plan.

We expect you to load the codebase, the data model, and the deploy path before you commit to a shape. The client gets one clear voice in the room from scope through handover.

Ship in slices that survive contact with production.

Feature flags, migrations with rollback, staging that matches prod. Speed matters, but "fast and unrecoverable" costs more than a careful week.

Own the gap between merged and actually done.

Monitoring, handover notes, and the awkward call when reality diverges from the brief. The ticket closed is not the outcome. The outcome is the business still running.

Requirements

Signals we actually check.

• 01 Several years shipping React and TypeScript in production.
• 02 Comfort owning Next.js App Router, server actions or API routes, and the performance story (Core Web Vitals, caching, images).
• 03 Supabase or equivalent Postgres-backed BaaS: RLS, migrations, auth flows you can explain to a non-engineer.
• 04 Written English strong enough to run async decisions: trade-offs, risks, and "here is what I recommend" in one screen.
• 05 Overlap for standing calls, releases, and incidents, agreed in the contract before the work starts.

Location

India, remote, with agreed overlap

We hire for fit and delivery track record. You work remote from India.

Most engagements need shared windows for client calls, go-lives, and incidents. We agree a fixed overlap window up front so nobody is guessing whether you will be reachable when production moves.

Wrong fit

Probably not us if this is you.

• You want a backlog groomed for you and a PM to sequence every sprint.
• You prefer hand-off after the build; someone else can own uptime and client tone.
• You need an India-only schedule with zero client-time overlap; most of our work needs shared release and decision windows.

Short paid assessment if we move past the first call. Contracts first. Full process on the careers page .

What's slowing your team down? (required)

We read every brief and reply within one business day.

Not sure where to start? Send the stuck decision, workflow, or page. We will say whether you need a diagnostic call, a tech stack audit, or a different first step.