Independent engineering through Synko Software

Software gets complicated.

I help teams make it easier to build, evolve and ship.

Senior Software Engineer working across product, frontend architecture, full-stack development and technical ownership.

Tell me what you're trying to solveSee how I work
What teams feel

Requirements drift. Frontends get heavy. Delivery slows down.

  • Unclear ownership
  • Complex state
  • Manual setup
What Jean brings

Product sense, architecture judgment and implementation depth.

  • Sharper decisions
  • Cleaner boundaries
  • Working software
What problem are you trying to solve?

Hire the problem solver, not the resume.

This is the Superhuman-suite idea applied to a person: a product-like surface where each problem changes the evidence, decision and outcome.

Problem LensSimplify a complex frontend
Selected lens

Ship a product

You have a product direction, but the path from idea to production still needs shape.

Decision

Start by modeling the workflow, then choose the smallest architecture that can support real use.

Evidence
Orquesto

Product, backend, frontend and operational decisions handled end to end.

Manas

A practical product surface for content generation, review and reuse.

Outcome

A product that can be shipped, operated and improved without turning every change into a restart.

Selected lens

Simplify a complex frontend

Your frontend still works, but every new feature feels more expensive than it should.

Decision

Reduce orchestration, clarify state ownership and make the hard workflows easier to reason about.

Evidence
Plaenge

~80% improvement in critical workflows.

NAV Orchestrator

65% fewer redundant API requests, about 5.5M requests/month reduced.

Outcome

A frontend that is faster to change because the product model is clearer.

Selected lens

Modernize a legacy application

The product cannot stop, but the architecture needs to move out of its old constraints.

Decision

Plan migration around seams, compatibility and delivery pressure instead of a rewrite fantasy.

Evidence
Dasa Scheduling

Ongoing feature delivery while improving frontend structure.

Plaenge Migration

Roughly 2x faster delivery in the migration/rebuild context.

Outcome

A product that keeps serving users while the technical base becomes easier to evolve.

Selected lens

Add technical ownership

The team has capable people, but needs someone to connect product ambiguity with engineering choices.

Decision

Own the technical path, challenge requirements and turn ambiguity into executable decisions.

Evidence
Frontend platform decisions

Stronger patterns for teams working inside complex product constraints.

Product engineering ownership

Less handoff friction between product thinking and implementation.

Outcome

The team moves with more confidence because the trade-offs are named and carried.

Selected lens

Improve engineering velocity

Developers are spending too much energy on setup, repetition and workflow friction.

Decision

Build small internal tools where they remove real drag, not where they just look clever.

Evidence
create-dasa-mfe

More reproducible onboarding and less tribal knowledge.

Tic Task

Time logging reduced from minutes to seconds.

Outcome

Fewer repeated decisions, faster setup and more attention available for product work.

Selected lens

Bring in a senior engineer

You need a senior engineer who can understand the product, make decisions and ship.

Decision

Work across the problem, architecture, implementation and production feedback loop.

Evidence
Senior Software Engineer

A practical mix of implementation depth and product ownership.

AI-assisted engineering workflows

Useful automation, codebase navigation and product thinking support.

Outcome

Less translation between product and engineering, more momentum through ambiguity.

Evidence mode

I've worked on this kind of problem.

The site keeps the claim and the proof close together. No portfolio theater, no inflated numbers, just context, decision and outcome.

Plaenge

A commercial workflow where complex screens had become expensive to operate and evolve.

Outcome

~80% improvement in critical workflows.

Performance work tied to frontend architecture and state model simplification.

NAV Orchestrator

A healthcare microfrontend platform with repeated requests and difficult coordination.

Outcome

65% fewer redundant API requests, about 5.5M requests/month reduced.

Request orchestration, frontend systems thinking and measurable platform impact.

65%fewer redundant API requests
5.5Mrequests/month reduced, approximately
80%critical workflow improvement, approximately
2xdelivery acceleration in migration context, roughly
Engineering Diff

Before and after, without pretending every decision was perfect.

Before

  • complex state orchestration
  • expensive renders
  • unclear ownership

After

  • simpler state model
  • clearer boundaries
  • optimized rendering
Decisions I've had to make

Complex orchestration to simpler state

Performance issues often look technical but start as product modeling problems.

Trade-off

Removing abstraction can be harder than adding it because teams are used to the existing shape.

What I'd do differently

I would create smaller diagnostic checkpoints before the larger architecture shift.

Things I build

Products and tools that exist because a workflow needed to be better.

Orquesto

Production SaaS for independent consultants, built from zero.

Product, full-stack implementation and operations.

Tic Task

Time logging integration between Taskweb and Senior.

Reduced a repeated workflow from minutes to seconds.

Manas

Instagram content editor and generator for brand-consistent content.

Practical AI-assisted workflow design without theatrical positioning.
Work with me

If the problem is "simplify a complex frontend", I can help you shape the work.

Available for remote PJ contracts, project-based engagements and embedded senior engineering work.

Embedded Senior Engineer

For teams that need a senior contributor inside the delivery rhythm.

Technical Lead / Product Engineering

For teams that need architecture, trade-offs, standards and delivery direction.

Project Engagement

For MVPs, modernization, internal tooling and scoped product work.

Engagements can be contracted through Synko Software and Innovation, my Brazilian software company.
Tell me what you're trying to solve
About
Brazil. Remote. Working internationally.

I tend to gravitate toward messy problems: products that need to ship, systems that became difficult to evolve, or teams that need stronger technical ownership.

I work across product and engineering, which usually means understanding the problem before deciding what should be built. The stack matters, but it is not the identity.

TypeScriptReactNode.jsGraphQLPostgreSQLArchitecture