Overview
PST Engineering is a small senior team that ships fast, measures everything, and owns outcomes end to end. We turn messy cross-border workflows into reliable, secure, and auditable systems.
What we build
- Public website and admin tools that stay fast under load
- Pricing, quotes, and shipment orchestration with audit trails
- Integrations with carriers, customs, and payment partners
- Developer surfaces: clean REST endpoints and signed webhooks
- Internal data pipelines for performance, fraud, and SLA tracking
Principles
- Reliability first: correctness and observability over cleverness
- Less code, more impact: reduce surface area, remove dead features
- Security by default: least privilege, encrypted everywhere
- Measure and learn: dashboards, alerts, and postmortems for every incident
- Accessibility and parity: light/dark, RTL, keyboard-friendly by design
How we work
- Tight scopes, weekly demos, zero-fluff standups
- Written design briefs before major changes
- Code reviews focused on risk and clarity, not stylistic bikeshedding
- Feature flags for safe rollout; revert beats quick fix
- On-call with playbooks and clear escalation
Our stack
- Frontend: Next.js, TypeScript, Tailwind, shadcn/ui, lucide
- Backend: Node.js, Next API routes, MongoDB, Mongoose
- Infra: VMs/containers, CDN, object storage, CI/CD with checks and previews
- Observability: logs, metrics, tracing, uptime and error budgets
- QA: contract tests, e2e smoke on critical flows, synthetic monitors
Team
- Head of Engineering — architecture, reliability, hiring
- Staff Engineer (Platform) — CI/CD, observability, security posture
- Senior Full-stack Engineer — product surfaces, performance, accessibility
- Senior Integrations Engineer — carriers, customs, payments, webhooks
- Product Designer — system UX, accessibility, component library
Open roles
We hire opportunistically for high-leverage roles. See current openings on /en/careers or send a strong general application with relevant work.
Contact
Partnerships, security disclosures, or technical questions: use /en/contact with “Engineering” in the subject. Security researchers: include steps to reproduce and affected endpoints.