Ammetra’s engineering pods are the core production workforce of the company. These are the teams in each division that write, test, and ship the code behind our products every day.
Who Works in a Pod #
Pods are small, cross-functional teams. A typical pod includes:
| Role | What they do |
|---|---|
| Full-stack developers | Design and build features across the front end and back end |
| QA testers | Test features, write automated tests, and protect quality |
| UX/UI designers | Design the user experience and interface |
| DevOps engineers | Run build and deployment pipelines, infrastructure, and monitoring |
| Engineering manager / pod lead | Leads the pod, sets priorities with product management, and supports the team |
Pods in Each Division #
| Division | Pods |
|---|---|
| Enterprise Software / Core SaaS | Feature pods for the flagship products |
| Cloud Services & Platform | Platform pods for APIs, infrastructure, data centers, and hosting |
| Cloud Services & Platform: Agile Incubation Team | Rapid-prototyping pods that build MVPs and experimental features |
| Emerging Technologies / AI & ML | AI and ML pods for models, data pipelines, and AI-powered features |
How Pods Work #
- Work is planned in sprints against the division roadmap.
- All code goes through code review and automated testing before it ships.
- Releases go through the shared CI/CD pipelines and staging environments provided by QA Infrastructure & Staging Environments.
- Pods share on-call duty for the services they own.
- After major releases or incidents, pods take part in blameless post-mortems run with Agile Transformation & Enablement.
What You Can Expect #
- Clear priorities: A defined roadmap and goals agreed with your product manager.
- Good tools: The hardware, software, and environments you need, kept up to date.
- Training: Engineering bootcamps, upskilling programs, and management tracks from Learning & Development.
- Support: Access to People Operations, wellness, and employee assistance services.
- Recognition: Programs that celebrate quality, reliability, and outstanding work.
Quality, Security, and Reliability First #
Shipping safely matters more than shipping fast.
- Follow secure coding standards and never commit secrets or credentials to code.
- Stop the release if you find a serious security or reliability problem. You have the authority and the responsibility to do so.
- Report security vulnerabilities to the Chief Information Security Office immediately.
- Use only approved tools, libraries, and open-source licenses.
Getting Help #
| Need | Contact |
|---|---|
| Daily work and priorities | Your engineering manager or pod lead |
| Team transfers, training, tooling | Your division’s management staff |
| Pay, leave, benefits | People Operations, hr@ammetra.com |
| Laptops, accounts, access | Internal IT & Global Infrastructure, it@ammetra.com |
| Security vulnerabilities | Chief Information Security Office, security@ammetra.com |
| Workplace safety | Headquarters Workplace Operations & Facilities, facilities@ammetra.com |
| Ethics concerns | Confidential Ethics Hotline |