Recruiter / ATS
Start with Atlas
- Classic resume structure for quick screening and PDF behavior.
- Best when the reviewer wants a familiar, low-friction resume read.
- Strongest when time is tight or the resume will be uploaded to an ATS.
Start with the reader, not the file format
These are the fastest entry points depending on who is evaluating you and what they care about.
Hiring Manager
Start with Signal (recommended default)
- Highlights Cloud, Backend, APIs, and enablement immediately.
- Lets the right bullets rise to the top instead of making the reader do the mapping work.
- Best when the reviewer wants fit, range, and relevance in one pass.
Technical Lead / Staff+
Start with Signal + a narrower preset
- Useful when a reviewer wants platform, integration, architecture, and ops emphasis.
- Best for cloud, backend, APIs, data platform, or device-service roles.
- Works well when the job description is specific and you want tailored emphasis quickly.
Proof-first reviewer
Start with Proof Hub
- Best when a skeptical reader wants cases, examples, and supporting materials first.
- Pairs especially well with the payment portal, automation, and serverless architecture evidence.
- Lets you prove outcomes before asking anyone to trust summary bullets.
Branded landing page
Open Home
- Useful when you want the fuller presentation layer around the resume system.
- Best for direct outreach, portfolio-style sharing, or a more designed first impression.
- Not the best first stop for ATS or fast recruiter scans.
Low-motion fallback
Classic switchboard behavior
- Keep this option when you want the simplest no-surprises routing page.
- Good fallback for constrained browsers or readers who just want a clean directory.
- This new version is better as the default because it explains the choices more clearly.
Selected proof the old switchboard did not surface early enough
These are the kinds of signals that should appear before a reader has to choose where to click.
< 1 min
Secure provisioning
Recent evidence documents a Python-based IoT provisioning flow that cut one quantified onboarding path from about 10 minutes to under 1 minute per device.
~40%
Payload efficiency
MQTT delta updates were documented as reducing payload size for constrained devices, with one example showing 476 bytes down to 15 bytes.
~30%
Onboarding reduction
A provisioning README with install, CLI, and security guidance was documented as cutting onboarding time for new engineers by an estimated 30%.
Exceeds
Enablement signal
The 2024 manager review specifically called out partner-team support, documentation, support efficiency, and cross-org collaboration as standout strengths.
2 AWS
Certification depth
The 2022 self-evaluation states the portfolio includes both AWS Cloud Practitioner and AWS Solutions Architect Associate, with SAA-C03 completed on 08/25/2022.
These proof cards are intentionally short. The goal is not to replace the resume; it is to earn the next click.
How the modes differ
The existing switchboard hints at this. This version makes it explicit.
Mode comparison
| Mode | Best for | Why it exists |
|---|---|---|
| Home | Direct outreach and branded portfolio sharing | Most presentation-heavy entry point. Good first impression, less ideal for ATS. |
| Atlas | Recruiters, ATS uploads, print-to-PDF | Classic, linear, low-friction resume reading experience. |
| Signal | Hiring managers and technical reviewers | Tailorable, job-specific emphasis without rewriting the resume each time. |
| Proof Hub | Skeptical readers and deep evaluators | Turns claims into examples, cases, and supporting evidence. |
| Switchboard | Readers who just need routing help | A utility hub. Best when it explains the routes clearly and gets out of the way. |
Your older switchboard already supported Atlas, Signal, presets, and a custom builder. Its main weakness was not capability. It was prioritization.
Fast recruiter summary
A copy-ready summary you can paste into outreach, job applications, or cover-note fields.
Build a tailored Signal link
Keep the flexibility of the original switchboard, but make the recommended path easier to find.
One-click presets
These jump directly into Signal with useful combinations already selected.
resume-signal.html?focus=iot,cloud,api,enable
Why this switchboard is better
- It treats Proof Hub as a first-class destination instead of hiding it in the dock.
- It makes the recommended default obvious, so a good reader does not have to self-diagnose first.
- It surfaces documented outcomes before the reader chooses a mode, which makes the click feel earned.
- It explains the differences between the modes plainly, instead of assuming the reader already understands the system.
- It keeps the original strengths: low motion, local theme storage, and Signal link-building.
If you deploy this, the cleanest production name is still resume-switchboard.html. This artifact uses a different filename so you can review it without overwriting the original.