发布于 2026年11月17日 · 我们于 2026年11月17日 确认该职位仍然有效
这是您的公司吗?US$ 25 – US$ 50 (每个项目)
Aphrodite is a dating platform only for students of the our pilot university. It deliberately does the opposite of Tinder, Bumble and Hinge: 1) no swiping and no endless catalogue. Students get a few curated matches ("drops") twice a week. 2) Skip-to-offline: When two students are both interested, the app offers 3 date slots at partner venues on or near campus. One shared choice books the date. 3) Desired Metric: time-to-offline, not screen time. What you will build (MVP scope) 1. Sign-up restricted to campus identity provider: only university addresses, with email verification. 2. Profile card (signals over photos): name, age (16–99), study program (fixed catalogue of ~29 Bachelor, Master and PhD programs), gender, interested in, "Looking for", 3–5 values and 3–10 interests from fixed lists, career aspirations (max 500 characters). Guided onboarding wizard plus an edit screen. 3. Matching drop: an algorithm scores pairs on study program and on the overlap of values and interests, with configurable weights. Drops run on a manual trigger for the MVP. Students aged 16–17 are only matched with each other, never with adults. 4. Date booking: on mutual interest, both students see 3 slots (date, time, partner venue). The first shared choice books the date into an in-app calendar. 5. Presence check: a bilateral QR scan during the booked slot confirms that both showed up. No location tracking. 6. No-show and cancellation policy: a no-show triggers a 1–2 week lockout. Cancelling more than 6 h ahead is free twice per semester; the third cancellation triggers a lockout. Cancelling less than 6 h ahead counts as a no-show. 7. Semester-end deletion of personal data. 8. Mobile-first web app (PWA-ready), accessible (WCAG AA), light and dark mode. Expected tech stack We have a preferred stack. Well-argued alternatives are welcome in your proposal. - Backend: Java 25, Spring Boot 4, Spring Modulith (modular monolith with modules such as identity, profile, matching, booking, venue, presence, policy), Gradle (Kotlin DSL) - API: API-first with OpenAPI 3.1; server interfaces and the TypeScript client generated from the spec - Database: PostgreSQL only (one schema per module, Flyway migrations). No Redis, no message broker. - Identity: Keycloak (custom login theme, email verification, domain restriction, IDP Integration) - Frontend: React + TypeScript (Vite), React Router, TanStack Query, `oidc-client-ts`, CSS Modules with design tokens - Testing: JUnit + Testcontainers + module boundary tests; Vitest, Testing Library, MSW, Playwright and axe; at least 80 % line coverage - Delivery: Docker Compose for local runs (app, Postgres, Keycloak, local mail catcher); CI on GitHub Actions; images in GHCR Profile: Must have - 2+ years of professional full-stack experience, with production Spring Boot and React work - Solid OAuth2 / OIDC experience, ideally with Keycloak (themes, realm configuration) - Comfortable designing relational data models and writing scheduled or batch logic (matching drops, lockouts) - Privacy by design: you know what data minimisation means in practice. Familiarity with Swiss revDSG or GDPR is a strong plus. - Writes tests as part of the work, not after it - Fluent written English Profile: Nice to have - Experience with Spring Modulith or other modular-monolith setups - Matching, recommendation or scheduling algorithms - Accessibility (WCAG) and mobile-first UI - Experience building consumer apps for students or young adults How we work with you - Work is organised as user stories in Jira with acceptance criteria. Each story is delivered as one pull request on GitHub. - Every PR maps each acceptance criterion to evidence (test, screenshot or manual check) and is reviewed by our team. - Technical decisions are recorded briefly in Confluence (ADRs for decisions, short technical design notes for new data or APIs). - Only synthetic test data. No real student data at any stage (besides production). - New dependencies, external services or costs are agreed with us before you add them. - Weekly 30-minute check-in with the product owner; async the rest of the time. Deliverables - Source code in our GitHub repository, with a green CI build and CD Integration - Short documentation: architecture overview, how to run, Feature Descriptions, ADRs, TDRs (all in Jira / Confluence)