</> Engineer · One Discipline

$ one_word
--engineer

Backend, frontend, infra, data, ML, mobile, security, QA. Most companies hire 6 specialists or route every change through a tech lead. I am the entire stack in one engineer.

Book a Call --list-roles
~/disciplines/engineer
28+
dev roles covered
1
engineer (me)
0
tickets to file
5x
faster ship velocity
inside one engineer

One title. Twenty-eight+ jobs.

Each one is normally a separate hire, a separate squad, a separate Jira board. I do them all.

// 01
Backend Developer
APIs, services, business logic, databases.
// 02
Frontend Developer
React, Vue, Tailwind, Next.js, hydration.
// 03
Full-Stack Developer
End-to-end features, top to bottom.
// 04
Mobile Developer
iOS, Android, React Native, Flutter.
// 05
DevOps Engineer
CI/CD, deploys, pipelines, automation.
// 06
SRE
Reliability, SLOs, on-call, incident response.
// 07
Cloud Engineer
AWS, GCP, Azure, Terraform, IaC.
// 08
Platform Engineer
Internal tooling, dev experience, abstractions.
// 09
Infrastructure Engineer
Networking, VPCs, load balancing, scaling.
// 10
Data Engineer
ETL, pipelines, warehouses, lakes, streaming.
// 11
ML Engineer
Training, serving, MLOps, feature stores.
// 12
AI / LLM Engineer
Agents, RAG, prompt engineering, evals.
// 13
Database Engineer
Schema, indexing, query plans, replication.
// 14
API Engineer
REST, GraphQL, gRPC, webhooks, versioning.
// 15
Integration Engineer
Third-party APIs, ERPs, CRMs, payments.
// 16
Security Engineer
Authn/authz, secrets, audits, hardening.
// 17
QA / Test Engineer
Unit, integration, E2E, regression.
// 18
Automation Engineer
Bots, scrapers, scripts, scheduled jobs.
// 19
Performance Engineer
Profiling, latency, caching, scaling.
// 20
Software Architect
System design, trade-offs, boundaries.
// 21
Solutions Architect
Cross-system designs, integrations, SLAs.
// 22
Tech Lead
Decisions, reviews, direction, ownership.
// 23
WordPress / CMS Dev
WP, Webflow, Shopify, themes, plugins.
// 24
Embedded Engineer
Firmware, microcontrollers, IoT devices.
// 25
Browser Ext / Plugin
Chrome, Edge, Firefox, content scripts.
// 26
Build / Release Engineer
Versioning, packaging, rollouts, hotfixes.
// 27
Refactoring Specialist
Legacy cleanup, dead code, debt reduction.
// 28
Code Reviewer
Standards, patterns, mentorship, taste.
// 29
Systems Engineer
OS-level, daemons, services, low-level glue.

// Most companies juggle 6+ of these between squads, on-call rotations, and a tech lead. Most never ship in a straight line.

the hidden cost

Squads + tickets. Or one engineer.

The shape of your dev team decides whether code ships today or three sprints from now.

Traditional team

// slow path
You
PM / Jira
Tech Lead
Backend
Frontend
DevOps
Data
QA
  • xEvery change becomes a Jira ticket
  • xCode review queues block delivery
  • xCross-squad work means cross-quarter waits

AnalyticLancer

// fast path
You
</> The Engineer
backend · frontend · infra · cloud · data · ML · mobile · security · QA · & more
  • okOne engineer owns the whole stack
  • okNo queues, no tickets, no review backlog
  • okIdea to deploy in hours, not sprints
no middle layers

Sentences I will never say.

Each one is a hidden delay. Each one disappears with one engineer.

~/killed-sentences.log
# "That needs a ticket on the backend team."
# "Frontend isn't in our scope this sprint."
# "DevOps is on-call rotation, file a request."
# "The data team owns that pipeline."
# "Security review will take 2 weeks."
# "Mobile is a different roadmap entirely."
# "Tech lead needs to approve before merge."
# "QA hasn't picked up the test plan yet."
# "Refactor is a Q3 initiative."
# "That third-party integration is out of scope."
echo "killed: 10"
time saved

One feature. Two timelines.

Traditional team

// 4 to 8 sprints
  • S1.Refine ticket. Wait for prioritization.
  • S2.Backend design doc. Tech lead review.
  • S3.Backend dev. PR review queue.
  • S4.Frontend dev picks it up next sprint.
  • S5.DevOps adds infra changes.
  • S6.QA writes E2E tests.
  • S7.Security review.
  • S8.Release window. Deploy.

AnalyticLancer

// 1 to 5 days
  • D1.You describe the feature. I scope it live.
  • D1.Backend, schema, and API done same day.
  • D2.Frontend wired and styled.
  • D3.Infra and deploy pipeline updated.
  • D4.Tests, security checks, edge cases.
  • D5.Shipped to production.
outcome

Ship faster. Own the whole stack.

5x
// faster ship velocity
28+
// roles in one
100%
// stack ownership
0
// tickets to file

Skip the queue. Ship with one engineer.

// no PM gate, no tech-lead bottleneck, no cross-squad waits. one engineer. one stack. one deploy.

Book a Call --see-services

// related routes

Surfaces: design · Truth: analyze

refactor / takeover · greenfield $500 day

huge_projects · au_virtual_assistant

contact_me — Melbourne