Datology AI
Software Engineer, Front-end
About this role
DatologyAI is seeking an experienced full-stack engineer to build customer-facing data curation products and internal tools that optimize AI training datasets. You'll work closely with founders on product direction and drive technical decisions for a well-funded startup backed by major investors and AI pioneers.
What you'll do
- Own full product development lifecycle for customer-facing data curation features and internal infrastructure
- Engage with customers and stakeholders to understand problems and design solutions
- Collaborate cross-functionally with engineers, researchers, and designers on new capabilities
- Ensure products and systems maintain high reliability, security, and trustworthiness
- Develop core visualizations and tooling for dataset curation workflows
- Maintain quality standards for design, correctness, and testing
What they're looking for
- JavaScript/TypeScript
- React and web technologies
- Python
- Full-stack and backend development
- Production systems design
- Software quality and testing practices
- Problem-solving and end-to-end ownership
- ML/AI experience (preferred)
Benefits
- Competitive salary ($180K-$300K) plus meaningful equity
- 100% covered health benefits (medical, vision, dental)
- 401(k) with 4% company match
- Unlimited PTO
- 12 weeks paid parental leave plus 6 months WFH flexibility
- $2,000 annual wellness stipend
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.
Datology AI
DatologyAI builds a data curation platform that optimizes AI training datasets to reduce costs and improve model performance. The company is hiring cloud infrastructure engineers, data platform engineers, full-stack product engineers, and solutions engineers to scale its multi-cloud infrastructure and customer-facing tools.
View all jobs at Datology AILikely interview questions
- Walk us through a production full-stack feature you owned end-to-end. What were the key technical decisions, and how did you balance frontend, backend, and infrastructure concerns?
- Tell us about a time you had to learn a new technology or domain quickly to solve a critical problem. How did you approach it?