Software Optimization Engineer
What you'll do
Make our systems faster and cheaper by figuring out what to delete.
Your job is finding bottlenecks, removing dead code, and optimizing databases.
The goal: Find the slowest parts and make them 10-100x better.
Day-to-day work
-
Finding what's slow:
- Profile apps to see where CPU, memory, and disk are getting hammered
- Look at slow database queries and fix them
- Find unused indexes and tables we can drop
- Spot heavy dependencies we can replace or just remove
-
Cleaning up code:
- Delete unused modules and dead code
- Simplify stuff that's more complicated than it needs to be
- Remove features nobody actually uses
- Turn messy legacy code into something readable
-
Making infrastructure cheaper:
- Cut server costs by using resources better
- Speed up deployments
- Clean up bloated configs
- Optimize caching and background jobs
-
Tools:
- Build your own profiling scripts (we don't use DataDog or New Relic)
- Use things like xhprof, strace, perf, and custom SQL analyzers
- Sometimes hook performance data into AI agents for automated cleanup
You'll probably like this if
-
You enjoy:
- Deleting code more than writing new code
- Finding database queries that's the slowest
- Making something way faster with barely any changes
- Reading logs and profiles to figure out what's actually wrong
- Making systems simpler, not more complicated
-
You have:
- At least 3-5 years of software engineering experience
- Solid Linux command line skills
- Done some work in Python, PHP, or similar languages
- Optimized SQL queries before (we use MySQL/MariaDB)
- Written shell scripts
- Made something measurably faster or cheaper
This probably isn't for you if
- You'd rather build new features than optimize old ones
- You need detailed instructions for everything
- You only want to use big enterprise tools
- Ambiguity makes you uncomfortable
- You like spending weeks analyzing before making any changes
- You get stuck in research mode instead of just trying things
- You need everything to be perfect before shipping
How we actually work
- Results matter: Make it cheaper, faster, better. In that order.
- Keep it simple: The simpler solution usually wins
- Ship small things quickly: we don't do month-long rewrites
- Show progress fast: We want to see improvements daily or every few days, not after weeks of silence
- Try it, measure it, fix it: Don't overthink. Run the experiment, look at the data, adjust.
- You own your work: find the problem, fix it, measure it, ship it
- Always ask: "Do we actually need this?"
- No BS: Small flat team, no micromanaging, no 10-page specs
Tech you should be comfortable with
You don't need to know everything, but you should be okay working with:
- Linux command line and basic system tools
- Python or PHP
- SQL, specifically MySQL or MariaDB
- Shell scripting
Nice to have:
- Profiling tools like xhprof, strace, perf, flamegraph
- Some experience with LLMs or AI agents (we use them occasionally)
- CI/CD and deployment stuff
- Git, Docker, basic infrastructure
What you get
- Your work matters: Your optimizations directly save costs and make things faster for users
- Good tools: Latest tech, alpha/beta access, decent hardware
- Room to grow: Tech lead, deep specialist, or start something up to you
- Global team: Smart people from all over + you'll work directly with founders/executives
- Freedom: Own your decisions, move fast