Software Architect
Owns architecture decisions, technology selection, scalability, APIs, microservices, and database design.
Designs, builds and tests your software.
The Software team works like a small development department: an architect who decides how things are built, developers who build them, a tester who tries to break them and a technical writer who explains them. Everything happens in Git, so nothing is lost and every change can be reviewed.
Work starts as an issue in your own Git server (Forgejo). The Software Architect shapes it into a plan, a Developer writes the code on a branch and opens a pull request, and the QA Tester checks it before anything is merged. The architect is the only agent with administrator rights on the Git server.
The team runs in its own isolated account with its own keys, so a mistake in one project never touches another team. DevOps connects the team to Infrastructure, and the Data Analyst and AI/ML Engineer bring data and machine learning into the products.
Automatic builds and tests for every pull request and error tracking for your apps are on the roadmap, so problems are found by machines before people meet them.
A customer reports a bug through Support. The issue lands in Forgejo, a Developer reproduces it, writes a fix with a test, the QA Tester confirms it and you merge the pull request with one click.
Owns architecture decisions, technology selection, scalability, APIs, microservices, and database design.
Builds and maintains the company's software and integrations.
LLMs, RAG, embeddings, prompts, evaluation, and inference optimization.
CI/CD, Kubernetes, Docker, Infrastructure as Code, and deployments.
Writes and runs tests, reports bugs, safeguards quality.
Documentation, API docs, release notes, installation guides, SOPs, and knowledge-base articles.
Turns data into dashboards and decisions.