Backend
- NestJS (TypeScript) - main REST API
- PostgreSQL - primary database
- Sequelize - ORM layer
- gRPC - inter-service communication
Back to Careers
How We Work
This is what you're signing up for.
No surprises. Here's how the team works, what tools we use, and what your first week would actually look like. If this sounds like your kind of environment, we should talk.
Remote-first
AI-assisted
Async by default
Our Stack
We're a monorepo with multiple services. Here's what you'd be working with.
Frontend
- Angular 16 with Material components
- TypeScript throughout the app layer
- Shared design tokens and reusable UI patterns
- Product-facing workflows built directly against the core platform
AI Infrastructure
- Python / FastAPI - AI service layer (AICM)
- Qdrant - vector database for RAG and embeddings
- Redis - caching and queues
- RAG workflows built into the platform, not bolted on
Services + Website
- Mail, CDN, SSO, Analytics - separate microservices
- Page Builder - template-based website and landing-page engine
- MCP Server - Claude / AI integration layer
- Tailwind CSS + DaisyUI on the website surface when that stack fits
Tools We Use
No mystery stack. Just the tools that keep the work moving.
Code hosting
GitLab
CI/CD
GitLab CI
Communication
Slack
Project tracking
Aktok - yes, we use our own product
AI development
Claude Code, MCP protocol
Design
Figma
Documentation
Markdown in repo
How We Use AI
This is the part that's different from most teams.
We don't just build AI features - we use AI to build.
Claude Code is integrated into our development workflow. We have a custom MCP server that connects Claude to our task management, codebase, and documentation.
That means the day-to-day work is faster, more research-heavy, and more explicit. The system is there to help you think, ship, and keep context - not to replace judgment.
- Code review and implementation assisted by AI agents
- Documentation generated and maintained with AI
- Task planning and architecture discussions with AI in the loop
- Research and competitive analysis powered by AI
If you've never worked this way, it's a learning curve. Once you're in it, going back to pure manual development feels slow. We'll help you get up to speed.
How We Communicate
Remote-first. Async when possible. Sync when it matters.
The team is distributed. We default to writing things down, keeping context visible, and only pulling people into a call when the written path will clearly lose time.
Day-to-day
Slack is the operating layer.
Channels are organized by topic, not by noise. Questions, drafts, updates, and handoffs happen where the next person can find them.
Decisions
Write it down first.
Written proposals in markdown are the default. That keeps the reasoning visible and makes async review possible.
Meetings
No standing calls for the sake of it.
We meet when async will be slower or lower quality. The goal is resolution, not calendar occupancy.
Updates
Ship notes, not status theater.
Progress shows up in code, content, proposals, and delivery. We care about what moved, not how busy everyone looked.
We trust people to manage their own time. If you need to work at 2am because that's when you're productive, fine. We care about output, not hours.
Your First Week
Within one week, you should have shipped something real and know how the system works.
01
Day 1-2
Setup
- Get access to GitLab, Slack, Figma, and Aktok
- Clone the monorepo and get local dev running
- Read the `CLAUDE.md` files - they are the map to the codebase
- Meet the team on a quick call
02
Day 3-4
Orient
- Pick a starter task - we will have one ready
- Ship something small: a fix, a component, or a piece of content
- Ask questions and break things - that is expected
03
Day 5+
Build
- You're in the flow. You have context. You ship.
- Nobody micromanages. If you're stuck, ask. If you're not, keep going.
- Momentum matters more than ceremony.
What We Expect
Let's be direct.
This setup works well for people who want ownership and badly for people who need a lot of external structure.
Self-directed. Nobody will assign you daily tasks or check in every morning. You own your work.
Good English. Written communication is how we operate. You do not need to be a native speaker, but you need to write clearly.
Comfortable with ambiguity. We're early-stage. Specs change. Priorities shift. That's not chaos - it's the nature of building something new.
Ship over perfect. We'd rather see something working today than something perfect next month.
If that operating style sounds right, the next step is the careers hub - not a long interview funnel.
Next Step
Sounds like your kind of thing?
The careers hub is where the openings live. Start there, then decide if you want into this system.