Open to work · Hartford, CT · Relocatable

I break EV
charging systems
before they do.

Preventing real-world EV charging failures across hardware, firmware, and cloud systems at scale — from CAN bus signals to CTEP certification.

Senior QA Engineer · 5+ years · AmpUp, Infosys, Sigma.
OCPP · ISO 15118 · HIL/SIL · Python Automation · Embedded Firmware.

View LinkedIn ↗ GitHub ↗ Contact Me →
Profile at a glance
⚡
EV Charging Systems
OCPP 1.6 / 2.0.1 · ISO 15118 · J1772 · CTEP
🔬
Hardware + Firmware Validation
HIL · SIL · CAN Bus · Oscilloscope · DMM
☁️
Backend + API Testing
REST Assured · WebSockets · Webhooks · PostgreSQL
📱
Mobile + Web Automation
Appium · Selenium · Playwright · BrowserStack
🤖
Automation Framework Dev
Python · Pytest · Jenkins · Docker · Allure
🛠
Internal Tools & Workflows
Retool · Shell scripting · CI/CD pipelines
scroll
Impact at scale
5×
Test Throughput
→ faster releases, lower production risk
1 → 5 chargers validated simultaneously via HIL automation
50%
Faster Validation
→ engineers unblocked, sprints ship on time
Manual 2-week regression → 3-day automated pipeline
11→0
Compliance Failures
→ California market access unblocked in 14 days
CTEP non-conformances resolved, certification passed
7
Critical Bugs Caught
→ zero field incidents from these firmware defects
Pre-production bugs found via fault injection testing
Also:
95% UAT sign-off rate across all sprints 40+ fault scenarios validated 200+ protocol sequences per nightly CI run 500+ OCPP transactions replayed under stress 3 OEM integrations — billing gap rate → zero
OCPP 1.6·OCPP 2.0.1·ISO 15118·J1772·CTEP Compliance·CAN Bus Analysis·HIL Testing·SIL Testing·Python · Pytest·Selenium · Appium·REST Assured·Jenkins · Docker·Oscilloscope · DMM·Embedded Firmware·DIN 70121·Retool·
What makes me different

Hardware + Software QA.
End to end.

🔩
I work from the wire up
Most QA engineers start at the API. I start at the CAN bus — probing voltage signals with an oscilloscope and correlating them with a backend billing discrepancy in the same session. That hardware-to-cloud range compresses root-cause cycles from days to hours.
⚡
Deep EV protocol expertise
Not just test execution — I understand OCPP 1.6, 2.0.1, ISO 15118, and CTEP compliance at a protocol level. I know why a charger fails, which firmware field is non-compliant, and how to produce certifying-body evidence without external consultants.
🧠
Systems-first debugging mindset
Before writing tests, I map the full failure surface: what can hardware do that firmware doesn't expect? Where does the OCPP spec leave room for divergent implementation? That mental model finds field-critical issues that generic test coverage misses entirely.
📐
I build infrastructure, not just tests
My HIL framework at AmpUp became the team standard. My fault injection matrix became a mandatory certification gate. I build quality infrastructure that compounds over time — other engineers build on it, and coverage improves with every release.
Case Studies

Engineering problems
I've actually solved

01
VoltGrid — EV Charge Point Operator Platform Open Source
✓ Full OCPP 1.6 implementation ✓ Live dashboard ✓ Real-time WebSocket
💡 Built a full-stack EV Charge Point Operator platform to demonstrate real OCPP protocol implementation end to end.
Personal Project · GitHub Repo · Live API · HTML · Node.js · SQLite
+
What it is
A full-stack EV Charge Point Operator (CPO) platform built from scratch to demonstrate real OCPP 1.6 protocol implementation. Covers the complete session lifecycle — boot notification, authorization, metering, and session stop — with a live operator dashboard.
What I built
  • OCPP 1.6 WebSocket server in Node.js handling all core message types
  • Real-time operator dashboard showing charger status and session data
  • SQLite backend storing transaction records and charger state
  • End-to-end session simulation for testing and validation
Stack
Node.jsOCPP 1.6WebSocketSQLiteHTML/CSSJavaScript
Why it matters
Shows I don't just test OCPP — I can implement it. Understanding the protocol at implementation level makes me dramatically more effective at diagnosing production failures in the field.
→
Full OCPP 1.6 CPO platform — built from scratch. Demonstrates protocol-level expertise that goes well beyond typical QA scope.
View Repo → View README → Live API →
02
OCPP Billing Validation System OCPP 2.0.1
✓ Billing gap rate → zero ✓ 3 OEM integrations fixed ✓ Root cause in 6 days
💡 Charging sessions failed to generate billing records → revenue lost silently, compliance at risk.
AmpUp · 2024–Present · Protocol + Backend Layer
+
Problem
Sessions closed without valid billing records — intermittent, invisible in staging, consistent in the field during cellular handoffs. meterValue gaps between StopTransaction payloads and backend records created unreconciled revenue discrepancies and compliance exposure.
Approach
  • Built Python OCPP message interceptor — replayed 500+ transaction sequences
  • Injected packet loss, session timeouts, reconnection events
  • Correlated charger-side OCPP payloads with PostgreSQL billing records
  • Surfaced 3 distinct gap patterns across 2 OEM firmware variants
Stack
PythonOCPP 1.6/2.0.1REST AssuredPostgreSQLPytestWiresharkWebSockets
Result
Root cause: non-compliant StopTransaction timing in firmware variant B. Fix deployed in 6 days. Framework adopted as the standard regression suite for all new charger OEM onboarding.
→
Billing gap rate: zero across all 3 OEM integrations. Root cause confirmed via protocol trace in 6 days.
View GitHub →
03
EV Charger HIL Automation Framework HIL / SIL
✓ 5× throughput gain ✓ 14 days → 3 days cycle ✓ Zero prod regressions
💡 Manual regression took 3 engineers × 2 weeks per release → shipping was slow and coverage was unreliable.
AmpUp · 2024–Present · Embedded + Automation Infrastructure
+
Problem
Manual regression per firmware release: 3–4 engineers, 2 weeks, no repeatability. OCPP 2.0.1 protocol edge cases — smart charging, reservation flows, certificate handling — were routinely missed. No automated signal between firmware commit and production readiness.
Approach
  • Modular Python + Pytest HIL framework with composable charger fixtures
  • Parallel execution across 5 physical stations via pytest-xdist
  • Allure dashboards with per-run protocol trace artifacts
  • Jenkins nightly regression — fully unattended on every firmware commit
Stack
PythonPytest + xdistOCPP 2.0.1HIL/SILAllureJenkinsDockerCAN Bus
Result
Regression cycle: 14 days → 3 days. 5× parallel charger coverage. 200+ protocol sequences per nightly run. Zero production regressions since deployment.
→
5× throughput. 14-day cycle → 3 days → faster releases, reduced production risk. Team-wide standard.
View GitHub →
04
Network & Power Failure Recovery Suite Fault Injection
✓ 7 firmware bugs found ✓ 0 stuck sessions post-fix ✓ New certification gate
💡 Chargers stuck mid-session during outages → driver abandonment, manual backend cleanup, support escalations.
AmpUp · 2024 · Resilience Engineering
+
Problem
Field deployments showed chargers stuck during Wi-Fi → cellular transitions and power cuts. Sessions abandoned mid-charge created backend state mismatches requiring manual reconciliation and driver support tickets at scale.
Approach
  • 40-scenario fault injection matrix: power cut, network drop, reconnect timeout, BMS signal loss
  • Relay-controlled power supplies + traffic shaping on purpose-built lab bench
  • Captured StatusNotification payloads, heartbeat recovery, webhook confirmations
  • Correlated oscilloscope/DMM hardware signals with backend logs
Stack
PythonFault InjectionCAN BusRelay BoardsOCPP 1.6Webhook CaptureOscilloscopeDMM
Result
7 previously unknown firmware defects surfaced. 0 stuck sessions across 3 months post-fix. Recovery matrix is now a mandatory pre-certification gate for all new charger hardware at AmpUp.
→
7 firmware bugs caught before production → zero field incidents. Fault injection matrix is now a mandatory certification gate.
View GitHub →
05
CTEP Compliance Validation ISO 15118
✓ 11 → 0 failures in 14 days ✓ CTEP certified ✓ CA market unblocked
💡 Pre-audit found 11 failures blocking California market entry → hard deadline, no room to slip.
AmpUp · 2024 · Certification Engineering
+
Problem
Pre-certification CTEP audit: 11 non-conformances blocking California market access. Failures: metering accuracy windows, session boundary reporting, energy data granularity under ISO 15118 PnC flows — with a hard deadline.
Approach
  • Mapped each of 11 failures to CTEP test case IDs + OCPP 2.0.1 message fields
  • Root cause: meterValue reporting intervals + StopTransaction energy summation
  • Produced protocol logs, oscilloscope waveforms, regression traces for certifying body
  • Compliance CI suite — runs automatically on every firmware release
Stack
CTEP FrameworkISO 15118OCPP 2.0.1PythonMetering ToolsOscilloscopeProtocol Traces
Result
All 11 non-conformances resolved in 14 days. CTEP certification passed. California market access unblocked. Compliance CI suite prevents future regressions automatically.
→
11 → 0 compliance failures in 14 days → California market unlocked. Compliance now runs automatically in CI.
View GitHub →
Internal Tooling

Retool dashboards &
automation pipelines

Beyond test cases — building the internal tools that make quality engineering faster for the entire team.

📊
Retool
Charger Health Dashboard
Built a Retool dashboard giving the QA team real-time visibility into charger session health, OCPP message flow status, and backend billing reconciliation across all deployed stations. Replaced manual log-grepping.
RetoolPostgreSQLREST APIOCPP Logs
→ 3× faster incident triage for field support teams
⚙️
Python + Shell
Automated Log Analyzer
Python CLI tool that parses raw OCPP WebSocket logs, extracts session state transitions, flags protocol anomalies, and outputs structured JSON reports. Eliminated hours of manual log analysis per debugging session.
PythonShell scriptingJSON parsingOCPP
→ Log analysis time: hours → <5 minutes per incident
🔄
Jenkins + Docker
Nightly Regression Pipeline
Full CI/CD pipeline for EV charger regression — Docker-containerized test environments, parallelized Pytest runs across 5 HIL stations, Allure report publishing, and Slack alerting on failures.
JenkinsDockerPytestAllureSlack API
→ Zero manual runs — fully automated since Q4 2024
Technical Skills

Full-stack quality,
hardware to cloud

⚡EV Protocols
🔬Hardware / Lab
🤖Automation
🔗API & Backend
🚀DevOps / CI
📱Mobile & Web
EV Charging Protocols
Protocol-level expertise — not just test execution but genuine understanding of session lifecycle, metering compliance, and failure modes.
OCPP 1.6OCPP 2.0.1ISO 15118DIN 70121J1772CTEP ComplianceCHAdeMOSmart ChargingPlug & Charge (PnC)RFID AuthenticationmeterValue ValidationSession LifecycleInteroperability TestingProtocol Trace Analysis
Hardware & Lab Validation
Hands-on embedded diagnostics — correlating hardware-level signals with cloud transaction data in the same debugging session.
HIL TestingSIL TestingCAN Bus AnalysisOscilloscopeDMMPower AnalyzersRelay Board ControlFault InjectionEmbedded Firmware TestingBMS Signal ValidationHV Charging CharacterizationLab Bench SetupVehicle-Level TestingMetering Accuracy
Test Automation
Building platforms others build on — not scripts, but test infrastructure that compounds in value with every release.
PythonPytestJavaSelenium WebDriverPlaywrightCypressCucumber BDDTestNGJUnitRobot FrameworkPage Object ModelData-Driven TestingParallel ExecutionAllure ReportsTosca L1 + L2
API & Backend Testing
From OCPP WebSocket payloads to REST billing APIs — validating the entire data layer end to end.
REST AssuredPostmanGraphQLSoapUIJMeterLoadRunnerWebhook ValidationWebSocket TestingPostgreSQLMySQLMongoDBSnowflakeRedisLog Analysis
DevOps & CI/CD
Quality gates that run automatically on every commit — integrated into the full software delivery lifecycle.
JenkinsGitHub ActionsGitLab CICircleCIDockerKubernetesTerraformAWSAzureGCPGit / BitbucketJiraTestRailSplunk
Mobile & Web Testing
End-to-end coverage across Android and iOS EV driver apps, operator dashboards, and responsive web interfaces.
AppiumBrowserStackAndroid AutomationiOS AutomationCross-Browser TestingResponsive UI ValidationJavaScriptHTML5 / CSSC#Shell ScriptingRetool
Experience

Where I've
built things

AmpUp
Hardware & Software Quality Engineer
Oct 2024 – Present
USA · EV Charging
  • Owns end-to-end integration validation across firmware, charger UI, backend APIs, and network layers — protocol-driven go/no-go gates before each production rollout across multi-vendor OCPP deployments.
  • Built Python + Pytest HIL automation framework scaling charger validation from 1 → 5 simultaneous stations, compressing 2-week manual regression to 3 automated days (5× throughput, faster release cycles).
  • Led CTEP compliance remediation: 11 non-conformances → 0 in 14 days — California market access unblocked; compliance CI suite prevents future regressions.
  • Hands-on embedded diagnostics via oscilloscope, DMM, and CAN bus analyzers — correlating hardware-level signals with backend transaction records to confirm root causes.
  • Designed 40-scenario fault-injection matrix surfacing 7 previously unknown firmware defects before field deployment — zero field incidents post-fix.
  • Maintained 95% release sign-off rate across all Agile sprint cycles; built Retool dashboards for real-time charger health visibility.
Infosys Limited
Automation Test Engineer
Jul 2021 – Dec 2022
India · Enterprise
  • Developed Cucumber BDD regression suites in Java — 100+ automated scenarios, coverage +45%, manual effort −50% per sprint.
  • REST/SOAP API validation — staging API failures reduced by 40% via early interface stability checks.
  • Integrated automation into Jenkins CI for nightly runs — 3× execution frequency, tighter quality feedback.
  • Led Appium mobile automation for iOS + Android — release cycle efficiency +20% across 25+ flows.
  • LoadRunner performance scripts simulating 1,000+ concurrent users — backend reliability at production scale.
Sigma Info Tech
QA Engineer
Jul 2018 – Jun 2021
India
  • Built scalable Page Object Model framework with Maven + Jenkins — maintenance overhead −35%, unattended nightly CI.
  • 200+ manual and exploratory test cases across 10+ Agile sprints — consistent release readiness.
  • 50+ Appium scripts for iOS + Android — mobile test execution +30% faster.
  • Standardized Selenium suite on Robot Framework — onboarding time −30%.
Contact

Let's build what
doesn't fail.

Looking for senior QA engineering roles where quality is a first-class discipline — EV charging infrastructure, autonomous systems, or FAANG-scale platforms. Based in Hartford, CT. Open to remote and hybrid.

Start a conversation →
✉
Email
dattaphani899@gmail.com
→
in
LinkedIn
linkedin.com/in/phanidatta
→
📞
Phone
+1 913 408 8775
→
⌥
GitHub
github.com/dattaphani899-create
→