The New Guilds: Who Gets to Define a Profession?

The architect they would not admit

Florence Taylor learnt architecture at night.

After her father died in 1899, she needed to support two younger sisters. She found work in an architect's office and enrolled at Sydney Technical College. By 1907 she had completed her articles, risen to chief draftsperson in the office of the prominent architect John Burcham Clamp and begun designing houses. Clamp nominated her for associate membership of the Institute of Architects of New South Wales.

The Institute rejected her.

The surviving accounts do not give us minutes in which the all-male committee explains its vote. Taylor later said she had been excluded because she was a woman. What can be established is already enough. She had studied, worked, designed and secured the backing of a senior practitioner. The occupational association still withheld recognition. It invited her to join only in 1920.

Taylor did not wait outside the door. With her husband George, she built a publishing company whose journals shaped debate about architecture, engineering, construction and town planning for decades. Her papers now sit in the State Library of New South Wales. The Australian Dictionary of Biography remembers her as an architect and publisher.

Her rejection exposes several answers to the question who gets to define a profession? Taylor's college could recognise learning. An employer could recognise her work. Clients could commission designs. A practitioner body could refuse membership. Colleagues and later historians could still call her an architect.

The state eventually added another answer. Today, the NSW Architects Registration Board says that only people on its register may use the title architect in the regulated context. Registration now joins qualification, practical experience and examination to a code of conduct, continuing development, insurance, complaints and discipline.

Yet the word has also escaped the building site. Amazon Web Services offers an AWS Certified Solutions Architect credential. Microsoft offers an Azure Solutions Architect Expert certification. Neither company asks the NSW board to define the role. Each writes its own job description, body of examinable knowledge, renewal rules and badges.

Three institutions can therefore look at three people using the same word and make different claims. One says: this person may use a legally protected title in this jurisdiction. Another says: this person passed our assessment about designing systems in our cloud. A third may say only: this colleague has earned our trust to approve changes to a shared technical project.

Calling all three “modern guilds” is tempting. The comparison becomes useful only after the temptation is slowed down.

A profession is an arrangement, not a compliment

In ordinary speech, professional can mean paid, skilled, dependable or merely well presented. None of those meanings explains why some occupations can control a title, set entry conditions, discipline members or persuade employers to demand a credential.

Sociologists have long resisted the search for one timeless checklist. In 1964, Harold Wilensky asked whether everyone was becoming professionalised and warned that loose criteria such as specialisation, standards and certification could hide new institutional forms. Andrew Abbott later shifted attention from traits to jurisdiction: the claim of an occupational group to diagnose a problem, perform work, judge its quality and control who may speak with authority about it.

Jurisdictions are settlements rather than natural property. They can be recognised in law, in workplaces and in public understanding. They can divide. Doctors may retain one task while technicians, nurses, software or clients take another. A new technology can create work before any occupation has secured it. A state may protect a title while leaving adjacent tasks open. An employer may ignore a voluntary certificate, then make it a hiring requirement next year.

This page therefore uses profession carefully: an institutionalised occupational claim to specialised knowledge, standards, jurisdiction and obligations. It does not assume that every profession holds the same powers, or that an occupation becomes better as it accumulates gates.

The distinction matters because a gate can do more than one thing. It can make competence easier to inspect, organise learning, protect clients and give practitioners a shared identity. It can also charge for entry, privilege one pathway, impede mobility, exclude credible outsiders or transfer authority to whoever owns the scheme.

The OECD's 2024 review of professional and occupational regulation holds both sides together. Regulation can respond to risks and information problems. Restrictions can also reduce competition and mobility when they travel beyond what the risk requires. The answer is not to assume that every gate protects the public or that every gate is a cartel. The gate has to be inspected.

Ten questions for any gate

The medieval guild often bundled functions that now belong to different bodies. It might arrange training, inspect work, recognise mastery, control a market, support members, discipline misconduct, represent a craft and give its name social force. As the history of the medieval guild shows, no single European guild held that whole bundle in the same way.

The same caution belongs in the present. Instead of asking whether an institution is a guild, ask:

1. Knowledge: Who defines the body of knowledge and recognised work?
2. Title: Who controls the occupational name?
3. Entry: Who examines entrants or verifies experience?
4. Renewal: Must recognition be maintained?
5. Conduct: Is there a code, complaint route or disciplinary power?
6. Consequence: Does the gate control legal practice, procurement, hiring, project permission or reputation?
7. Government: Do practitioners, a state, an employer, a vendor or a parent organisation govern it?
8. Record: Who owns the credential, register and underlying data?
9. Cost: Who pays to enter and remain recognised?
10. Challenge: Can a decision be appealed, transferred or contested?

These are not ingredients in a score. Six ticks do not make a body 60 per cent guild. One institution may resemble a guild in its control of knowledge and identity while having no market power. Another may lack membership and welfare functions but exercise a harder commercial gate through a dominant ecosystem.

The profile is the result.

IAAP and the work of making a field legible

In late 2013, Microsoft's chief accessibility officer, Rob Sinclair, wrote about a meeting of people trying to form the International Association of Accessibility Professionals. Their problem was recognisable in many young fields. Organisations needed accessibility expertise. People arrived through design, engineering, disability advocacy, policy, testing, education and law. Employers had no shared way to judge the claim accessibility professional. Practitioners lacked a common occupational home.

Sinclair's account was written before the association could prove what it would become. Its value is historical. The founders proposed to organise networking, education and certification so that expertise could be recognised and kept current. IAAP launched in 2014 and later became a division of the Global Initiative for Inclusive ICTs, or G3ict.

The current certification system makes part of the field unusually inspectable. IAAP says its programmes are based on job tasks that a minimally qualified candidate should be able to perform. The foundational Certified Professional in Accessibility Core Competencies, or CPACC, covers disability, accessibility and universal design, and accessibility-related standards, laws and management strategies. The technical Web Accessibility Specialist and Accessible Document Specialist credentials cover narrower practices. Passing both CPACC and the web-specialist examination produces the higher CPWA credential.

The distinction between constructs and evidence matters here as much as it does in any assessment. CPACC is a 100-question, closed-book examination of broad conceptual knowledge. IAAP explicitly says that the holder may manage or support accessibility without personally implementing every technical task. The credential supports the claim its content and assessment can carry. It does not turn one result into proof of every accessibility capability.

IAAP has built many functions associated with a profession:

• published bodies of knowledge and content outlines;
• experience expectations and examinations;
• three-year certification with education-credit renewal;
• an opt-in directory of certified people;
• a code of conduct;
• complaint, sanction and appeal procedures;
• committees that approve the body of knowledge and job analysis.

Its Certification Committee is formally autonomous for essential certification decisions and separated from IAAP's training functions. IAAP's rules require at least one certified member and a public or non-employer consumer representative on the committee. Those are recognisable attempts to prevent the body that teaches from simply selling its own test.

This is substantial practitioner-oriented organisation. Its limits are equally important.

IAAP cannot stop an uncertified person from calling themselves an accessibility professional. It cannot grant a legal right to work, compel employers to use its directory or remove someone from the field. Conduct sanctions can affect membership or certification; they do not cancel an occupation. The association is also nested inside G3ict governance rather than owned collectively by everyone who performs accessibility work.

IAAP is guild-like in its effort to define knowledge, recognise practitioners, maintain identity and discipline use of its own credential. It is unlike a statutory guild in title and market control. Whether employers treat its credentials as valuable, optional or mandatory is a separate labour-market question that the scheme's design cannot answer by itself.

The cloud vendors that define their own architects

AWS and Microsoft solve a different recognition problem.

A cloud system can combine identity, networks, storage, compute, data, security, resilience, monitoring and cost. Employers and clients need people who can turn those services into a coherent design. The vendors need customers and partners who can use fast-changing products successfully. Both companies therefore define a solutions-architect role and certify it.

The AWS Solutions Architect Associate exam guide organises the claim around secure, resilient, high-performing and cost-optimised architectures built with AWS services and the AWS Well-Architected Framework. The credential page describes a 65-question examination and three-year validity. Recertification requires the current exam or a specified higher credential.

Microsoft's Azure Solutions Architect Expert requires the Azure Administrator Associate credential and the AZ-305 examination. The measured work includes identity and governance, data storage, business continuity and infrastructure. Microsoft updated the English version of the certification in April 2026. Eligible role-based Microsoft certifications last one year and renew through a free, open-book online assessment.

Those changing requirements are not a defect hidden in the small print. They express the nature of the claim. A vendor credential is attached to a technical environment that its owner changes. Microsoft can retire a certification when a role or product loses relevance. AWS can update the services within an exam. The badge is current only under the issuer's rules.

The vendors also give the credentials consequences beyond a person's CV.

AWS tells certification holders that, with consent, their credentials can be associated with an employer and become a factor in the employer's AWS Partner Network tier. Microsoft's Partner Center counts named employee certifications towards the skilling component of a Solutions Partner designation. That designation also requires performance and customer-success evidence, so certified staff do not prove the organisation's complete capability. Still, a person sitting an exam can help unlock a badge and benefits for a company.

This is a modern gate with no medieval counterpart in exactly the same shape. The same organisation:

• owns the technical ecosystem;
• defines the role inside it;
• writes or commissions the examination;
• controls the digital record and brand;
• sets expiry and retirement;
• links individual results to partner status;
• sells the services around which the role is built.

Practitioners contribute expertise to exam development, but they do not collectively govern AWS or Azure. A candidate can challenge a Microsoft exam item within a bounded process; they cannot vote to keep a credential Microsoft has decided to retire. Portability depends on whether another employer, client or ecosystem recognises the claim.

The vendor gate may be weaker than law because it cannot stop someone working as a solutions architect. It may be stronger than a voluntary professional certificate inside a particular commercial network. A consultancy seeking partner status, a procurement panel looking for vendor evidence or a hiring manager screening cloud roles can make it consequential.

This is why a credential has to be inspected by issuer, evidence and consequence. Certified architect sounds grand. The useful question is: certified by whom, to design what, under which current version, and allowed to do what next?

The state and the protected architect

New South Wales places architect in another institutional world.

The Architects Act 2003 gives public authority to a register and regulator. An individual using the protected title must be registered. A business describing itself as an architect must nominate a registered architect responsible for its architectural services.

The pathway joins several forms of evidence. The Architects Accreditation Council of Australia's National Standard of Competency distinguishes the graduate, the candidate for registration and the architect after registration. The usual route requires a recognised professional qualification, broad practical experience and the Architectural Practice Examination, or an approved alternative pathway.

Registration is continuing status, rather than a certificate placed permanently on a wall. NSW architects are bound by a code of conduct. They must maintain professional indemnity insurance appropriate to their services and undertake continuing professional development. Members of the public can inspect the register, make a complaint about professional conduct and search published disciplinary action.

Public power changes the consequence. IAAP can withdraw an IAAP credential. Microsoft can invalidate a badge. The NSW regulator can affect the legal use of a title in its jurisdiction. The Act also creates review routes for named registration decisions. Authority, duty and challenge are written into law rather than only into a programme agreement.

The boundary needs equal emphasis. NSW protects the title. This article does not claim that every act of building design is reserved exclusively to architects, or that registration proves excellence in every project. The public register establishes current professional standing under a defined scheme. The code and complaints process create accountability. Their effects still depend on enforcement, proportionality and the quality of the underlying standards.

Florence Taylor's history prevents a celebratory account of closure. Professional recognition can protect clients and make responsibility visible. It can also reproduce the judgement of insiders about who belongs. Modern law has changed the gate that excluded her, but every rule about qualification, experience, fees, recognition and mobility still distributes opportunity.

The history of apprenticeships and dual vocational training shows the same institutional truth from another angle: a route is never merely a curriculum. Employers, schools, governments, examining bodies and occupational rules decide which learning becomes socially usable.

Kubernetes and authority without an occupational licence

Now consider a gate built almost entirely from work observed in public.

Kubernetes is open-source software for managing containerised systems. Anyone can report a problem, propose a change, review code or improve its documentation. Many contributors do this as paid work; others participate through employers, independently or in spare time. The project does not ask a newcomer for a Kubernetes profession certificate before accepting a pull request.

It still has ranks of trust.

The Kubernetes community encourages sustained contributors to become members. Special interest groups and repositories recognise reviewers and approvers. Public OWNERS files name people trusted with parts of the codebase. Reviewers examine quality and correctness. Approvers make a broader judgement about whether a change fits dependencies, compatibility and project direction. In the documented two-phase process, their decisions help determine whether code can merge.

Authority is earned through contribution, peer sponsorship and continuing familiarity with the work. It is also bounded. A person may be an approver for one area and a newcomer in another. Inactive reviewers can be removed or moved to emeritus status. Leadership lives in project governance and auditable files, not in a certificate that follows the person everywhere.

This arrangement has guild-like elements:

• learning through participation in real work;
• reputation built among experienced peers;
• progressive access to consequential decisions;
• shared technical standards and conduct expectations;
• a collective identity;
• removal from active authority when participation lapses.

It lacks other elements. Kubernetes does not control the title software engineer, license employment or claim jurisdiction over all cloud-native work. There is no occupation-wide examination. An OWNERS entry is powerful inside the project and incomplete outside it. An employer may value it, but the project does not define the person's job level or wages.

This low-formality case is not without gates. Peer sponsorship can be difficult to secure. Contribution requires time, access, language, confidence and knowledge of a complex social and technical system. Public rules make the path inspectable; they do not prove that every credible contributor experiences it equally.

The important distinction is between authority over shared work and authority over an occupation. Kubernetes grants the first. It does not pretend to grant the second.

Four profiles, no league table

Professions · Gatekeepers · Scope

How guild-like is it?

The useful answer is a profile of powers and limits, never a total score. Four institutions can resemble a guild in different functions while governing different constituencies.

Professional associationIAAPShow detailsHide details

Reach: Defines accessibility knowledge, awards and renews its credentials, publishes rules and can sanction credential use.

Limit: Cannot protect the occupational title or grant a legal right to practise.

Challenge: Certification application and policy appeal routes

Vendor ecosystemAWS / MicrosoftShow detailsHide details

Reach: Defines product-specific roles, exams, badges, renewal and partner-programme consequences.

Limit: Authority is commercial and ecosystem-bound, not statutory occupational control.

Challenge: Vendor exam, credential and partner support processes

Statutory regulatorNSW architect registrationShow detailsHide details

Reach: Protects the architect title, maintains a public register and connects conduct to statutory discipline.

Limit: Jurisdiction-specific title regulation does not reserve every act of design.

Challenge: Complaints, statutory review and tribunal or court routes

Open-source communityKubernetesShow detailsHide details

Reach: Confers project roles through contribution, peer sponsorship and repository-local responsibility.

Limit: Project authority does not license employment or certify general software capability.

Challenge: Public project governance and community review

Function-by-function profiles of four modern gatekeepers

Question	IAAP	AWS / Microsoft	NSW architect registration	Kubernetes
Knowledge	Body of knowledge	Product-role blueprint	National competency standard	Contribution practice
Title	Credential post-nominal	Vendor credential title	Architect title protected	Project role only
Entry	Application and examination	Exam prerequisites by credential	Qualification, experience and exam	Contribution and sponsorship
Renewal	Continuing education and renewal	Vendor renewal cycle	Annual registration and CPD	Continuing activity
Conduct	Association rules	Programme and exam policies	Statutory code and discipline	Community code and role review
Consequence	Voluntary recognition signal	Ecosystem and partner gate	Legal title and public standing	Repository-local authority
Governance	Association inside G3ict	Vendor-owned programme	Statutory board	Open project governance
Record	Certification directory	Vendor credential record	Public statutory register	Public repository files
Cost	Application, exam and renewal	Exam and programme costs	Education, exam and registration	Time and contribution
Challenge	Certification application and policy appeal routes	Vendor exam, credential and partner support processes	Complaints, statutory review and tribunal or court routes	Public project governance and community review

Four profiles and a ten-row matrix compare IAAP, cloud-vendor credentials, NSW architect registration and Kubernetes roles across knowledge, title, entry, renewal, conduct, consequence, governance, record ownership, cost and challenge. No total, percentage or ranking is calculated.

The table refuses a winner because the cases do different jobs. NSW registration has the strongest title consequence. Kubernetes has the most direct link between observed contribution and project authority. IAAP has the clearest attempt to build a profession across employer and jurisdiction boundaries. The vendors can change a role quickly and connect individual credentials to commercial networks.

Those observations are not quality rankings. They describe institutional reach.

Where the guild analogy earns its keep

The analogy is useful first as a memory aid. The medieval guild reminds us that training, examination, identity, discipline, welfare, market access and political voice can be joined or separated. A modern certificate is easier to understand when the reader asks which of those functions it actually carries.

It is useful second because it exposes power behind apparently neutral standards. Someone chooses the tasks in a job analysis. Someone decides what counts as enough experience. Someone sets the fee and controls the database. Someone can retire a credential, reject an application, withhold sponsorship or publish a disciplinary finding.

It is useful third because it keeps recognition separate from capability. The vocabulary of capability distinguishes knowledge, skill, competence and expertise. An institution sees only selected evidence. A multiple-choice examination, supervised project, public contribution history and statutory practice interview reveal different things. The gate's prestige cannot make its evidence travel further.

Finally, the analogy makes exclusion part of the design question. Florence Taylor's association saw her work and still refused her. Today's exclusions may operate through cost, language, inaccessible testing, required experience, geographical recognition, employer sponsorship, unpaid contribution time or dependence on one vendor's ecosystem. A gate should state what risk it addresses, why its evidence is relevant and how an excluded person can challenge or take another route.

Where it breaks

The analogy breaks when it implies direct descent. AWS certification did not grow out of a medieval craft fraternity. Kubernetes OWNERS files are not electronic masterpiece examinations. NSW registration belongs to modern public law. IAAP emerged from disability rights, technical standards and a globalising field of practice.

It breaks when every collective body is assumed to be practitioner self-government. A vendor credential may use subject-matter experts while leaving final authority with the company. A statutory board may include practitioners while exercising powers granted by the state. A community may be open to participation while giving a small number of maintainers decisive project authority.

It breaks when all closure is treated alike. A legal title offence, a procurement requirement, a partner-programme score, a hiring filter and a reputation signal impose different constraints. Their remedies also differ. One may go to a tribunal. Another goes to a certification appeal form, vendor support queue, employer or project discussion.

It breaks most dangerously when the romance of craft hides the people outside the gate. Historical guilds protected some members while excluding many workers. Modern institutions can widen recognition for people whose expertise was previously hard to see. They can also create a new fee, badge or sponsorship requirement between a capable person and work.

There is no honest way to decide from the word profession alone.

Who gets to define it?

No single institution does, at least not everywhere and for all purposes.

Practitioners define knowledge and identity. Education providers organise learning. Certification bodies examine bounded claims. States decide which titles or practices need public authority. Employers and procurement systems turn optional credentials into practical gates. Vendors define roles around technologies they own. Communities grant trust through participation. Clients and the public give, withdraw and contest legitimacy.

Those voices do not carry equal power. The state can make a title illegal to use. A dominant vendor can change a commercial ecosystem. An employer can keep a capable person from an interview. A community can deny permission to change shared work. A practitioner association can make a field more legible without compelling anyone to listen.

Florence Taylor lived through several definitions at once. Her college said she had learned. Her employer said she could work. The Institute said she did not belong, then reversed itself thirteen years later. Her publications gave her another kind of professional authority. History rejected the rejection.

That is the durable answer. A profession is not announced once. It is a contested settlement over knowledge, responsibility, recognition and access. The test of a modern gate is therefore not whether it resembles a guild in the abstract. It is whether we can see who holds each power, what evidence supports it, whom it protects, whom it excludes and how its decisions can be challenged.

Related reading

• The Medieval Guild: Apprentice, Journeyman, Master — the historical bundle of training, trust, welfare, power and exclusion.
• Certifications, Licences and the Fragmenting Credential — how to inspect a credential by object, issuer, evidence, consequence and current status.
• Apprenticeships, Traineeships and Dual Vocational Training — how work, learning, qualification and occupation are joined by different institutions.
• The Vocabulary of Work — why a profession is an institution, not merely a skilled occupation.
• Work and Identity — how recognition makes an occupational identity socially usable without exhausting the person.

Sources

• Ludlow, Christa. “Florence Mary Taylor.” Australian Dictionary of Biography; Powerhouse Collection. “Ephemera used by Florence Taylor.”
• State Library of New South Wales. Florence Mary Taylor papers, 1906–1968.
• New South Wales. Architects Act 2003.
• NSW Architects Registration Board. Protection of the architect title, regulation, registration checking and complaints.
• Architects Accreditation Council of Australia. 2021 National Standard of Competency for Architects.
• Abbott, Andrew. The System of Professions: An Essay on the Division of Expert Labor. University of Chicago Press, 1988.
• Wilensky, Harold L. “The Professionalization of Everyone?” American Journal of Sociology 70, no. 2 (1964): 137–158.
• OECD. Competition and Regulation in Professions and Occupations. 2024.
• Productivity Commission. National Competition Policy Analysis. 2025.
• Sinclair, Rob. “Microsoft Will Help Launch a New Association for Accessibility Professionals.” Microsoft Accessibility Blog, 2013; IAAP Nordic. “History.”
• International Association of Accessibility Professionals. Certification Overview, CPACC and CPACC Body of Knowledge.
• International Association of Accessibility Professionals. Certification Committee Charter and Rules and Policies.
• International Association of Accessibility Professionals. Certification Terms, Governance and Conduct and Application Appeals.
• Amazon Web Services. AWS Certified Solutions Architect — Associate and SAA-C03 Exam Guide.
• Amazon Web Services. Certification Policies and Partner Certification.
• Microsoft Learn. Microsoft Certified: Azure Solutions Architect Expert.
• Microsoft Learn. Credential Expiration, Renewal and Retirement.
• Microsoft Partner Center. Partner Capability Score and Solutions Partner Qualification Criteria.
• Microsoft Learn. Credential Item Challenge Process and Sharing Microsoft Credentials.
• Kubernetes Community. Community Membership and Contributing to Kubernetes.
• Kubernetes Contributors. OWNERS Files and Pull Request Process.
• Kubernetes. Participating in SIG Docs.
• Cloud Native Computing Foundation. Governance and Maintainer Council Template.
• Guidebeam Work Library. “The Medieval Guild: Apprentice, Journeyman, Master.” and “Certifications, Licences and the Fragmenting Credential.”