Back to jobs

Head of Engineering

Creative ChaosRemote (Afghanistan, Albania, Algeria, American Samoa, Andorra, Angola, Anguilla, Antarctica, Antigua and Barbuda, Argentina, Armenia, Aruba, Australia, Austria, Azerbaijan, Bahamas, Bahrain, Bangladesh, Barbados, Belarus, Belgium, Belize, Benin, Bermuda, Bhutan, Bolivia, Bonaire, Sint Eustatius and Saba, Bosnia and Herzegovina, Botswana, Bouvet Island, Brazil, British Indian Ocean Territory, Brunei Darussalam, Bulgaria, Burkina Faso, Burundi, Cabo Verde, Cambodia, Cameroon, Cayman Islands, Central African Republic, Chad, Chile, China, Christmas Island, Cocos (Keeling) Islands, Colombia, Comoros, Congo, Congo, The Democratic Republic of the, Cook Islands, Costa Rica, Croatia, Cuba, Curaçao, Cyprus, Czechia, Côte d'Ivoire, Denmark, Djibouti, Dominica, Dominican Republic, Ecuador, Egypt, El Salvador, Equatorial Guinea, Eritrea, Estonia, Eswatini, Ethiopia, Falkland Islands (Malvinas), Faroe Islands, Fiji, Finland, France, French Guiana, French Polynesia, French Southern Territories, Gabon, Gambia, Georgia, Germany, Ghana, Gibraltar, Greece, Greenland, Grenada, Guadeloupe, Guam, Guatemala, Guernsey, Guinea, Guinea-Bissau, Guyana, Haiti, Heard Island and McDonald Islands, Holy See (Vatican City State), Honduras, Hong Kong, Hungary, Iceland, India, Indonesia, Iran, Iraq, Ireland, Isle of Man, Israel, Italy, Jamaica, Japan, Jersey, Jordan, Kazakhstan, Kenya, Kiribati, Kosovo, Kuwait, Kyrgyzstan, Lao People's Democratic Republic, Latvia, Lebanon, Lesotho, Liberia, Libya, Liechtenstein, Lithuania, Luxembourg, Macao, Madagascar, Malawi, Malaysia, Maldives, Mali, Malta, Marshall Islands, Martinique, Mauritania, Mauritius, Mayotte, Mexico, Micronesia, Federated States of, Moldova, Monaco, Mongolia, Montenegro, Montserrat, Morocco, Mozambique, Myanmar, Namibia, Nauru, Nepal, Netherlands, New Caledonia, New Zealand, Nicaragua, Niger, Nigeria, Niue, Norfolk Island, North Macedonia, Northern Mariana Islands, Norway, Oman, Pakistan, Palau, Palestine, State of, Panama, Papua New Guinea, Paraguay, Peru, Philippines, Pitcairn, Poland, Portugal, Puerto Rico, Qatar, Romania, Russian Federation, Rwanda, Réunion, Saint Barthélemy, Saint Helena, Ascension and Tristan da Cunha, Saint Kitts and Nevis, Saint Lucia, Saint Martin (French part), Saint Pierre and Miquelon, Saint Vincent and the Grenadines, Samoa, San Marino, Sao Tome and Principe, Saudi Arabia, Senegal, Serbia, Seychelles, Sierra Leone, Singapore, Sint Maarten (Dutch part), Slovakia, Slovenia, Solomon Islands, Somalia, South Africa, South Georgia and the South Sandwich Islands, South Korea, South Sudan, Spain, Sri Lanka, Sudan, Suriname, Svalbard and Jan Mayen, Sweden, Switzerland, Syrian Arab Republic, Taiwan, Tajikistan, Tanzania, Thailand, Timor-Leste, Togo, Tokelau, Tonga, Trinidad and Tobago, Tunisia, Turkey, Turkmenistan, Turks and Caicos Islands, Tuvalu, Uganda, Ukraine, United Arab Emirates, United Kingdom, United States Minor Outlying Islands, Uruguay, Uzbekistan, Vanuatu, Venezuela, Vietnam, Virgin Islands, British, Virgin Islands, U.S., Wallis and Futuna, Western Sahara, Yemen, Zambia, Zimbabwe, Åland Islands)Posted 1w ago
Creative Director
Full Time
Remote
Craft my tailored resume free

Free to start · No card

Job description

Job Summary:
Creative Chaos is looking for a Head of Engineering to lead our engineering organization and drive the technical direction, execution, and growth of our technology teams.

This is a senior leadership role for someone who can operate at both the strategic and technical level — shaping engineering practices and architecture while working closely with leadership, product, clients, and engineering teams to deliver high-quality software solutions.

What you own

The engineers. Everyone technical at Creative Chaos reports into you: hiring, the technical screen, performance, growth, and the decision that someone is not working out. Today they are spread across client accounts, and the account sets the priorities. You set the standard.

The bar. What Creative Chaos will and will not put its name on. AI standards, workflows and best practices, architecture review, code review, testing, security posture, infra, tools, and what qualifies as an exceptional working experience with a client. Today this is held informally by whoever is most senior on an account. Your job is to make it a standard, to coach and mentor toward it, and to hold it across every account whether or not you are in the room.

Who is on what. Staffing across accounts, including the bench. You own the assignment decisions and the utilization that follows from them.

The technical relationship with the client. You are the person who tells a client their architecture is wrong, and the person a client's CTO calls when they want a second opinion. Several of our engagements exist precisely because two or three consultants failed there first.

The hiring plan. What kind of engineers we need next week, next month, and over the next year, and how we find them. Our positioning depends on senior, AI-native engineers with excellent communication skills, and they are the hardest people in the market to hire.

The half of this job that is not technical

Roughly half of this role is standing in front of people and being believed.

You will spend a large part of your week explaining: to a client why their architecture will not hold, to an engineer why the work is not ready, to a room of thirty people how to actually work with AI agents instead of talking about them. Our clients are primarily US customers. They buy confidence as much as capability, and you are frequently the most senior technical person they will ever speak to.

You are also the coach. Training, workshops, and code review as teaching rather than as gatekeeping. The standard only holds if people want to meet it.

If you are the strongest engineer in the room but nobody seeks you out, this is not your role. We are weighting this equally with technical depth, and we will screen for it.

What you do not own

Contracts, invoicing, pricing, and the commercial relationship. Those sit with the Head of Engagements. You two will argue about staffing, and that argument is the point: one of you owns the client, one of you owns the quality, standards and work put out by the engineers.

The first 90 days

By day 30: you know every account, every engineer, and where the real quality risk sits. You have told us at least one thing about our delivery that we did not want to hear.

By day 60: AI standards are being implemented in engineering. You are running training sessions and workshops, and helping people in their respective areas.

Requirements

  • 8+ years building software; 3+ years leading engineers directly.
  • Experience running engineering across several simultaneous client engagements, or running an in-house org and understanding what changes when the work is someone else's business.
  • You still read code and review it. This is not a role where you stop being technical.
  • You have hired engineers, and you have let one go. Both matter.
  • Comfortable being the person who says the design is wrong, to a client, early.
  • Someone people listen to. You can hold a room, teach a workshop, and disagree with a client without losing them.
  • AI-native in practice, not opinion: you use coding agents daily and you have specific views on where they break. Much of our work now involves inheriting applications a client's own staff built with AI, with no governance, no security review, and one person who understands them.
  • Direct, written communication. Our clients are in the US and much of our team is not, so most decisions are made in writing and read hours later.
  • Useful, not required: distributed and offshore team leadership; heavy data and integration work against systems that do not want to be integrated (ERP, unstable APIs, no direct database access); experience taking a services business toward owning a product.

Originally posted on Himalayas

Prepare your application

Use the description above to assess your fit for Creative Chaos. This checklist is guidance from Resumize, rather than additional requirements from the employer. Imported listings can be shortened or change after collection, so confirm the complete description and current availability before sending an application.

Match requirements to evidence

Identify the responsibilities and skills the employer explicitly names. For each important requirement, choose one example from your work, education, training, or projects. Explain what you did, how you did it, and what changed as a result. Include a measurable outcome when you can support it. If you lack a requirement, describe related experience accurately instead of adding an unfamiliar skill to your resume.

Put the most relevant examples near the top of your resume. Keep job titles, dates, qualifications, and contact details consistent across your application materials. Use the employer’s terminology when it describes your experience accurately; a copied list of keywords does not explain your contribution. A short, specific bullet is easier to review than a paragraph that mixes several unrelated duties.

Check the working arrangement

Confirm the location, schedule, employment type, and any eligibility requirements on the employer’s site. A remote label does not establish worldwide eligibility or flexible hours. If compensation, benefits, equipment, travel, or contract duration are missing from this listing, write down your questions for the recruiter. Do not assume details from another opening at the same company apply to this role.

Review before submitting

Follow the employer’s requested file format and application instructions. Open your exported resume and check that its text is selectable, its sections read in order, and its links work. Proofread names, dates, and contact information. Share confidential work samples only when you have permission, and use an anonymized example when necessary.

Submit through a trusted employer or recruiting destination. If the original listing has disappeared, search the employer’s careers page for the title rather than assuming the vacancy remains open. Save the application date, job reference, and the version of your resume you sent. Those details help you prepare for a later conversation and avoid submitting conflicting information through several job boards.

Review your resume for writing and readability feedback, or browse other openings if this opportunity is unavailable.