CareerSwift
Full-Stack Developer
About this role
CelebriOS is hiring a Full-Stack Developer to build a new analytics platform for mid-market businesses. You'll work across TypeScript/React and Python/PostgreSQL to create data-driven dashboards and insights, with meaningful input on technical direction and product evolution from day one.
What you'll do
- Develop features across React frontend and Python/PostgreSQL backend for an analytics platform
- Design and implement analytics functionality that transforms business data into dashboards and reports
- Own technical design and implementation with guidance from senior engineers
- Collaborate with product and design teams to build reliable, intuitive user experiences
- Write automated tests and ensure quality of production code; investigate issues and improve performance
- Review pull requests and help establish engineering practices as the team scales
What they're looking for
- React and TypeScript
- Python backend development
- PostgreSQL and relational databases
- SQL
- API design and integration
- Testing and debugging
- Git and code review
- AWS or cloud platforms (nice to have)
Benefits
- Remote-first work environment
- Professional development opportunities
- Comprehensive benefits package
- Opportunity to shape product direction and technical decisions
- Work with a distributed US-based team
- Early-stage product involvement with meaningful impact
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
CareerSwift
CareerSwift builds an AI-powered job search platform with a focus on reliable infrastructure and polished user experiences. The company is hiring DevOps engineers to manage cloud infrastructure and CI/CD pipelines, frontend developers to build React-based interfaces, and QA engineers to ensure product quality through manual and automated testing.
View all jobs at CareerSwiftLikely interview questions
- Tell us about a production feature you built end-to-end across frontend and backend—what was your technical approach and how did you handle testing?
- How do you approach designing an API that a React frontend will consume, and what tradeoffs do you consider?