Careers
We’re always interested in designers who care about resilient, low-energy architecture.
Why Baldwin O’Bryan
- Specialist work in earth-sheltered & bushfire-responsive design
- Hands-on experience across concept, documentation and delivery
- Mentorship and a practical, buildable design ethos
- Small, focused team with meaningful project ownership
Questions before applying? Call +61 439 888 840 or email
obryan@bigpond.net.au.
Current Opportunities
- Registered Architect
- Graduate / Architectural Assistant
- Documentation / Draftsperson
- Intern (expressions of interest)
Email your CV/portfolio (PDF or link) to obryan@bigpond.net.au or call +61 439 888 840.
Please include role, availability and a short note on why our work resonates with you.
Culture & Benefits
- Flexible hybrid work by arrangement
- Project ownership with direct client + consultant exposure
- CPD support and paid registrations where applicable
- Calm, quality-first studio with low-energy design focus
How to Apply
- One-page cover letter (why us, why now)
- CV (2–3 pages max) with referees
- Portfolio (10–15 pages PDF or link; include tech/detail sheets)
Formats we love: PDF ≤ 15 MB or a web portfolio link (Google Drive, Issuu, Behance).
Tools & Workflow
- Revit / ArchiCAD (project dependent), AutoCAD, Adobe CC
- Thermal modelling + passive design tools
- Clear documentation standards and buildability reviews
- Site-based collaboration with builders + engineers
Locations & Flexibility
- Melbourne-based with regional and interstate projects
- Occasional site travel
- Part-time/return-to-work pathways considered
- We welcome diverse backgrounds and perspectives
FAQ
Do I need local experience?
Local experience is preferred, but strong technical portfolios and relevant project work are considered. Please highlight Australian standards exposure if you have it.
Do you sponsor visas?
Not currently. Applicants should have existing Australian work rights.
What’s the interview process?
Short screen → portfolio chat (online) → studio interview with task/markup discussion → reference checks.