StartupPool
2023-04-28 — 2023-06-28
Backend developer in 8-member cross-functional team building a startup vertical network platform — designed and implemented core community APIs on NestJS, integrated 4 OAuth 2.0 social login providers, built independent admin backend across 2-month sprints
Problem Solving
Startup info scattered, making comparison difficult for investors/job seekers
Built startup data collection/normalization platform with NestJS + PostgreSQL, category filters + search API
Unified startup info browsing + category-filtered platform
Project Description
Responsible for the backend of a startup vertical network platform enabling aspiring entrepreneurs to handle team building through item validation in one place. Designed and implemented core community APIs (posts, comments, likes, bookmarks, follows) on NestJS, and built a unified user onboarding flow integrating 4 social login providers (Google, Naver, Kakao, Facebook). Developed OpenGraph metadata scraping for link previews and file upload APIs, along with a separate admin backend for content management. Collaborated with frontend developers on API specifications across 2-month sprint cycles in an 8-member team.
Team Composition
FE(2) BE(2) PM(1) Design(1) Marketing(2) / Responsible for BE
Collaboration Tools
Highlights
- Integrated 4 social login providers (Google, Naver, Kakao, Facebook) with unified OAuth 2.0 flow
- Solely implemented core community APIs (posts, comments, likes, bookmarks, follows)
- Developed OpenGraph scraping-based link preview with metadata parsing
- Built independent admin backend for content and user management
- Collaborated on API spec design with FE in 8-member cross-functional sprint team
Performance Metrics
| Performance Metrics | Before | After |
|---|---|---|
| Social login providers | - | 4종 통합 (OAuth 2.0) |
| Community APIs | - | 게시물·댓글·좋아요·북마크·팔로우 (전담 구현) |
Tech Decisions
- ▶ NestJS + PostgreSQL: manages normalized relational data model for startup information, optimized category and search filter queries
Lessons Learned
- • Learned provider-specific auth flow differences and token management strategies through integrating 4 OAuth 2.0 social login providers
- • Strengthened interface-based collaboration and communication skills by negotiating API specs with FE in an 8-member cross-functional team
- • Gained experience in social feature data modeling and relationship design by solely designing and implementing core community APIs (posts, comments, likes, follows)
- • Learned separation of concerns between user-facing services and admin systems by independently building a content management admin backend