Georgia State University Department of Health Sciences

Business Operations

• Understand and challenge our operational workflows
• Design and ship BizOps projects end to end
• Bring AI into our operational workflows
• Contribute to the ERP deployment
• Make operational performance measurable

Business Operations Manager

QA Engineer

• Define and own the hardware quality plan
• Build a complete quality plan covering all Vizzia hardware products, with clear deliverables for each hardware function
• Set quality standards and acceptance criteria that everyone on the team can reference
• Ensure the plan is shared, understood, and applied — not just a document that lives on a drive
• Write, share and roll out quality processes across the full hardware development chain
• Create the internal and external templates the team and suppliers will use day-to-day (test plans, audit forms, non-conformity reports, certification documentation)
• Train and coach the hardware team to embed these processes into their work
• Define test plans for every Vizzia hardware product
• Ensure test plans are executed systematically before products reach production
• Trace results so nothing falls through the cracks
• Establish structured supplier quality control, starting with Altior and extending to other manufacturing partners
• Lead audits, define corrective action plans and follow them through to closure
• Travel to China approximately twice a year to audit suppliers and align on quality expectations on site
• Ensure certification-related documentation (CE in particular) is complete, up-to-date and audit-ready at any time
• Build traceability that allows reconstruction of the full history of any product version, any change, or any non-conformity
• Improve field reliability over time — increase mean time to failure and reduce field returns

Lead Hardware Quality Engineer

Cloud Engineer

• Take ownership of the IoT cloud perimeter
• Get hands-on with FleetAPI, AWS Step Functions provisioning, RMS, and the Retool layer - operating 50% of the perimeter autonomously within three months, 100% within six.
• Document the stack as you go. The goal isn't a wiki - it's that the team's knowledge becomes shared infrastructure, not tribal memory.
• Make the cloud foundations resilient enough that scaling the fleet doesn't put pressure on a single person.
• Own AWS architecture and infrastructure-as-code
• Design and evolve compute (Lambda, ECS, Batch), networking, storage and IAM across the DLM perimeter.
• Bring the full stack under CDK - no manual AWS console clicks to ship a critical infra change.
• Make trade-offs (serverless vs container, RDS vs DynamoDB, push vs pull) and explain them to the team without dogmatism.
• Drive observability and reliability
• Instrument logs, metrics, alerting that ops and engineers can act on.
• Run on-call rotation, write post-mortems, keep runbooks current.
• Move MTTR down quarter after quarter, with the numbers to prove it.
• Ship backend services
• Build and maintain backend services in Node.js / TypeScript (Python where it makes sense), at production grade.
• Pair with the Tech Lead and the full-stack IC on infra-aware design from the spec stage - so trade-offs are made before the code, not discovered at review.
• Become the cloud referent across teams
• Within 12 months, represent CIOT-DLM in cross-team architectural discussions (Platform, Data Platform, NetSec, AI).
• Take ownership of one major vertical at six months - provisioning, fleet drift detection, or RMS - and ship a measurable improvement on reliability or manual correction.

Business Operations Manager

Lead Hardware Quality Engineer

Senior Backend, Cloud Engineer