Kartikeya Bhatt
Forward Deployed Engineer
19+ years exp
Management: 10+ years (6-15 people)
JavaScript
SQL
Java
TypeScript
Python
Node JS
Swift
Data Layer & Database: 6/10
Security & Auth: 6/10
Scalability & Performance: 5/10
Active 1 day ago
Invite to interview
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
Backend-focused engineer (senior-level) with a strength for local-first, data-oriented tooling and demonstrable attention to data integrity and safety. The strongest proven skill is building a local synthetic scenario quality platform with careful schema migrations, signed replay artifacts, a safe SQLite job queue and benchmarking (see scenario_quality/engineering.py and scenario_quality/advanced.py). The public artifacts do not show production-grade service deployments, cloud infrastructure, or large distributed systems patterns such as durable, horizontally scaled queues or multi-service contracts.
Phone
Technical skills
Languages
7
JavaScript
SQL
Java
TypeScript
Python
Node JS
Swift
DevOps
12
AWS
Rest API
Kubernetes
Linux
Terraform
Jenkins
CI/CD
Docker
GitHub Actions
Ansible
Amazon EKS
SOAP
QA
9
Selenium
TestNG
Cypress
Playwright
Appium
XCUITest
JMeter
k6
Pytest
Frontend
3
React.js
Redux
GraphQL
Other
35
OWASP ZAP
Lombok
LLM
PostgreSQL
FastAPI
Pydantic
SQLAlchemy
Amazon S3
Allure Reporting
Tailwind CSS
Next.js
Claude
LangGraph
MySQL
Amazon EC2
AWS Lambda
Jest
GitHub
Datadog
Git
GitLab
GitLab CI
Prometheus
npm
Claude Code
Copilot
Cursor
CloudFormation
Swagger
Nessus
AI Agents
OpenAI Codex
Frontend
RAG
OWASP
Timeline
Forward Deployed Engineer
•
Middle
Nityo Infotech
•
Full-Time
Partnered with business and product stakeholders to translate complex financial workflows into scoped, API-connected solutions and rapid prototypes. Developed React and TypeScript UI features including forms, tables, search, and review workflows with permissions, validation, and resilient error handling. Coordinated rollout and production iteration using REST services, Playwright testing, and application diagnostics to improve maintainability and usability.
React.js
TypeScript
Rest API
Playwright
Forward Deployed Engineer
•
Middle
Fiserv
•
Full-Time
Built React and TypeScript interfaces for payments, accounts, customer service, and operations workflows for enterprise users. Integrated UI with REST APIs and backend services in Node.js and Python, implementing reusable component patterns for authentication, validation, partial responses, and failure states. Collaborated to resolve production issues and shipped improvements using Cypress/Playwright tests, API checks, and CI workflows with production observability.
React.js
TypeScript
Node JS
Python
Rest API
Cypress
Playwright
CI/CD
Full-Stack Software Engineer
•
Middle
Apple
•
Full-Time
Created React/TypeScript/JavaScript prototypes for web and cloud-backed workflows in collaboration with product, design, backend, and platform teams. Improved responsiveness and reliability through profiling, request optimization, caching, and staged rollouts backed by production diagnostics. Contributed to cloud delivery using AWS, Kubernetes/EKS, Terraform, CI/CD, and observability and AI-assisted log analysis to accelerate issue investigation.
React.js
TypeScript
JavaScript
AWS
Kubernetes
Amazon EKS
Terraform
CI/CD
Software Developer
•
Middle
Equiis
•
Full-Time
Developed responsive React and TypeScript web interfaces with reusable UI components, integrating GraphQL and REST API-connected workflows. Built web and mobile automation using Playwright, Cypress, Selenium, Appium, Espresso, and XCUITest, supporting reliable end-to-end testing. Worked with AWS and CI/CD tooling, including Jenkins and GitHub Actions, and supported cloud environments using Docker, Kubernetes, and Terraform.
React.js
TypeScript
GraphQL
Rest API
Playwright
Cypress
Selenium
Appium
XCUITest
Jenkins
AWS
GitHub Actions
Docker
Kubernetes
Terraform
CI/CD
Software Developer
•
Middle
Noon
•
Full-Time
Delivered React and Redux-based web experiences for commerce and operational workflows by integrating frontend components with REST services and backend data flows. Automated parts of cloud infrastructure and delivery pipelines using AWS, Terraform, Ansible, Kubernetes, and Docker. Supported performance and reliability work using k6 and JMeter, alongside automated testing and API-oriented debugging with Cypress and Playwright.
React.js
Redux
Rest API
AWS
Terraform
Ansible
Kubernetes
Docker
CI/CD
k6
JMeter
Cypress
Playwright
Software Developer
•
Middle
Webroot
•
Full-Time
Contributed to web application interfaces and security product workflows, including cross-browser behavior, API integration, and data validation with database-backed features. Worked across JavaScript and Java codebases, implementing automated testing and release automation. Supported monitoring and troubleshooting using Jenkins and Linux with performance and security scanning workflows involving REST/SOAP APIs and SQL-backed components.
JavaScript
OWASP ZAP
Selenium
TestNG
Jenkins
AWS
Linux
SQL
Rest API
SOAP
California State University (East Bay Campus)
Master's Degree •
Computer Science
Frontend Software Developer
•
Middle
NebuAd
•
Full-Time
Built analytics web interfaces using JavaScript and client-side UI technologies for dashboards, charts, tables, search, and interactive filters. Integrated browser experiences with server-side services and improved asynchronous data loading behavior. Focused on usability and reliability through iterative debugging and incremental feature delivery.
JavaScript
Senior Backend Developer
Confidence: High Data Platform
Backend-focused engineer (senior-level) with a strength for local-first, data-oriented tooling and demonstrable attention to data integrity and safety. The strongest proven skill is building a local synthetic scenario quality platform with careful schema migrations, signed replay artifacts, a safe SQLite job queue and benchmarking (see scenario_quality/engineering.py and scenario_quality/advanced.py). The public artifacts do not show production-grade service deployments, cloud infrastructure, or large distributed systems patterns such as durable, horizontally scaled queues or multi-service contracts.
API Design
3/10
How well APIs are designed
Minimal API design for a local dashboard and JSON endpoints; endpoints exist and are consistent but lack versioning, idempotency keys, explicit pagination, and a formal error contract.
Evidence
autonomous-scenario-quality-platform/scenario_quality/webapp.py: Handler.do_GET routes (/api/summary, /api/sample, /api/trends, /api/meta, /api/issues)
autonomous-scenario-quality-platform/scenario_quality/__main__.py: CLI exposes 'serve' that binds webapp.serve for serving the same API
Data Layer & Database
6/10
Working with databases
Conscious schema design with CREATE TABLE scripts, indexes, migration functions, and explicit transaction usage; shows schema evolution and data integrity checks though using SQLite for a local-first demo.
Evidence
autonomous-scenario-quality-platform/scenario_quality/advanced.py: migrate(db) defines multiple CREATE TABLE and INDEX statements (executions, inspections, repair_requests)
autonomous-scenario-quality-platform/scenario_quality/engineering.py: setup(db) creates replay_artifacts, jobs, repair_patches and commits; includes indexed columns
autonomous-scenario-quality-platform/scenario_quality/engineering.py: consume_jobs uses 'BEGIN IMMEDIATE' to claim jobs safely with sqlite transactions
Scalability & Performance
5/10
Handling load and speed
Design includes a queue/worker model and a local benchmark harness with thread-based concurrency and latency percentiles; suitable for local performance testing but limited for large-scale production (SQLite and local threads).
Evidence
autonomous-scenario-quality-platform/scenario_quality/engineering.py: queue_jobs and consume_jobs implement queue-based job claiming and worker logic
autonomous-scenario-quality-platform/scenario_quality/engineering.py: benchmark(path,count,concurrency) uses ThreadPoolExecutor and computes p50/p95/p99 latencies
System Architecture
5/10
Overall system structure
Reasonable module separation (core, advanced, engineering, security, webapp) and local-first constraints; shows thoughtful local-safety constraints but lacks evidence of multi-service contracts or production configuration/secret management beyond environment variables.
Evidence
autonomous-scenario-quality-platform/scenario_quality/core.py, advanced.py, engineering.py: clear functional separation of responsibilities
autonomous-scenario-quality-platform/scenario_quality/webapp.py: serve(host,port) enforces loopback-only binding and sets DB_PATH from env
Security & Auth
6/10
Protecting data and access
Good pragmatic security hygiene for a demo: HMAC signing for artifacts, CSRF protection for form endpoints, safe cookie attributes and content-security headers; token lifecycle and revocation are not implemented for production-grade auth.
Evidence
autonomous-scenario-quality-platform/scenario_quality/security.py: authorize, csrf_token, verify_csrf functions using hmac/secrets
autonomous-scenario-quality-platform/scenario_quality/webapp.py: sets HttpOnly SameSite cookie, Content-Security-Policy and X-Content-Type-Options; verifies CSRF token on POST
autonomous-scenario-quality-platform/scenario_quality/engineering.py: replay(db,...) enforces signing key presence and minimum length before signing artifacts
Reliability & Observability
5/10
Stability and monitoring
Basic observability and reliability: audit log entries, a /metrics-style endpoint and benchmark tooling are present, and careful DB transaction claims reduce race conditions; systematic retries, backoff, distributed tracing and alerting are not evidenced.
Evidence
autonomous-scenario-quality-platform/scenario_quality/core.py: audit(db,action,detail) writes audit_log entries used across the system
autonomous-scenario-quality-platform/scenario_quality/webapp.py: /metrics and other endpoints expose summary metrics; audit log is surfaced in UI
autonomous-scenario-quality-platform/scenario_quality/engineering.py: benchmark collects latencies and system metadata
Expertise
Python• Middle
Java• Middle
Databases & Vector Storage• Middle
Industries
Artificial Intelligence• Middle
Technologies
Node JS• since 2022 • Middle
Rest API• since 2009
GraphQL• since 2019
FastAPI
Lombok
Recommendations
- Own the next iteration of the scenario tooling by replacing local SQLite job claiming with a production-grade queue (e.g., RabbitMQ or Redis streams) and add idempotency and retry/backoff semantics.
- Expose the core functionality as a production REST service (FastAPI/uvicorn) with versioning, structured JSON error contracts, and OpenAPI documentation for consumers.
- Add CI/CD and containerization, plus integration tests that exercise DB migrations and end-to-end replay verification under realistic data volumes.
- Harden auth for production by introducing token lifecycle management, refresh and revocation, and integrate a secrets manager for signing keys.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle QA Engineer
Confidence: Medium SDET
SDET-focused QA engineer at an early-to-mid career level specializing in end-to-end web UI and API automation. The strongest proven skill is building maintainable UI page objects and API wrappers as shown by PythonSeleniumFramework/base/base_driver.py and Java-REST-Assured-Cucumber/src/main/java/utilities/RestAssuredExtensionv2.java. There is little public evidence of contract testing, performance/load engineering, CI workflow automation or rigorous mutation/property-based testing.
Test Automation Frameworks
5/10
Building automated tests
Test automation frameworks and fixtures are present with POM usage, a reusable BaseDriver and pytest/conftest integration; framework work is practical but conventional and resembles a developer-built demo rather than large-scale test infrastructure.
Evidence
PythonSeleniumFramework/base/base_driver.py
PythonSeleniumFramework/testcases/conftest.py
Java-Cucumber-POM/src/main/java/com/depop/pages/LoginPage.java
Test Coverage & Strategy
3/10
What and how to test
Test coverage shows a mix of happy-path and some negative/boundary checks (path/query parameter handling, explicit negative assertions, JSON schema validation) but lacks risk-based prioritization, mutation/property-based tests and systematic negative-path matrices.
Evidence
Java-REST-Assured-Cucumber/src/test/java/steps/GetPostsSteps.java
Java-REST-Assured-Cucumber/src/test/java/steps/POSTProfileSteps.java
PythonSeleniumFramework/testcases/test_searchflights.py
API & Integration Testing
4/10
Testing how parts work together
API integration work uses RestAssured wrappers, token handling and helpers for query/path params plus JSON schema validation; however there is no contract testing, testcontainers or simulated external-system logic visible.
Evidence
Java-REST-Assured-Cucumber/src/main/java/utilities/RestAssuredExtensionv2.java
Java-REST-Assured-Cucumber/src/main/java/utilities/RestAssuredExtension.java
Java-REST-Assured-Cucumber/src/test/java/steps/GetPostsSteps.java
Performance & Load Testing
Testing speed under load
Not evidenced in public code
Bug Reporting & Analysis
2/10
Finding and describing bugs
Reporting artifacts and hooks (Allure, html report hooks) exist which support test result capture, but there are no reproducible bug reports, root-cause analyses or tracked flaky-investigation artifacts.
Evidence
PythonSeleniumFramework/testcases/conftest.py
PythonSeleniumFramework/reports/allure-report/
CI Test Integration
3/10
Running tests automatically
Basic CI/test integration patterns are present locally - TestNG Cucumber runner, pytest report hooks and Allure attachments - but there are no CI workflow definitions, selective matrix runs, quarantine mechanics or advanced artifact-retention policies.
Evidence
Java-Cucumber-POM/src/main/java/com/depop/runner/TestRunner.java
PythonSeleniumFramework/testcases/conftest.py
Expertise
SDET & Test Engineering• Middle
Technologies
Python• since 2022 • Senior
JavaScript• since 2007 • Middle
Java• since 2020 • Senior
TypeScript• since 2019 • Senior
SQL• since 2009 • Junior
TestNG• since 2009
Selenium• since 2009
JMeter• since 2016
Cypress• since 2017
Playwright• since 2020
Appium• since 2019
Terraform• since 2016
Ansible• since 2016
GitHub Actions• since 2019
Datadog
Prometheus
Allure Reporting
GitLab CI
Jest
CI/CD• since 2016
Jenkins• since 2011
Git
AWS• since 2009
Docker• since 2016
Kubernetes• since 2016
Pytest
k6• since 2017
XCUITest• since 2019
Amazon EKS• since 2020
AWS Lambda
Amazon EC2
GitHub
GitLab
Amazon S3
Linux• since 2009
SOAP• since 2009
Recommendations
- Develop and harden API automation suites around the RestAssuredExtensionv2.java wrapper with explicit negative-path and idempotency tests.
- Invest in CI integration and flaky-test engineering - add workflow files, per-test artifacts and quarantine mechanics to reduce noise in pipelines.
- Add contract/schema testing (Pact/Schemathesis) or Testcontainers-based integration tests to improve confidence in backend changes.
- Introduce load/perf scenarios (k6/locust) and mutation or property-based tests for higher coverage of edge cases.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Junior Frontend Developer
Confidence: Low Generalist
Frontend QA Engineer (junior level) focused on end-to-end UI automation and test harnesses. The strongest proven skill is building and running automated UI test suites and reports as seen in CypressAutomation/package.json and the cypress support/pageObjects structure. There is little to no public evidence of production frontend architecture, accessibility engineering, measured performance optimization, or meaningful unit/integration test coverage for application code.
UI Component Architecture
1/10
How interface parts are built
Minimal evidence of deliberate UI component architecture or custom component design; repository contains end-to-end test scaffolding and a large third party report asset but no custom design-system, deliberate component boundaries, or custom lifecycle hooks authored for a production UI.
Responsive & Cross-browser
1/10
Works on all screens and browsers
No clear work on responsive layout strategy, container queries, RTL or cross-browser feature detection in authored files; only test/runner and report assets appear in the material provided.
Performance Optimization
1/10
Speed of the interface
No developer-authored performance work (bundle analysis, LCP/INP measurements, code-splitting or virtualization) is present; the only large JS is a bundled report viewer which is a third party asset.
Accessibility & Semantics
1/10
Usable for everyone
No evidence of deliberate accessibility work in original code (ARIA on custom widgets, focus management, accessibility tests); only third party report code is included in the human-authored set.
State Management & Data Flow
1/10
Managing data in the app
No evidence of advanced async state discipline in frontend code such as request cancellation, optimistic updates or state machines; available artifacts are test framework configs and a bundled report asset.
UX & Visual Polish
1/10
Look and feel quality
UX polish signals (skeletons, undo, measured perceived performance) are not present in developer-authored code; the repository is focused on automation and includes a third party report bundle rather than custom UX flows.
Technologies
Frontend
Redux• since 2016
React.js• since 2016
npm
JavaScript• mentioned only
Recommendations
- Use this developer to build and maintain E2E automation suites, page object models and test CI pipelines for web applications.
- Assign tasks to integrate test runs into CI/CD and to improve test reporting and flakiness handling (retries, isolation, parallelization).
- Have the developer implement Page Object based test coverage for new user flows and maintain Playwright/Cypress cross-browser test matrices.
- Avoid assigning large frontend architecture, performance optimization, or accessibility remediation work until there is clear evidence of experience in those areas.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: