pesha
- role
- Product, frontend, backend
- project
- Personal product
- status
- Live · alpha
- built with
- Next.js · React · TypeScript · Go · Chi · PostgreSQL
- visit
- pesha.work ↗
- my part
- I own the frontend and backend development: the Next.js interface, Go API, PostgreSQL integration, and the connection between job discovery and account flows.
overview
Pesha is my own product for discovering work. The current alpha brings job listings into a focused interface where people can search roles, narrow the list by category, and find the details they need before applying.
I build both the frontend and backend. That means working on the experience people see, the APIs that serve it, and the data behind each listing. The live release is an alpha, and the product is still evolving.
the experience
find a role
Search jobs by role or skill and use category filters to narrow the listings. Pagination keeps the feed manageable.
read the essentials
Each listing brings together the role, company, location, employment type, posting date, and application deadline.
keep it focused
The current release prioritises job discovery. Planned sections are clearly marked as alpha previews in the live product.
under the hood
interface
Next.js, React, and TypeScript power the job feed and account screens, with responsive layouts and light and dark themes.
application
Go and Chi serve the API. Handlers, services, and repositories separate HTTP requests, application rules, and persistence.
data & delivery
PostgreSQL stores the application data through pgx. Docker packages the frontend and backend for deployment.
engineering decisions
give the job feed its own boundary
The frontend can use a dedicated jobs API independently of the account API. That lets local account development work alongside the live job feed, without tying every screen to the same backend environment.
separate the application rules
The Go backend separates HTTP handlers, services, and repositories. Request handling stays at the edge, application behaviour lives in services, and PostgreSQL access stays in the repository layer.