[da.]

Daniel
Atkinson.

Senior Frontend Engineer

I build production web and mobile applications with React, TypeScript, Next.js, React Native, and AWS.

7+ years of experience across frontend architecture, API integrations, technical scoping, and project delivery.

View projects View résumé
React + TypeScript
Daniel Atkinson
DANIEL ATKINSON
{ } Web & mobile apps
Technical experience

01 ABOUT

Frontend-focused
software engineer

Since 2019, I’ve worked across web, mobile, desktop, cloud infrastructure, and AI-enabled products. I specialize in React and TypeScript, with experience in APIs, authentication, AWS, architecture, scoping, and delivery.

On small and larger teams, I own features, review code, help set technical direction, and work directly with clients and stakeholders.

UIAPIAIAWSCI

Frontend

State management, component architecture, accessibility, testing, and performance.

ReactTypeScriptNext.jsReact NativeVue
7+ years

experience

35+

web & mobile apps

40+

projects scoped

02 PROJECTS

Selected work

Projects that show the kind of frontend architecture, integration work, production debugging, and technical leadership I’ve handled.

Tomb Raider — Frontend architecture and performance

High-traffic public website built with Next.js, Contentful, Tailwind, and GSAP, where I led frontend architecture and rendering strategy.

Key decisions & result

Key decisions

  • Chose Next.js over our usual React + Vite setup because SEO, initial load performance, and public traffic were important.
  • Used ISR for shared public content, request-time SSR for protected admin data, and client-side fetching for authenticated account data.
  • Introduced Tailwind to improve design consistency and iteration speed across the team.
  • Reworked an initially ambitious Three.js concept into a lighter GSAP-based parallax experience when the project budget changed.
  • Later fixed authentication/profile-state race conditions by separating loading, failure, and genuinely missing user data.

Result

  • The site handled 10,000+ concurrent users without major frontend performance issues.
  • Next.js and Tailwind became standard choices for similar public-facing projects afterward.
Next.jsSSR / ISRContentfulPerformanceFrontend Architecture

Parking Analytics — Working with unreliable external data

Operations and analytics platform for parking facilities, integrating occupancy and device data from an existing INDECT system.

Key decisions & result

Key decisions

  • Helped define requirements and estimate work where the upstream integration provided periodic snapshots rather than authoritative parking sessions.
  • Identified that polling every few minutes did not guarantee the upstream data itself was fresh.
  • Worked through edge cases around occupancy timing, stale updates, inconsistent device refresh rates, and unreliable sensor behavior.
  • Helped identify repeated empty/occupied flipping as a device-health issue rather than legitimate parking activity.
  • Supported the design of configurable toggling detection so unreliable sessions could be flagged or excluded from accuracy-sensitive reporting.

Result

  • The team was able to deliver useful occupancy and reporting features despite imperfect upstream data.
  • Client expectations around arrival/departure precision were reset to match what the integration could actually support.
  • Device-health monitoring improved confidence in downstream analytics.
Data IntegrationAnalyticsDevice HealthRequirementsUnreliable Data

SpeedyEats — Securing an inherited AWS environment

A production incident in an inherited AWS environment exposed broader security problems beyond the initial SES suspension.

Key decisions & result

Key decisions

  • Investigated the incident across AWS, Apache, Laravel, and PHP logs rather than treating SES as an isolated email issue.
  • Found that sensitive server files had been exposed, including application configuration and source-related files.
  • Rotated exposed credentials and removed long-lived IAM keys from the EC2 instance.
  • Switched AWS access to role-based EC2 permissions, restricted SES access, and moved secrets into AWS Secrets Manager.
  • Brought in the cybersecurity team once the scope was clear and implemented much of the remediation they validated or recommended.
  • Worked through multiple rounds with AWS Support to demonstrate the environment had been hardened.

Result

  • Unauthorized email sending stopped.
  • SES was reinstated.
  • The hardened AWS configuration remains in place, and there have been no repeat incidents from the same class of issue.
AWSIncident ResponseIAMSecrets ManagementProduction Debugging

CENTERLINE — TypeScript guidance and team standards

Architectural project management software with roughly 10 developers, focused heavily on document workflows and review cycles.

Key decisions & result

Key decisions

  • Reviewed a large amount of frontend work and became one of the people developers came to for React, TypeScript, and debugging help.
  • Repeatedly addressed misuse of any, non-null assertions, broad union types, excessive optional chaining, and unnecessary type casts.
  • Focused code-review feedback on understanding why TypeScript was raising an issue rather than simply suppressing the error.
  • Encouraged developers to model real application states with narrower, more meaningful types.
  • Walked developers through a consistent debugging process using logs, browser console, Inspect Element, network state, and breakpoints.
  • Helped standardize Prettier across the team and later adopted ESLint rules so some conventions were enforced automatically.

Result

  • Developers generally incorporated the feedback, and I saw fewer repeated TypeScript issues in later PRs from the same people.
  • Code reviews became less focused on formatting and recurring conventions and more focused on correctness, state modeling, and maintainability.
TypeScriptReactCode ReviewESLintTechnical Leadership

AI work

Built AI assistant interfaces using OpenAI APIs, LangChain/LangGraph, SSE, realtime voice, permission-scoped database querying, and interactive charts.

03 EMPLOYMENT

Full résumé

Experience

Vigilus / May 2019 — present

At Vigilus, my responsibilities span frontend architecture, delivery, code review, and technical leadership.

I’ve also conducted 80+ technical interviews as part of the team’s hiring process.

010203
2025–PresentPrincipal Frontend Engineer

2025–Present

Lead frontend architecture and technical direction across web and mobile projects. Scope and estimate work, review code, support developers, and contribute across APIs, cloud infrastructure, and AI-enabled features.

2022–2025

Owned frontend implementation across React, React Native, and Next.js projects, integrated APIs and authentication, contributed to AWS infrastructure, and helped coordinate multi-developer projects.

2019–2022

Built and maintained web, mobile, and desktop applications across React, React Native, and .NET projects.

</>

BS, Computer Science

Louisiana State University · 2017–2021

04 CONTACT

Get in touch

I’m open to senior frontend, full-stack, and frontend-heavy software engineering roles.

daniel@danielatkinson.dev