핵심 요구사항
- Spring Boot로 REST 엔드포인트 설계 및 구현 (엔티티·리포지토리·서비스·컨트롤러·DTO)
- 입력 검증 및 JUnit/Mockito 단위 테스트 작성
- Angular 또는 React 컴포넌트로 API 연동 및 반응형 UI 구현
- Swagger/Postman 문서 작성 및 Git PR 기반 협업
- GraphQL·Kafka·AWS 경험 시 우대(후속 단계)
Required stack
필요 기술
Spring BootJavaAngularReactREST APIJUnitMongoDBGit
Project brief
프로젝트 내용
I have several mini projects in motion and a growing to-do list across a Spring Boot back-end and Angular / React front-ends. The most urgent item is fleshing out clean, well-documented REST APIs in Spring Boot that feed the existing UI layers. Typical tasks include defining entities, repositories and service classes, wiring controllers, mapping DTOs, validating input, and writing unit tests. As soon as an endpoint is stable, it needs to be consumed by either the Angular or React interface with a responsive, polished user experience.
The codebase lives in Git; each feature is tracked in small Jira tickets so the scope stays tight. After completing a ticket, simply open a pull request, add Swagger or Postman collections for quick testing, and walk me through the changes on a short call. GraphQL, Kafka, and AWS sit on the roadmap for later phases, so prior exposure to those tools will definitely help when we begin integrating messaging and cloud deployment.
Deliverables per ticket
• Spring Boot REST endpoint(s) fully functional and tested
• Updated Angular or React components hooked to those endpoints
• Swagger / Postman documentation for the new API surface
• JUnit / Mockito back-end tests and front-end test coverage where applicable
• Brief hand-off notes explaining design decisions
Acceptance criteria: Maven build passes, all tests are green, the UI compiles without warnings, and each endpoint returns the expected payload as specified in the ticket.
Work kicks off immediately, with milestones scoped small so progress is visible and feedback is fast.
The codebase lives in Git; each feature is tracked in small Jira tickets so the scope stays tight. After completing a ticket, simply open a pull request, add Swagger or Postman collections for quick testing, and walk me through the changes on a short call. GraphQL, Kafka, and AWS sit on the roadmap for later phases, so prior exposure to those tools will definitely help when we begin integrating messaging and cloud deployment.
Deliverables per ticket
• Spring Boot REST endpoint(s) fully functional and tested
• Updated Angular or React components hooked to those endpoints
• Swagger / Postman documentation for the new API surface
• JUnit / Mockito back-end tests and front-end test coverage where applicable
• Brief hand-off notes explaining design decisions
Acceptance criteria: Maven build passes, all tests are green, the UI compiles without warnings, and each endpoint returns the expected payload as specified in the ticket.
Work kicks off immediately, with milestones scoped small so progress is visible and feedback is fast.
지원 기회 분석
지원 전에 볼 것
예상 산출물
- 완성·테스트된 Spring Boot REST 엔드포인트
- API 연동된 Angular/React 컴포넌트
- Swagger/Postman API 문서
- JUnit/Mockito 백엔드 및 프론트엔드 테스트
- 설계 결정 설명 핸드오프 노트
매력 포인트
- 명확한 티켓 단위 스펙과 수용 기준
- GraphQL·Kafka·AWS 등 향후 확장 로드맵 존재
확인할 점
- 시급 $8~$15로 요구 기술 범위(풀스택+테스트+문서화) 대비 지나치게 낮은 단가
- 입찰 139건·평균 $14로 저단가 경쟁 심화
- 클라이언트 국가·평점 정보 부재로 신뢰도 확인 불가
Client signal
클라이언트 정보
플랫폼에서 상세 정보를 확인하세요.